Infrastructure Translations Tools session at Kilo Summit
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#.VF... 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
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. Thanks, Akihiro On Thu, Oct 30, 2014 at 4:40 AM, Elizabeth K. Joseph <lyz@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#.VF...
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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Akihiro Motoki <amotoki@gmail.com>
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
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@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@gmail.com>
participants (3)
-
Akihiro Motoki
-
Andreas Jaeger
-
Elizabeth K. Joseph