From Fedora Project Wiki

mNo edit summary
mNo edit summary
 
Line 1: Line 1:
In a software release cycle, localization steps like...
= Transtats Project =
* extracting or updating language resources,
* pushing them to translation platform,
* pulling and packaging translations,
* translation quality and other checks etc.
seem necessary but sometimes they lack attention which results in delay.


[http://transtats.org/ Transtats] is a web application which tries to tie up upstream repositories, translation platforms, build system, and product release schedule together to solve problems of mismatch, out-of-sync conditions and to assist the timely packaging of quality translations. Actually, it collects translation data, analyzes them, and creates meaningful representations. Fedora Transtats is hosted at [https://transtats.fedoraproject.org/ transtats.fedoraproject.org]


Translation is the most fundamental in localization process and tracking its progress seems quite helpful in overall success. Looking at this more generically, translation process is distributed and at times lies with community. Whereas in-house/outsourced translation is more requirement driven. In simple words its difficult to say where translation is happening upstream vs downstream, which may introduce some redundancy (in cost, may be).


[[File:ts-landing.png|700px|thumb|center|Transtats Landing Page]]
Basically an answer to following:
* Trends for language translation across packages. Irrespective of where their translations are hosted.
* Translation and i18n QA workload estimation for approaching release.
* A basis to l10n/i18n automation of a few steps, may be.
* A method to streamline translation process, upstream vs downstream.




Idea is if we can have translation status of the package for downstream (example: Fedora releases) with respect to current development. [http://transtats.org/ Transtats] is an attempt to tie up loose ends and then, may be automate some of the steps. Concept is based on syncing with translation platform for statistics (How progress is going?), comparing stats with release streams (Is latest translations packaged?), managing translation differences (What piece of translation cause an error or left to get translated or ..?), keep upstream updated (May be update upstream with translations?) and create notifications (Based on release dates: to Developers, Quality Engineers and Managers?).
Idea is if we can have translation status of the package for downstream (''example: Fedora releases'') with respect to current development. An attempt to tie up loose ends and then, may be automate some of the steps. Concept is based on syncing with translation platform for statistics (''How progress is going?''), comparing stats with release streams (''Is latest translations packaged?''), managing translation differences (''What piece of translation cause an error or left to get translated or ..?''), keep upstream updated (''May be update upstream with translations?'') and create notifications (''Based on release dates: to Developers, Quality Engineers and Managers?'').




[[File:ts-stack.png]]
[[File:ts-arch.png|500px|thumb|center|Transtats Architecture]]


= Learning More =


The solution is based on creation of mapping between translation platform, releases and upstream.
Read [https://fedoramagazine.org/tracking-translations-with-transtats/ magazine post] and [http://docs.transtats.org/en/latest/ docs] to dive deep! The project has been covered at [https://flocktofedora.org/ flock] conference a couple of times:


Keep reading [http://docs.transtats.org/en/latest/ docs] to dive deep! If you like the idea and have some points to add/discuss please create GitHub [https://github.com/transtats/transtats/issues/new issues].
* [https://www.youtube.com/watch?v=jgXJZRj43M0 2019 - Use cases for Transtats in the Fedora community]
* [https://www.youtube.com/watch?v=yy3GuMtRnUY 2018 - Using transtats to track translation string change]
* [https://www.youtube.com/watch?v=Ln9e3LM2Ht8 2017 - Introduction to Transtats]
 
= Contribute to Transtats =
 
* Follow [https://github.com/transtats/transtats/blob/master/CONTRIBUTING.md contributing guide] to make changes in Transtats.
* Join the `[https://webchat.freenode.net/?channels=#transtats #transtats]` channel on chat.freenode.net
* See [http://docs.transtats.org/en/latest/roadmap.html roadmap] and [https://github.com/transtats/transtats/issues issues] to discuss more.
 
= Bugs and Requests =
Feel free to open an [https://github.com/transtats/transtats/issues/new issue] and help us to look into the problem/request.
 
= People =
 
Awesome folks from fedora [https://fedoraproject.org/wiki/G11N g11n], [https://fedoraproject.org/wiki/I18N i18n], [https://fedoraproject.org/wiki/L10N l10n], [https://fedoraproject.org/wiki/Infrastructure Infra] and [https://fedoraproject.org/wiki/QA QA] teams!
 
As well as source repository contributors [https://github.com/transtats/transtats/graphs/contributors transtats], [https://github.com/transtats/transtats-cli/graphs/contributors transtats-cli], [https://github.com/transtats/transtats.github.io/graphs/contributors transtats.org].

Latest revision as of 10:06, 22 July 2020

Transtats Project

Transtats is a web application which tries to tie up upstream repositories, translation platforms, build system, and product release schedule together to solve problems of mismatch, out-of-sync conditions and to assist the timely packaging of quality translations. Actually, it collects translation data, analyzes them, and creates meaningful representations. Fedora Transtats is hosted at transtats.fedoraproject.org


Transtats Landing Page


Idea is if we can have translation status of the package for downstream (example: Fedora releases) with respect to current development. An attempt to tie up loose ends and then, may be automate some of the steps. Concept is based on syncing with translation platform for statistics (How progress is going?), comparing stats with release streams (Is latest translations packaged?), managing translation differences (What piece of translation cause an error or left to get translated or ..?), keep upstream updated (May be update upstream with translations?) and create notifications (Based on release dates: to Developers, Quality Engineers and Managers?).


Transtats Architecture

Learning More

Read magazine post and docs to dive deep! The project has been covered at flock conference a couple of times:

Contribute to Transtats

Bugs and Requests

Feel free to open an issue and help us to look into the problem/request.

People

Awesome folks from fedora g11n, i18n, l10n, Infra and QA teams!

As well as source repository contributors transtats, transtats-cli, transtats.org.

Retrieved from "https://fedoraproject.org/w/index.php?title=Transtats&oldid=583185"