Abstract In a software release cycle, some of the necessary l10n steps lack attention which affect translation quality and delivery. These steps (for a package) are extracting or updating language resource, pushing that to translation platform, pulling and packaging translations, quality checks etc. Transtats helps to tie up loose ends and making packages ready to ship with translation completeness.
Using transtats, a sync between upstream, translation platform and build system could be created, which can solve many problems and bring interesting results. One of them is to find translation gaps through which string change can be tracked. Determining out-of-sync packages and tracking of string change are helpful in locating / fixing translation errors.
Transtats Use Cases:
This contributes to overall success of g11n.
In this session we will discuss / demo transtats use cases, jobs, deployments and path ahead. As transtats jobs would be foundation to next developments - discussion around this would be of great help!
Audience Everyone interested in i18n / l10n. Folks involved in providing l10n support to their software / project. Developers, Quality engineers, language co-ordinators linked with l10n process.
This is a talk of 60 mins.
Presenters Sundeep Anand (fas: suanand) irc: suanand Parag Nemade (fas: pnemade) irc: paragan
How does this related to #38?
Here, we will try to cover new developments in transtats through slides and demo. This should be little technical and thorough aimed to bridge the gap with fedora i18n, l10n community in terms of "How to use Transtats". Primary audience are i18n, l10n, translation folks.
i18n
l10n
translation
An attempt to get i18n, l10n community on-board to transtats!
This is related to #38 as-in what can make transtats better for community? And how we should shape it and what should be the priority for transtats?
Thanks, that helps!
Metadata Update from @bex: - Issue assigned to bex
Metadata Update from @bex: - Issue tagged with: Talk Accepted
Metadata Update from @bex: - Issue close_status updated to: Talk Scheduled - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.