Transtats

helps making packages ready to ship with translation completeness




Overview


Why 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 helps to tie up loose ends for translations. The idea is to track Translation Platforms for statistics, compare them with Release Streams, manage translation differences, and keeping upstream updated and creating notifications.


How Transtats Works

Transtats Jobs sync with translation platforms, release calendars, build systems and upstream repositories for registered packages to process translation data, and represent information through graphs for enabled languages grouped by releases. YML based jobs enhance capabilities and makes it flexible!


Transtats Stack

Transtats in i18n and l10n

Tracking translation progress of packages for downstream releases with respect to current development seems meaningful to localization teams, developers, package maintainers and quality engineers. From estimating translation update volume to inspecting translations in what packaged, it can be engaged throughout a release.



Package translation completeness

Once a package is sync’ed with the translation platform, upstream repository, and build system through jobs, meaningful results can be obtained. It shows the translation position at all three places. Plus with branch mapping done, differences could be calculated which indicate whether a package is out-of-sync or not, and if so, which languages need attention to get it fixed.


Translation volume estimation

Having an estimate at an early stage of the development cycle is very helpful for the translation team. Transtats does it for releases across packages. It has three views: combined, detailed and per language. This is achieved through branch mapping maintained for every package. It is also helpful for package maintainers and developers tracking strings during translation and packaging.


Package set coverage
based on graph rules

Sometimes tracking translation status of a component (for a release) is required, where a component comprises of a set of packages. This can be achieved by creating graph rules. Rule of a package set for a specific release in associated (to release branch) or selected languages. And coverage graphs are created based on these rules.