- OpenStack-I18n - lists.openstack.org

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Douglas Fish 23 Sep '15

23 Sep '15

2 2

Automatic copying of translations in Zanata?
by Andreas Jaeger 22 Sep '15

22 Sep '15

Today the majority of the IBM translations got merged into the the normal versions since zanata by default searches at every upload with the zanata client for translation of untranslated strings and merges them [1]. So, when ceilometer got uploaded as master version, the IBM ceilometer strings where searched for already translated strings and untranslated ceilometer strings where automatically translated with the IBM version. Daisy, Clark, Lyz, and myself just had some discussion on #openstack-i18n and decided to disable for now the automatic copying of translations while we discuss what to do next. The question for me is, do we want this kind of automatic copying of translations - and if, how do we want it. Previously enabled was copying only in a project between versions. So, for example if there is a stable/liberty and a master version (or an IBM and a master version) of the same document, and one contains a translated string and the other gets updated, the translated string gets copied over if the string is not translated yet. This feature can also be enabled for copying between projects and files. So, we could enable it and then when a string gets translated in let's say nova and exactly the same string is in neutron and untranslated, the translation would be copied from nova to neutron. So, question to discuss: 1) Do we translators want such automatic translations? 2) And if yes, only between: a) versions of same document b) inside a project (so, only inside nova) c) across all projects and documents Note that this setting is the same for all languages. Note that there's an option as well to do this automatic translation manually, for example at project creation time. So, if a new project gets setup, Zanata could try to copy automaticly translations across projects for a quick start. What do you think? Do you want to translate each string manually - or let Zanata do the work and to which extend? I hope I summarized everything correctly, if not please correct my understanding, Andreas References: [1] http://zanata.org/help/copytrans-explained/ -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Please review IBM translations in the master branch
by Ying Chun Guo 22 Sep '15

22 Sep '15

Hi, friends Something unexpected happened tonight. IBM translations were copied into master branches. The copy action is triggered by uploading of pot files, which are executed by automatic Jenkins jobs when the source pot files in code repo are updated. Nobody expects it. Infrastructure team have figure out a way to stop auto copy while uploading pot files so this kind of things won't happen the second time. IBM translations only fill in blanks without overwriting the others. I hope translation teams could take a look at IBM translations in the master branches. IBM contributions could be located by searching "last-modified-after: 2015-09-21". You could * improve translations if they are easily to improve. Different terminologies could easily be fixed by "project-wide Search & Replace". ( in the Editor view, click the magnifying glass icon on the right top corner to open the search&replace view.) * reject some translations if you don't like. * If you don't like the whole translations at all, I may work out a way to revert it but it will cost time. The relevant translation teams include: de es fr it ja ko_KR pt_BR ru zh_CN zh_TW. The relevant documents are: nova.pot, glance.pot, swift.pot, ceilometer.pot, cinder.pot, heat.pot, ironic.pot, keystone.pot and neutron.pot. Sorry for the troubles and thank you for your work. Best regards Ying Chun Guo (Daisy)

1 0

IP capitalization change in nova - ok to merge?
by Andreas Jaeger 22 Sep '15

22 Sep '15

Translation team, I've just send a patch for review that fixes lots of user visible capitalization strings in nova as I noticed during translation that it should be "IP" and not "ip" for example in "fixed IP". Is it ok to get this patch in now - or should I wait after liberty and mark it as WIP for now? https://review.openstack.org/225923 Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

2 1

Re: [Openstack-i18n] Would like Zanata branch to correct 1494819
by Ying Chun Guo 22 Sep '15

22 Sep '15

Hi, Doug We need to consider it carefully. After working with Zanata dev team, I got to understand: 1. Zanata has its own plural forms. If po file has its own plural form, Zanata will use that. Otherwise, Zanata will use its own plural form. Pluralforms in Zanata: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2). So it looks like that OpenStack po files overrode the pluralforms in Zanata. 2. Zanata currently don't allow update of plural forms once the document has been uploaded to Zanata. Even with deletion of that source document and re-upload (in the same project-version, same doc name and same path), Zanata will still reuse the old pluralform. 3. If we want to update the pluralforms, we will need to do it in new project-version (don't use copy-from previous version function). I think we need to carefully design the steps to change pluralforms of Russian. At first, I want to confirm with you, are you sure this issue is caused by plural forms? Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 2015/09/18 23:38:22: > From: Douglas Fish/Rochester/IBM@IBMUS > To: guoyingc(a)cn.ibm.com > Cc: openstack-i18n(a)lists.openstack.org > Date: 2015/09/18 23:38 > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > Hi Daisy, > > Yes, I understand - I don't think I can even propose my branch > unless I am added as a translator by the Russian team. > > My proposal would include removing one plural form for > 4 messages in horizon django.po > 1 message in horizon djangojs.po > 144 messages in openstack_dashboard django.po > 0 messages in openstack_dashboard djangojs.po > plus the pluralization specification would be updated in all 4 files. > > Doug > > ----- Original message ----- > From: Ying Chun Guo <guoyingc(a)cn.ibm.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: openstack-i18n(a)lists.openstack.org > Subject: Re: [Openstack-i18n] Would like Zanata branch to correct 1494819 > Date: Fri, Sep 18, 2015 3:25 AM > > Are there a lot of changes in your proposed po files ? > I'm still waiting for Russian team's response. > > Best regards > Ying Chun Guo (Daisy) > > > "Douglas Fish" <drfish(a)us.ibm.com> wrote on 09/18/2015 05:37:07 AM: > > > From: "Douglas Fish" <drfish(a)us.ibm.com> > > To: openstack-i18n(a)lists.openstack.org > > Date: 09/18/2015 05:38 AM > > Subject: [Openstack-i18n] Would like Zanata branch to correct 1494819 > > > > Hi translation friends, > > > > I'd like to contribute 4 PO files for the Horizon Russian > > translation to correct the issue > > https://bugs.launchpad.net/openstack-i18n/+bug/1494819 > > > > These uploads won't contain any new translations, but instead will > > be an adjustment to the PO files so they have 3 pluralities, which > is standard > > http://localization-guide.readthedocs.org/en/latest/l10n/pluralforms.html > > > > Specifically, I plan to remove the msgstr[2] translation from the > > files (because msgstr[2] is blank for many cases), rename the msgstr > > [3] translation to msgstr[2] and adjust the plurality specification to > > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && > > (n%100<10 || n%100>=20) ? 1 : 2); > > > > As discussed in the team meeting http://eavesdrop.openstack.org/ > > meetings/openstack_i18n_meeting/2015/openstack_i18n_meeting. > > 2015-09-17-13.00.log.html > > please create a Zanata branch so I can propose these corrections for review. > > > > Thanks! > > > > Doug > > _______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

1 0

Translation of Nova
by Ying Chun Guo 21 Sep '15

21 Sep '15

Hi, John I put nova project as the first non-user interface project in Liberty translation. I set nova.pot as "required to be translated" and set nova-log-* as "optional to be translated". I understand nova.pot contains all user facing messages. But I don't clear what kinds of messages they are. Could you explain what kinds of messages nova.pot includes and how these messages are visible to end users ? There is another mail thread[1] discussing that python-openstackclient should be high priority to translate. And other clients such as python-novaclient are deprecating and should not be translated or lower priority to be translated. I know you are busy with the RC1 cut. When you are available, help to share some inputs. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001389.h…

2 1

Re: [Openstack-i18n] Zanata, message to the team
by Akihiro Motoki 21 Sep '15

21 Sep '15

I see no technical reason. I am okay if we have a consensus that we can use various languages on the list to discuss topics specific to languages. Does everybody want this? I don't think it works if message in Frensh, Spanish, Chinese, Russian, Japanese, Korean, Turkish, Arabian and more on a single list. I might be missing something important. OpenStack foundation provides use the mailing list server under openstack.org domain and local communities can use it. Akihiro 2015-09-17 23:40 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Can't other languages be used on the mailing list? Is this a technical > limitation? > > Doug > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 09/17/2015 09:08:26 AM: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Openstack-i18n Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > Date: 09/17/2015 09:09 AM > > Subject: Re: [Openstack-i18n] Zanata, message to the team > > > > One thing to note is that each language team would like to discuss > > in its language in most cases. > > > We don't want to use English in translation discussion :p > > Thus I think this mailing does not work to address the original question. > > > > In Japanese case, we use a mailing list in the local community, > > but not all language team has such media and they might had Transifex > > messaging to communicate each other. > > > > 2015-09-17 22:50 GMT+09:00 Andreas Jaeger <aj(a)suse.com>: > > On 2015-09-17 15:19, Jeremy Stanley wrote: > > On 2015-09-17 07:58:39 -0500 (-0500), Douglas Fish wrote: > > Can't the openstack-i18n mailing list be used for this? In the > > openstack-dev lists multiple teams use it and we just include [horizon] > or > > [keystone] or similar as appropriate to help sort out messages to > > interested parties. > > > > The nice thing about this is that it makes the discussion open to others > > who might take interest periodically. > > > > Not only that, the discussion is also archived and accessible > > anonymously over the Web. Any group contact mechanism built into > > Zanata as an afterthought is going to be inferior to proper mailing > > lists as a general discussion platform. > > > > > Challenge is that not every translator is subscribed here AFAIU. How > > can we encourage usage of this mailing list? > > > > Andreas > > -- > > Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > > HRB 21284 (AG Nürnberg) > > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > > > > > > _______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > _______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > >

4 4

Liberty translation progress report
by Ying Chun Guo 21 Sep '15

21 Sep '15

Hi, team 10 days passed since we started Liberty translation. Now let's review the progress we made. 1. Horizon translations Till today, following teams have made amazing progress. Many thanks for their works. These teams could certainly finish Horizon translation on time. They are: Japanese 100.0% English (Australia) 99.63% French 98.61% German 98.51% Chinese (China) 97.56% Spanish 97.28% Turkish (Turkey) 96.76% Czech 96.55% Korean (South Korea) 96.0% Chinese (Taiwan) 95.12% Portuguese (Brazil) 93.13% Following teams have possibilities to catch the deadline too. They are: English (United Kingdom) 87.85% Russian 83.58% Polish (Poland)80.48% If coordinators of those language teams have difficulties to catch the goal, please let me know as soon as possible. 2. Horizon authorization page translations This is not a big resource. There are 12 languages 100% completed. They are: Chinese (China),Czech,English (Australia), English (United Kingdom),German, Japanese,Korean (South Korea), Portuguese (Brazil),Russian,Spanish,Spanish (Mexico), Turkish (Turkey). There are only a very few strings left in Chinese (Taiwan), Polish (Poland), and French translations. Please don't forget to finish them. 3. Nova translations nova.pot is included in Liberty translation plan. Following language teams have made good progress: Chinese (China) 100.0% Czech 99.63% Spanish 94.78% Turkish (Turkey) 94.1% Some others languages team might not have good progress. I understand some translators are not active in Nova translations. For those language teams, I will suggest to import IBM translations. While I did test, after merging IBM translations, the percentage will increase to 90% and even more. I hope coordinators could take a serious consideration of this suggestion. I appreciate very much your contributions in Liberty translations. I'm very sure we will get a good result in Liberty. Thank you. Best regards Ying Chun Guo (Daisy)

1 0

PTL Elections September 2015
by Ying Chun Guo 21 Sep '15

21 Sep '15

Hi, team We just became a official team in Liberty, I guess some of you are not familiar with PTL elections process. Every official project must elect a PTL. PTLs are elected for 6 months. All ATC's have the right to vote for your favorite PTL for a cycle. Refer to this wiki page: https://wiki.openstack.org/wiki/PTL_Elections_September_2015 I have submitted my candidacy for I18n team just now. Hope to get your support for my PTL role for Mitaka. Thank you. Regards Daisy

2 2

Would like Zanata branch to correct 1494819
by Douglas Fish 18 Sep '15

18 Sep '15

2 2