Overview for language translations across packages

About Transtats

In a software release cycle, localization steps like extracting or updating language resource, pushing them to translation platform, pulling and packaging translations, quality checks etc. seem necessary but sometimes they lack attention which results in delay.

Transtats is an attempt to tie up loose ends by creating mapping between translation platforms, releases (schedule & build system) and upstream. Its mostly around syncing with Translation Platform for statistics, comparing stats with Release Streams, managing translation differences, keeping upstream updated and creating notifications.

Tracking translation progress of packages for downstream releases with respect to current development seems meaningful to localization managers, developers and quality engineers.

Transtats Arch

Architecture wise, Transtats Jobs operate on some inventory: translation platforms, release streams and upstream repositories for registered packages to process translation data, and represent information in the form of tabular, graphs for enabled languages.

Translation Status
of packages

Translation progress of packages for most of the release branches in all enabled languages. This includes translation statistics of upstream repository as well. Provided packages are sync’d.

Translation Workload
by releases

Translation workload estimation for a release branch across packages. It has three views: combined, detailed and per languages. This is achieved through name and branch mapping created for every package.

Translation Coverage
based on graph rules

This is for custom needs. Translation coverage of a package list for a specific release in associated (to release branch) or selected languages. These are based on graph rules, which can be created by anyone.