[Openstack-i18n] Infrastructure Translations Tools session at Kilo Summit

Akihiro Motoki amotoki at gmail.com
Thu Oct 30 09:26:50 UTC 2014


I cannot join the session just due to schedule conflicts.
I usually bridge Horizon translations and add one point worth considered.

How to manage translations for stable branches?
This is not related to the topic of translation tools, so I am not
sure it fits to the session.
Most of the following is now up to volunteer work and there is no
systematic process.

* Transifex does not support branch model and Daisy or I prepares new
resources for stable branches
  per release manually. Hopefully new translation tool supports branch model.
  The tricky point is "proposed/xxxx" branch and I don't think we can
automate all thing.
* Source string update of stable branch
  The source strings of stable branch are not updated automatically.
  Backport patches sometimes introduce new strings or string update,
  but they are not imported into Transifex unless I do not notice it.
* Translation import
  Translation import to stable branch is another topic. For master
branch it is done automatically
  by Jenkins job (thanks to Andreas). I am not sure it works for
stable branches because
  I would not like to see many translation import patches in stable reviews.

Regarding translation tool choice, I don't have strong opinion.
As maintenance point of view as a bridge of Horizon and I18N team, it
seems Andreas' trial
already covers my points.
As a translator, I hope the following in a new translation tool
* better translation memory and suggestion mechanism
* better issue tracking
  Transifex supports issue tracking as a comment, but there are
several pain points:
  * comments without "issue" mark cannot be tracked
  * issues are visible to all languages. some are for all languages
and some are language-specific
  * even after marked as "resolved", all issues are displayed in
Transifex interface.


On Thu, Oct 30, 2014 at 4:40 AM, Elizabeth K. Joseph
<lyz at princessleia.com> wrote:
> Hello translators!
> Thanks for your work evaluating Pootle and Zanata, the etherpad[0]
> will be very helpful to us. If others could chime in on Pootle in the
> next week or so it would be great.
> The Infrastructure team has reserved a spot in our track at the summit
> next week in order to discuss the tools and next steps based on your
> input and what Andreas and I have discovered about maintainability and
> process with regard to both tools.
> The session will be on Thursday at 11AM local (Paris) time:
> http://kilodesignsummit.sched.org/event/d40800cfbdcd2c9cf752c3cede10cf6e#.VFFBi3VGh5R
> Please join us if you're available. We've put some infrastructure
> notes and what we expect from the translations team in the "Summit
> session" part of our etherpad, so if there are other topics you wish
> to cover, please add them there:
> https://etherpad.openstack.org/p/kilo-translations
> If you're not available to join, feedback here on list, on the above
> etherpad or to Daisy, Andreas or myself is welcome so we can make sure
> your opinions/suggestions are represented at the session.
> [0] https://etherpad.openstack.org/p/translation-tools-comparation
> --
> Elizabeth Krumbach Joseph || Lyz || pleia2
> _______________________________________________
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

Akihiro Motoki <amotoki at gmail.com>

More information about the Openstack-i18n mailing list