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

Akihiro Motoki amotoki at gmail.com
Fri Oct 31 05:05:02 UTC 2014

Unfortunately I have many queued tasks by the middle of the Summit
and there is no spare time to evaluate them.....
I hope more translators try and input their feedback.

On Thu, Oct 30, 2014 at 6:45 PM, Andreas Jaeger <aj at suse.com> wrote:
> On 10/30/2014 10:26 AM, Akihiro Motoki wrote:
>> Hi,
>> 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.
> Could you have a look at the current demo systems and evaluate them for
> these topics? Your feedback on how the two systems handle this, would be
> great!
> Thanks,
> Andreas
> --
>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>   SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>    GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

Akihiro Motoki <amotoki at gmail.com>

More information about the Openstack-i18n mailing list