Transtats has been into development for a while now, and has some interesting results.
It talks to translation platforms (DamnedLies and Zanata), Releases (Schedule and Build
System) and Git repository of a package which creates possibilities doing multiple tasks.
One of them is finding translation gaps. Lets talk a bit on use cases:
Q) What is translation completeness of a package, say abrt, for fedora 28? Is it in sync -
are all translations done at platform packaged and built in koji?
40 packages are added as of now, which are pointing to 3 translation
Q) How many packages are out-of-sync for fedora 28? And for which languages?
Please select individual package to see language details.
Q) How to see translation status for a package built in koji for other build_tags?
A) Please run a job at http://transtats.xyz/jobs/yml-based
Q) What is estimated translation volume for fedora 28 across 40 packages?
Please switch to "Language Wise" view for insights.
Q) How to look at translation coverage of a package set for f28 in, say, 10 languages?
A) We can create graph rules. For example: for, say, "rhinstaller"
component/package-set, we have
This seems quite helpful to developers, i18n quality engineers and l10n-team. Please see
quick start doc to get started and for FAQs. Complete docs are stored at
In this development stream, next step is to compare POT and PO, both from all three
locations and see reasons behind string breakage. We are working with fedora-infra team
for deployment. We would request you to give it a try and share feedback / comments /
suggestions - to make this better!