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