Quick Start
Introduction
Reports are generated for the languages, and their aliases are used while syncing. One can create a language set, which can be associated with a product release. Multiple instances of a translation platform can be added. A release should have a language set and a schedule attached. Transtats jobs talk to upstream repositories, translation platforms and build systems to keep translation statistics, build tags and release schedule latest.
Add and Configure Packages
While adding a package, upstream URL is required. And the package name is verified with selected translation platform. Translation of a package can be tracked for multiple products. The package should be sync'd with the translation platform and the build system. Once sync'd, branch mapping will be created. It maps product releases with most suitable project versions available at translation platform and with appropriate build tags. The package can be sync'd with upstream repo as well.
Generate Diff
Once we have all versions/tags mentioned in branch mapping of the package sync'd with pointing translation platform or build system, differences can be created. This answers - for a package - latest translations are packaged or not? Which languages need attention?
Add Coverage Rule
Coverage (for a group of packages in a set of languages to a given release) is based on rules. Slug form of the rule name will be saved. This should be specific for a product release. Packages having branch mapping are included here. Languages can be picked either from language set associated with the release or from enabled ones. Corresponding build tags can be overridden too. This shows statistics differences in details.
Experience
Transtats has two traversal options: releases and languages. One can see high level summary and can pick any of releases or languages, followed by packages. Summary can tell you: packages which are out of sync, release by release l10n effort progress and much more. Run a job to track string change.
FAQs
Is Transtats project open source? Where are the docs written?
Yes. Source code is available at GitHub. Project's website is transtats.org and point your browser to docs.transtats.org for complete documentation.Which translation platforms and build systems are currently supported?
Transtats supports DamnedLies, Transifex, Weblate and Zanata translation platforms. Transtats can talk to koji build system.What is branch mapping? And why is it important?
Every package has its own branch mapping. This establishes mapping between:Transtats product_release :: translation platform project_version :: build system build_tag
On the basis of this, translation differences/gaps are derived.
How to figure out which languages need attention for any of the packages?
Please navigate to package details page. Sync the package with translation platform and build system (use shortcuts). Update branch mapping.Once all the mapped branches get sync'd, update statistics diff. Here you could find an answer to this!
Which jobs are available?
Broadly two categories: Predefined and YML based.Predefined jobs fill data required by various work-flows. syncbuildtags should be run first (one-time), as it is required for branch mapping and syncdownstream jobs.
Three templates are available in YML based jobs: syncupstream, syncdownstream and stringchange.
Why YML based jobs are introduced?
YML based jobs add great level of flexibility by broadening capabilities to interact with build systems, translation platforms and source repositories.Which YML job to run when and why?
They can be run in any order. Just that required values should be obeyed.- To collect translation statistics from package source repository, syncupstream job can be triggered. This job can only be run for added packages.
- Using syncdownstream job, one can inspect translation files and generate statistics in latest built SRPM. This applies patches (as-per SPEC file) also.
- Translation string change can be detected using stringchange job. This is highly flexible. Requires package branch mapping and POT command.
How to look and share for details about a YML job ran?
Please navigate to job log details page. Here you would find the YML supplied to the job and respective output of each task.If the job type is stringchange msgid diff found in translation template would be available along with full line-by-line file diff. This URL can be copied and shared.