[Mageia-i18n] Workflow for i18n translators
misc at zarb.org
Mon Dec 20 14:35:00 CET 2010
Le samedi 18 décembre 2010 à 09:49 +0800, Funda Wang a écrit :
> 2010/12/18 Wolfgang Bornath <molch.b at googlemail.com>:
> > We already have 2 major points which (according to what I read so far)
> > are important:
> > - online and offline work should be possible.
> > - only 2 or 3 translators of each language should be able to commit
> > (which implies collaboration)
> FYI, since transifex 1.0, it provides a nice CLI toolkit for both
> translators and developers. Translators could sync and commit po file
> directly to transifex platform via this toolkit, without any web
Yup, and I packaged this tool.
For more information :
> And, the task of commit translation to VCS becomes the duty of
> developer, not the transifex robot anymore. We might want to improve
> our mgasys tool, so that something like "mgasys tag urpmi 4.0" would
> commit translations from transifex to our VCS, then tag it into
> soft/urpmi/tags/4.0, and finally generate a urpmi-4.0.tar.xz in the
> developers harddisk.
That's not really the goal of mdvsys to manage anything else than rpms.
Ie, for software, I would push this either in generic tools ( like
moap ), specific tools ( like dist:zilla ), or directly in plain old
Another solution is a simple cronjob that run transifex command line
tool with proper svn acl management on languages file.
More information about the Mageia-i18n