Using Transtats to ensure Package Translation Completeness

Transcript

1. 1.

   Using Transtats to ensure package translation completeness transtats.org

2. 2.

   Software Package Localization i18n-ed app あ A platform extract push

   pull merge & compile build ship package
3. 3.

   Challenges we face - Is everything translated packaged? - Are

   all strings pushed to translation platform latest to software repositories? - Is there a way to speed up the process?
4. 4.

   Software Package Localization: Closer Look i18n framework i18n-ed app POT,

   PO, MO INI, JSON PROP, DTD RC, RESX XML, YML あ A DamnedLies Pootle Transifex Weblate Zanata srpm, rpm dsc, deb pkg jar, apk msi git, svn, bzr, etc. yum, apt (dpkg), brew, etc.
5. 5.

   i18n frameworks i18n framework Programming Language App framework C /

   C++ Python .NET Java Ruby GoLang PHP JavaScript C / C++ .. Django .. ASP MVC .. Spring .. Rails .. Revel .. Drupal .. Angular .. gettext babel System.Globalization Java i18n Libraries Rails i18n API i18n servlet PO RESX DTD PROP multiple
6. 6.

   Transtats Support Translation Platforms i18n Frameworks Build Systems Version Control

   ( POT, PO, MO ) ( koji - srpm/rpm - yum/dnf ) ( pagure, github, gitlab, bitbucket, etc.) * logo(s) belong to their respective owners.
7. 7.

   Demo - Is everything translated packaged? Package Translation Completeness -

   Are all strings pushed to translation platform latest to software repositories? Job to detect string change. - Is there a way to speed up the process? YML Jobs https://youtu.be/RHPtsIHNIgg
8. 8.

   How Transtats Works?

9. 9.

   Q Answers Thanks! {~} transtats.fedoraproject.org </> github.com/transtats (?) docs.transtats.org #fedora-g11n

   #transtats [$] .fasinfo suanand Sundeep Anand suanand@fedoraproject.org