March 2016 - OpenStack-I18n - lists.openstack.org

Translation server is back !
by Ying Chun Guo 18 Mar '16

18 Mar '16

With the great support from infrastructure team, now we have our translation server back. You can login to http://translate.openstack.org to continue your work then. Sorry for the inconvenience. Best regards Ying Chun Guo (Daisy)

2 1

Re: [Openstack-i18n] Looking for Translations for Nova Mitaka RC1
by Ragwitz, Augustina 18 Mar '16

18 Mar '16

> According the agreement about StringFreeze[1], cutting RC1 means hard > freeze and translators can get extra 10 days to complete their > translations after hard freeze. So I don't think we can finish the job > next week. The translation work is planned to be finished at the early of > the week after next. > > Can you figure out when is the last day to merge nova translations ? I will follow up with the Nova team to find out our projected timeline for RC2. We have our team meeting today so I'll bring it up then. I assumed it would be end of next week based on the date in Launchpad for the OpenStack project [1], but this might not be accurate. [1] https://launchpad.net/openstack/+milestone/mitaka-rc2 --- Augustina Ragwitz Sr System Software Engineer, HPE Cloud Hewlett Packard Enterprise --- irc: auggy

1 0

Glossary management
by Akihiro Motoki 17 Mar '16

17 Mar '16

# I changed the thread title to the appropriate one. 2016-03-01 17:23 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you for the input, Akihiro and Kato. > > I'm not strict in local communication method and IRC ID. > If you have clearly documented them in your team wiki, that's fine. > > As to the glossary, I still think git repository is better than > wiki to store glossaries. Git repo has strict control, while wiki > has no controls at all. Wiki is used for frequently update purpose. > After it turns to mature, Git repo is good to store. I agree that it is better to use gerrit to manage glossaries, but all of my efforts disappointed me and discourage me to do more efforts. I already tried to maintain our glossary with context in our git repository. It used YAML file and converts it to PO files. It allowed us to keep contextual information. You said it will be discussed in the IRC meetings, but I got no feedback. I felt it was simply ignored (or rejected). (I could not join IRC meetings. If joining meetings is a requirement, I have to go away.) I clearly define what is required, but I don't see any counter solution provided and it forces me to use useless format (i.e., PO files). I believe I already have made enough proposal, but all of the results disappoints me and discourage me to try more efforts because it tends to waste my time. Finally, I tried to use another way to manage the glossary, then I was complained that it is not a standard way...... As a result, I had no way to satisfy requirements. Managing the glossary in two places is completely less-productive, maintain the master glossary with context information and then copy it into i18n repo (with losing the contextual information). > And, using pot/po file can make all translation teams to easily follow the > same glossary list. Do you mean even if the data format does not satisfy our requirements we should use it? Unified tools or formats are also important, but tools/format which do not satisfy requirements are useless. > As to the glossary, I still think git repository is better than > wiki to store glossaries. Git repo has strict control, while wiki > has no controls at all. Wiki is used for frequently update purpose. > After it turns to mature, Git repo is good to store. Regarding wiki usage, I don't think each language team page is not frequently updated. Does this mean a language team page does not fit into Wiki? I am not sure why we need to apply strict policy only for glossary. If the problem is that a wiki allows everyone to edit contents (i.e. glossary in this case), it is a problem of communication in a local language team. Final question. Gerrit is an easy way for translators or translation reviewers? If a language coordinator is forced to proxy maintaining glossaries, Perhaps, I am expecting too much and I may be better to be a translator. Akihiro > I understand Japanese glossaries are out of date and your team don't > like the current one in Zanata. If that's your team decision, I'm OK > to delete it from Zanata. > > Thoughts? > > Best regards > Ying Chun Guo (Daisy) > > > "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> wrote on 2016/02/27 > 17:08:46: > >> From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> >> To: "'Akihiro Motoki'" <amotoki(a)gmail.com>, Ying Chun Guo/China/IBM@IBMCN >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/27 17:40 >> Subject: RE: [Openstack-i18n] To language team coordinators: get >> ready for Mitaka translation >> > >> > Thanks Daisy for initiating this. >> > >> > 2016-02-25 17:53 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > Dear coordinators, >> > > >> > > Mitaka translation will be started at the beginning of March, and >> > > probably ended in the week of March 28. >> > > We need to get ourselves ready for Mitaka translation from now on. >> > > >> > > Because of the join of IBM professional translators, we will be able >> > > to cover more projects in our translation plan of this release. >> > > Generally, the jobs of existing community translators will not be >> > > affected, focus on Horizon, same as before. >> > > IBM translators will focus on "other" projects. >> > > >> > > Before Mitaka translation starts, there are several things you can do: >> > > >> > > 1. Update glossary. >> > > >> > > If you don't have glossary translations in i18n repo[1], or you want >> > > to update glossary translations, you can send a patch with your >> > > translations or your updates to i18n repo directly. >> > >> > I would like to raise a question how the glossary work? Is it actually >> > working? >> > >> > As one of coordinators of Japanese team, the glossary list itself is >> > out-of-date. >> > In addition to update per-language glossary, can we update a list >> of glossary >> > itself? >> > >> > Beyond this, the current format of PO file for the glossary lacks an >> > essential feature as I described before. There is no way to describe the >> > context. >> > I wonder how the glossary help translations without the contextual >> > information. >> > As a result, Japanese team is forced to describe contextual information >> > in translated strings. >> > This is the reason we preferred to Wiki style glossary. >> > >> > From the above observation, does it sound a good option to clear the >> > whole >> > entry of Zanata glossary of a specific language? >> >> +1 to clear, as long as Japanese, as of now. >> >> > > 2. Document your local team communication method in the team wiki >> > > page[2]. >> > > >> > > While Mitaka translation starts, it's good to open your local >> > > communication channel to all of your language translators. Good >> > > communication is quite important for people from different places to >> > > work well together. >> > >> > I missed the previous team meeting (it is not special to me due to >> the meeting >> > time). >> > I would like to make some follow-up comments on a local communication. >> > >> > I personally would like to continue to use Gitter (hosted by Github) as >> > a communication channel in Japanese team. From my past experience, it >> > has >> > various good merits. >> > I felt the first point is really useful in the crunch time of Liberty >> > translation reviews. >> > >> > * Pros: >> > * it has a notification mechanism. Unread messages will be notified >> > via >> > email. >> > * It can be used via browser (without any extra application) >> > * Unlimited archive as long as gitter room is open to everyone >> > * Cons >> > * it is not provided by OpenStack infra >> > >> > Kato-san and Japanese team members, feel free to comment it. >> > Your feedbacks would be really appreciated. >> >> I agree to using Gitter in Japanese team. >> >> In my understand, using IRC channel for local team is not mandatory, >> just an option. >> >> >> > > 3. Join IRC channel[3] #openstack-i18n with your zanata ID >> > > >> > > As a coordinator, you have the responsibility to coordinate your >> > > language translations. >> > > A good practise is to show up in IRC and have your people to get you >> > > easily when they have troubles. >> > >> > "with Zanata ID"? It is just an option. It is not a requirement. >> > It is not a surprising thing someone uses an IRC nickname different from >> > Zanata ID. >> >> I'm using different IDs :) >> And, I'm not always join IRC because of my business reason and equipments. >> To coordinate my local language team, I'd like to use Gitter and >> local mailing list. >> >> >> Regards, >> KATO Tomoyuki >> >> > Note that it is important we need to know each other who you are but it >> > is not a requirement to use Zanata ID as IRC nickname if you already use >> > a different IRC nick. >> > >> > > If you have any questions, talk to me. >> > > My IRC ID is "Daisy" in the channel of #openstack-i18n. >> > >> > I can help you too. My nick is 'amotoki'. >> > I am usually online from 0200UTC to 1600UTC. >> > >> > # It will be easier to find me compared to finding Daisy on IRC :) # >> > Just >> > joking.. never mind Daisy! >> > >> > Akihiro >> > >> > > Thank you. >> > > >> > > Best regards >> > > Ying Chun Guo (Daisy) >> > > >> > > [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale >> > > [2] https://wiki.openstack.org/wiki/I18nTeam/team >> > > [3] https://wiki.openstack.org/wiki/IRC >> >

3 2

Re: [Openstack-i18n] Cannot connect to Zanata
by Ilya Alekseyev 17 Mar '16

17 Mar '16

Dear Yumiko, Ian, Kato-san, same here, i can login to openstack.org and more i've checked in https://openstackid.org/accounts/user/profile that authentification is successfull: https://translate.openstack.org:443/openid.seam | LOGIN But unfortunatelly can't login to zanata. Kind regards, Ilya Alekseyev. 2016-03-17 10:28 GMT+03:00 Yumiko Ogawa <OGAWAYUM(a)jp.ibm.com>: > > Kato-san, > > Yes, I can login www.openstack.org without any problem, but not Zanata... > > Best regards, > > 小川優美子 Yumiko Ogawa, PMP® <ogawayum(a)jp.ibm.com> > Translation Services Center, IBM Japan > Tel: 03-3808-5007 > > > "Kato, Tomoyuki" ---2016/03/17 16:22:32---Hi, Can you login www.openstack.org? > > From: "Kato, Tomoyuki" <kato.tomoyuki(a)jp.fujitsu.com> > To: Yumiko Ogawa/Japan/IBM@IBMJP, Ilya Alekseyev <ilyaalekseyev(a)acm.org> > Cc: "openstack-i18n(a)lists.openstack.org" < openstack-i18n(a)lists.openstack.org> > Date: 2016/03/17 16:22 > Subject: RE: [Openstack-i18n] Cannot connect to Zanata > > > ________________________________ > > > > Hi, > > Can you login www.openstack.org? > # I can. But I can not login translate.openstack.org, too. > > I guess it seems to be a combination problem between > Zanata and OpenStack OpenID, or Zanata standalone problem... > > KATO Tomoyuki > > > -----Original Message----- > > Hi, > > > > We have the same problem in Japan. I understand that the OpenID authentication system is down. Our translators have been > > on standby all day today, so hopefully Zanata will be back soon. > > > > 小川優美子 Yumiko Ogawa, PMP® <ogawayum(a)jp.ibm.com> > > Translation Services Center, IBM Japan > > Tel: 03-3808-5007 > > > > > > Ilya Alekseyev ---2016/03/17 15:59:39---Dear colluegues, for some unknown reason i cannot connect to Zanata. > > > > From: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > To: "openstack-i18n(a)lists.openstack.org" < openstack-i18n(a)lists.openstack.org> > > Date: 2016/03/17 15:59 > > Subject: [Openstack-i18n] Cannot connect to Zanata > > > > ________________________________ > > > > > > > > > > Dear colluegues, > > > > for some unknown reason i cannot connect to Zanata. > > Tried different browsers and it just don't work. > > Wonder if somebody have the same problems? > > > > Kind regards, > > Ilya Alekseyev_______________________________________________ > > Openstack-i18n mailing list > > Openstack-i18n(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > > > > > > > >

1 0

Mitaka translation, go!
by Ying Chun Guo 17 Mar '16

17 Mar '16

Hi, team According to the release schedule, Mitaka translation starts from today. In the home page of translation website[1], you can find the detail information of Mitaka translation plan. The plan includes 6 web projects and 8 backend projects. Mitaka translation will last for above 3 weeks, from March 4th to March 28th. Here are some points for your attention during translation. 1. We start translations after soft string freeze. It means there will be string changes while you are translating. So don't be surprise when you notice the percentage of translation progress becomes smaller. 2. The hard string freeze will happen in the week of March 14-18. Different projects have different exact time of hard freeze. After hard freeze, our translation work will switch from master version to mitaka version. The links in the translation plan in the home page will be changed correspondingly. So continue your translation work from links in the home page is a good practise. Also, I will send notice to mailing list when the switch happens. 3. After hard string freeze and switch to mitaka version, there will be very few string changes. We can get 10(almost) more days after hard string freeze to finish up the translations. Let's work together to make a great success of mitaka translation. If you have any questions or get into troubles, there are several ways to ask help from: 1. Get help from your local team through the local communication method 2. Go to #openstack-i18n 3. Send mail to I18n mailing list There is a whole team who are willing to help. Enjoy translations! Best regards Ying Chun Guo (Daisy) [1] http://translate.openstack.org

4 8

Cannot connect to Zanata
by Ilya Alekseyev 17 Mar '16

17 Mar '16

Dear colluegues, for some unknown reason i cannot connect to Zanata. Tried different browsers and it just don't work. Wonder if somebody have the same problems? Kind regards, Ilya Alekseyev

4 4

IRC meeting today
by Ying Chun Guo 17 Mar '16

17 Mar '16

Hi, team We will have IRC meeting today at UTC 1300 in #openstack-meeting. The agenda in my mind are: * Mitaka translation updates * Open discussions If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Ilya Alekseyev 16 Mar '16

16 Mar '16

Dear Daisy, Akihiro, Alex, thank you very much for your investigation and fix of this issue. Kind regards. Ilya Alekseyev 2016-03-15 10:14 GMT+03:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > I think you are right. > plural can be only set once. > After setting, it's not able to change. > > python-neutronclient is fixed. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/14/2016 07:21:10 PM: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev > > <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" > > <openstack-i18n(a)lists.openstack.org> > > Date: 03/14/2016 07:22 PM > > Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > > > Hi Daisy, > > > > 2016-03-14 17:33 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Hi, Akihiro > > > > > > I tried to upload a new Russian translation file with the correct > plural > > > formula to django-openstack-auth. > > > And then I downloaded it. Yet the header is not changed at all. > > > I'm afraid uploading po files will not change the header. > > > > I made some tests with nplurals. > > My conclusion is that Zanata allows to update nplurals ONLY ONCE. > > I succeed to change nplural to 2 by putting japanese PO file, but once > > it was changed, > > even though I put Japanese PO file with nplural==1, nplural was not > changed. > > > > I tested it using neutronclient Japanese. > > As an unfortunate result, Japanese resource in neutronclient now have > > the wrong nplurals (2). > > Could you reset neutronclient in Japanese? > > (There is no translation in neutronclient, so we can do this more easily > :-) > > > > Thanks, > > Akihiro > > > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/12/2016 09:13:09 PM: > > > > > >> From: Akihiro Motoki <amotoki(a)gmail.com> > > >> To: Ying Chun Guo/China/IBM@IBMCN > > >> Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev > > >> <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" > > >> <openstack-i18n(a)lists.openstack.org> > > >> Date: 03/12/2016 09:14 PM > > >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> > > >> Hi Daisy, Alex, > > >> > > >> I think the steps Daisy describes is the last resort. > > >> Regarding translation statistics, I have nothing to say as I don't > > >> know any about stats. > > >> > > >> There are a couple of things I would like to note. > > >> > > >> * It is better to first try to upload Russian PO files with > nplurals=3 > > >> even though you failed it last time. > > >> * We need to check other Russian resources other than Horizon. > > >> I checked django-openstack-auth and nova and they have nplurals=4. > > >> There might be more. > > >> At now only Horizon and dashboard-related projects use plural > cases, > > >> so we see this issue only in Horizon now. > > >> > > >> Akihiro > > >> > > >> > > >> > > >> 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> > Thank you for the investigation, Akihiro and Alex. > > >> > > > >> > Below are the steps we previously used. > > >> > We can follow the same steps, just changing "stable" version to > > > "master" > > >> > version. > > >> > I think the statistic data will not be affected in step 1 to 5. > > >> > But, if we delete master-old, the contribution data in master-old > will > > > be > > >> > removed. > > >> > So my suggestion is to do the same steps, and keep master-old > version > > > (mark > > >> > it as readonly) > > >> > till 6 month or 12 month later when the contribution data is not > that > > >> > important. > > >> > > > >> >> 1. Create Russian translation files with only the correct header > and > > > the > > >> >> pluralities translation items. > > >> >> 2. Create a new version named as russian-fix > > >> >> 3. Upload the source files and the Russian translation files > created > > > in #1 > > >> >> to the version russian-fix > > >> >> 4. Merge the stable version with version russian-fix > > >> >> 5. Rename stable version to stable-old, and rename russian-fix to > > > stable. > > >> > > > >> > Alex and Akihiro, please confirm my proposal. > > >> > Then I can take actions. > > >> > > > >> > Best regards > > >> > Ying Chun Guo (Daisy) > > >> > > > >> > > > >> > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: > > >> > > > >> >> From: Alex Eng <aeng(a)redhat.com> > > >> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> > > >> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ > > >> >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- > > >> >> i18n(a)lists.openstack.org> > > >> >> Date: 2016/03/11 04:37 > > >> >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian > > >> > > > >> > > > >> >> > > >> >> Hi, > > >> >> > > >> >> If we fix the plural forms in pot file and push to Zanata, that > > >> >> would not affect the statistics. > > >> >> > > >> >> But I remember last time when we trying to fix this, there are > some > > >> >> limitation of the pluralform wont update after the file is being > > >> >> uploaded once to Zanata. And we have to create a new version with > > >> >> fixed pot file and use "merge translation" feature to bring over > all > > >> >> the translations. > > >> >> > > >> >> We can do the same thing again and the statistics won't be > affected. > > >> >> (copied translation doesn't count in as contribution) > > >> >> > > >> >> I checked and Zanata has the correct form. > > >> >> > > >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 > && > > >> >> (n%100<10 || n%100>=20) ? 1 : 2) > > >> >> > > >> >> --------------------------------------------- > > >> >> > > >> >> Alex Eng > > >> >> Senior Software Engineer > > >> >> Globalisation Tools Engineering > > >> >> DID: +61 3514 8262 > > >> >> Mobile: +614 2335 3457 > > >> >> > > >> >> Red Hat, Asia-Pacific Pty Ltd > > >> >> Level 1, 193 North Quay > > >> >> Brisbane 4000 > > >> >> Office: +61 7 3514 8100 > > >> >> Fax: +61 7 3514 8199 > > >> >> Website: www.redhat.com > > >> >> > > >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev > > > <ilyaalekseyev(a)acm.org> > > >> >> wrote: > > >> >> Daisy, > > >> >> > > >> >> i remember we fixed this for Liberty. But looks like somewhere > wrong > > >> >> config or error in script that creating master version. > > >> >> How ca we fix it? How i can help with this issue? > > >> >> > > >> >> Alex, is it possible to fix plural formula ofr version and keep > > >> >> statistics safe? > > >> >> > > >> >> We need to fix it as soon as possible, because 4 plural forms > making > > >> >> issues for russian translation (empty message, empty buttons, etc, > > >> >> as we can seee in Kilo release). > > >> >> > > >> >> Kind regards, > > >> >> Ilya Alekseyev. > > >> >> > > >> >> С уважением, > > >> >> Илья Алексеев > > >> >> > > >> >> Russian OpenStack Community > > >> >> > > >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: > > >> >> Russian translations in the horizon repo is downloaded from > Zanata, > > >> >> OpenStack translation platform. > > >> >> It seems Zanata has wrong plural configuration. > > >> >> > > >> >> > Daisy, Alex, > > >> >> Could you check Russian configuration in Zanata is correct? > > >> >> > > >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: > > >> >> > Dear collegues, > > >> >> > > > >> >> > i've checked current russian translation in horizon repository > and > > > find > > >> >> > out > > >> >> > that we have wrong plural formula in upstream. > > >> >> > > > >> >> > https://github.com/openstack/horizon/blob/master/ > > >> >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 > > >> >> > > > >> >> > There is only 3 plural forms in Russian. > > >> >> > And correct formula should be > > >> >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && > n%10<=4 > > > && > > >> >> > (n%100<10 || n%100>=20) ? 1 : 2); > > >> >> > > > >> >> > Looks like some script is wrong. > > >> >> > Does anybody know how to fix it? > > >> >> > > > >> >> > Kind regards, > > >> >> > Ilya Alekseyev > > >> >> > > > >> >> > _______________________________________________ > > >> >> > Openstack-i18n mailing list > > >> >> > Openstack-i18n(a)lists.openstack.org > > >> >> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >> >> > > > >> > > > > > > > > > > >

1 0

Re: [Openstack-i18n] Wrong plural formula for russian
by Akihiro Motoki 15 Mar '16

15 Mar '16

Hi Daisy, 2016-03-14 17:33 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Hi, Akihiro > > I tried to upload a new Russian translation file with the correct plural > formula to django-openstack-auth. > And then I downloaded it. Yet the header is not changed at all. > I'm afraid uploading po files will not change the header. I made some tests with nplurals. My conclusion is that Zanata allows to update nplurals ONLY ONCE. I succeed to change nplural to 2 by putting japanese PO file, but once it was changed, even though I put Japanese PO file with nplural==1, nplural was not changed. I tested it using neutronclient Japanese. As an unfortunate result, Japanese resource in neutronclient now have the wrong nplurals (2). Could you reset neutronclient in Japanese? (There is no translation in neutronclient, so we can do this more easily :-) Thanks, Akihiro > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 03/12/2016 09:13:09 PM: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: Ying Chun Guo/China/IBM@IBMCN >> Cc: Alex Eng <aeng(a)redhat.com>, Ilya Alekseyev >> <ilyaalekseyev(a)acm.org>, "openstack-i18n(a)lists.openstack.org" >> <openstack-i18n(a)lists.openstack.org> >> Date: 03/12/2016 09:14 PM >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian >> >> Hi Daisy, Alex, >> >> I think the steps Daisy describes is the last resort. >> Regarding translation statistics, I have nothing to say as I don't >> know any about stats. >> >> There are a couple of things I would like to note. >> >> * It is better to first try to upload Russian PO files with nplurals=3 >> even though you failed it last time. >> * We need to check other Russian resources other than Horizon. >> I checked django-openstack-auth and nova and they have nplurals=4. >> There might be more. >> At now only Horizon and dashboard-related projects use plural cases, >> so we see this issue only in Horizon now. >> >> Akihiro >> >> >> >> 2016-03-11 14:20 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > Thank you for the investigation, Akihiro and Alex. >> > >> > Below are the steps we previously used. >> > We can follow the same steps, just changing "stable" version to > "master" >> > version. >> > I think the statistic data will not be affected in step 1 to 5. >> > But, if we delete master-old, the contribution data in master-old will > be >> > removed. >> > So my suggestion is to do the same steps, and keep master-old version > (mark >> > it as readonly) >> > till 6 month or 12 month later when the contribution data is not that >> > important. >> > >> >> 1. Create Russian translation files with only the correct header and > the >> >> pluralities translation items. >> >> 2. Create a new version named as russian-fix >> >> 3. Upload the source files and the Russian translation files created > in #1 >> >> to the version russian-fix >> >> 4. Merge the stable version with version russian-fix >> >> 5. Rename stable version to stable-old, and rename russian-fix to > stable. >> > >> > Alex and Akihiro, please confirm my proposal. >> > Then I can take actions. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Alex Eng <aeng(a)redhat.com> wrote on 2016/03/11 04:36:15: >> > >> >> From: Alex Eng <aeng(a)redhat.com> >> >> To: Ilya Alekseyev <ilyaalekseyev(a)acm.org> >> >> Cc: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun Guo/China/ >> >> IBM@IBMCN, "openstack-i18n(a)lists.openstack.org" <openstack- >> >> i18n(a)lists.openstack.org> >> >> Date: 2016/03/11 04:37 >> >> Subject: Re: [Openstack-i18n] Wrong plural formula for russian >> > >> > >> >> >> >> Hi, >> >> >> >> If we fix the plural forms in pot file and push to Zanata, that >> >> would not affect the statistics. >> >> >> >> But I remember last time when we trying to fix this, there are some >> >> limitation of the pluralform wont update after the file is being >> >> uploaded once to Zanata. And we have to create a new version with >> >> fixed pot file and use "merge translation" feature to bring over all >> >> the translations. >> >> >> >> We can do the same thing again and the statistics won't be affected. >> >> (copied translation doesn't count in as contribution) >> >> >> >> I checked and Zanata has the correct form. >> >> >> >> nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && >> >> (n%100<10 || n%100>=20) ? 1 : 2) >> >> >> >> --------------------------------------------- >> >> >> >> Alex Eng >> >> Senior Software Engineer >> >> Globalisation Tools Engineering >> >> DID: +61 3514 8262 >> >> Mobile: +614 2335 3457 >> >> >> >> Red Hat, Asia-Pacific Pty Ltd >> >> Level 1, 193 North Quay >> >> Brisbane 4000 >> >> Office: +61 7 3514 8100 >> >> Fax: +61 7 3514 8199 >> >> Website: www.redhat.com >> >> >> >> On Fri, Mar 11, 2016 at 3:00 AM, Ilya Alekseyev > <ilyaalekseyev(a)acm.org> >> >> wrote: >> >> Daisy, >> >> >> >> i remember we fixed this for Liberty. But looks like somewhere wrong >> >> config or error in script that creating master version. >> >> How ca we fix it? How i can help with this issue? >> >> >> >> Alex, is it possible to fix plural formula ofr version and keep >> >> statistics safe? >> >> >> >> We need to fix it as soon as possible, because 4 plural forms making >> >> issues for russian translation (empty message, empty buttons, etc, >> >> as we can seee in Kilo release). >> >> >> >> Kind regards, >> >> Ilya Alekseyev. >> >> >> >> С уважением, >> >> Илья Алексеев >> >> >> >> Russian OpenStack Community >> >> >> >> 2016-03-10 19:37 GMT+03:00 Akihiro Motoki <amotoki(a)gmail.com>: >> >> Russian translations in the horizon repo is downloaded from Zanata, >> >> OpenStack translation platform. >> >> It seems Zanata has wrong plural configuration. >> >> >> >> > Daisy, Alex, >> >> Could you check Russian configuration in Zanata is correct? >> >> >> >> 2016-03-10 22:42 GMT+09:00 Ilya Alekseyev <ilyaalekseyev(a)acm.org>: >> >> > Dear collegues, >> >> > >> >> > i've checked current russian translation in horizon repository and > find >> >> > out >> >> > that we have wrong plural formula in upstream. >> >> > >> >> > https://github.com/openstack/horizon/blob/master/ >> >> openstack_dashboard/locale/ru/LC_MESSAGES/django.po#L35-L37 >> >> > >> >> > There is only 3 plural forms in Russian. >> >> > And correct formula should be >> >> > nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 > && >> >> > (n%100<10 || n%100>=20) ? 1 : 2); >> >> > >> >> > Looks like some script is wrong. >> >> > Does anybody know how to fix it? >> >> > >> >> > Kind regards, >> >> > Ilya Alekseyev >> >> > >> >> > _______________________________________________ >> >> > Openstack-i18n mailing list >> >> > Openstack-i18n(a)lists.openstack.org >> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> > >> > >

2 1

GILT in Curriculum
by Rajesh Ranjan 14 Mar '16

14 Mar '16

Hi We, FUEL Community [1], are in discussion with SICSR [2] and some other institutes to introduce a formal curriculum on GILT (Globalization, Internationalization, Localization, Translation) technology which can be taught either as short term or long term course. This was outcome of discussions at past FUEL GILT Conference and FUEL meetings in Gnunify. Please refer the mail by Karunakar: https://lists.fedorahosted.org/archives/list/fuel-discuss@lists.fedorahoste… Please check the draft curriculum link: https://docs.google.com/document/d/1M4KgUy4VOU8aIlo8XT-C7HW2no_B0B5ZhkM69TZ… You are invited to contribution in the formation of the curriculum and take any chapter/sub chapter. Your suggestions are also welcome! Like all the content of FUEL Project, the content of the curriculum will be under open license. This is a unique activity and will help GILT technology. Thanks [1]. http://fuelproject.org/ [2]. http://sicsr.ac.in/ -- *Rajesh Ranjan* Open Source Community Manager Digital India, Govt. of India https://twitter.com/kajha

1 0