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:
Tracking translation progress across packages for downstream releases with respect to current development. Finding translation gaps by syncing with source repositories, translation platforms and build systems. Estimates translation update volume at an early stage of a release cycle. 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!
