<html><body>
<p><font size="2" face="sans-serif">You are correct.</font><br>
<font size="2" face="sans-serif">It looks like the source language was setting when creating the project.</font><br>
<br>
<font size="2" face="sans-serif">Regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<tt><font size="2">Tom Fifield <tom@openstack.org> wrote on 2013/08/29 13:21:48:<br>
<br>
> Tom Fifield <tom@openstack.org> </font></tt><br>
<tt><font size="2">> 2013/08/29 13:21</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo/China/IBM@IBMCN, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> openstack-infra@lists.openstack.org</font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [OpenStack-Infra] Need help on Transifex setting</font></tt><br>
<tt><font size="2">> <br>
> On 29/08/13 15:15, Ying Chun Guo wrote:<br>
> > Thanks for looking into it again.<br>
> ><br>
> > Regards<br>
> > Ying Chun Guo (Daisy)<br>
> ><br>
> > Tom Fifield <tom@openstack.org> wrote on 2013/08/29 12:42:05:<br>
> ><br>
> > > Tom Fifield <tom@openstack.org><br>
> > > 2013/08/29 12:42<br>
> > ><br>
> > > To<br>
> > ><br>
> > > openstack-infra@lists.openstack.org,<br>
> > ><br>
> > > cc<br>
> > ><br>
> > > Subject<br>
> > ><br>
> > > Re: [OpenStack-Infra] Need help on Transifex setting<br>
> > ><br>
> > > On 21/08/13 16:33, Ying Chun Guo wrote:<br>
> > > > Hi,<br>
> > > ><br>
> > > > Translation team wants to set shared glossary among all OpenStack<br>
> > > > projects in Transifex.<br>
> > > > Recently, Transifex introduced "Organization". The same glossary or TM<br>
> > > > can be used across<br>
> > > > multiple projects belonging to the same organization. It��s possible to<br>
> > > > designate specific<br>
> > > > users as Organization Administrators. Each admin will be ableto manage<br>
> > > > glossary sharing<br>
> > > > details[1]. The glossary can be bootstrapped by uploading a CSV file.<br>
> > > ><br>
> > > > The glossary can be only shared among projects with the same source<br>
> > > > language. Now under<br>
> > > > OpenStack, the source language of some projects (Cinder, Glance,<br>
> > > > Horizon, and Nova) are "en_US",<br>
> > > > and the source language of the others are "en". The source language<br>
> > > > "en_US" may cause issues. We<br>
> > > > knew 1 bug[2] in Horizon.<br>
> > > ><br>
> > > > So I need help to<br>
> > > > * An admin to create a shared glossary among all projects under<br>
> > > > "OpenStack". The initial CSV file<br>
> > > > can be gotten from translation team.<br>
> > ><br>
> > > Since we still have the en vs en_US problem, I have merged the<br>
> > > glossaries into two:<br>
> > ><br>
> > ><br>
> > > openstack_2012-08-02 (English)<br>
> > ><br>
> > > Ceilometer Heat Keystone Neutron OpenStack OpenStack Manuals savanna<br>
> > ><br>
> ><br>
> > French team is working on the glossary importing.<br>
> > I think they are importing to the previous glossary used by openstack hub.<br>
> > I don't know if it is openstack_2012-08-02 (English).<br>
> > If you did some check, I trust you.<br>
> ><br>
> > > horizon_2012-08-17 (English (United States))<br>
> > ><br>
> > > Cinder Glance Horizon Nova<br>
> > ><br>
> ><br>
> > At last, we need to use only 1 glossary.<br>
> > So we'd better to change the source language to English.<br>
> ><br>
> > ><br>
> > > > * Change the source language of projects from "en_US" to "en". It<br>
> > cannot<br>
> > > > be changed directly. The<br>
> > > > new source file with source language as "en" has to be uploaded to<br>
> > > > replace the old one by manual.<br>
> > ><br>
> > > My understanding on what we need to do here is:<br>
> > ><br>
> > > eg for Nova<br>
> > ><br>
> > > 0. Backup translations from nova project<br>
> > > 1. Create a new project nova-new<br>
> > > 2. Upload new translation source to nova-new, using language=en<br>
> > > 3. Upload the translation backup to nova-new<br>
> > > 4. test that translations have restored from backup OK<br>
> > > 5. Rename nova to nova-old<br>
> > > 6. Rename nova-new to nova<br>
> > > 7. Test that everything in the toolchain works<br>
> > > 8. delete nova-old<br>
> > ><br>
> > > Repeat for: Cinder Glance Horizon<br>
> > ><br>
> > > Does that make sense?<br>
> > ><br>
> ><br>
> > I have plan to update the source language of Horizon by the following steps:<br>
> > Step 1. Pull the all of the translation results from Transifex.<br>
> > Step 2. Create new translation resources in Transifex based on the PO<br>
> > files in Github, with source language setting as "en".<br>
> > Step 3. Update the translation results to the latest version and push to<br>
> > Transifex.<br>
> ><br>
> > I don't know if I can success.<br>
> > I will let you know the result, then we can broadcast to openstack<br>
> > mailing list and<br>
> > ask the owner or the maintainer to do the same to Nova, Cinder and Glance.<br>
> <br>
> I noticed that the source language is set when the project is created, <br>
> so maybe it needs new projects to fix this :(<br>
> <br>
> I am trying a test import now with <br>
> <a href="https://www.transifex.com/projects/p/nova-new/">https://www.transifex.com/projects/p/nova-new/</a> - but for some reason the <br>
> TMX upload has only done English, even though all other translations are <br>
> in the downloaded TMX file.<br>
> <br>
> It did say it was a background process that "took some time", but I <br>
> worry maybe the all-language TMX is too large.<br>
> <br>
> I am playing a bit more.<br>
> <br>
> <br>
> > ><br>
> > > One other note from clarkb: where we do an extract_catalog in the<br>
> > > jenkins scripts we may need to enforce the source locale [so it's always<br>
> > > set consistently]<br>
> > ><br>
> ><br>
> > Sorry, I cannot understand.<br>
> ><br>
> > ><br>
> > ><br>
> > > Regards,<br>
> > ><br>
> > > Tom<br>
> > ><br>
> > ><br>
> > ><br>
> > > ><br>
> > > > Please let me know if anybody can help.<br>
> > > ><br>
> > > > Thanks and regards<br>
> > > > Ying Chun Guo (Daisy)<br>
> > > ><br>
> > > > [1]: <a href="http://blog.transifex.com/post/57712611874/organizations">http://blog.transifex.com/post/57712611874/organizations</a><br>
> > > > [2]: <a href="https://bugs.launchpad.net/horizon/+bug/1179526">https://bugs.launchpad.net/horizon/+bug/1179526</a><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > OpenStack-Infra mailing list<br>
> > > > OpenStack-Infra@lists.openstack.org<br>
> > > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
> > > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > OpenStack-Infra mailing list<br>
> > > OpenStack-Infra@lists.openstack.org<br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
> ><br>
> <br>
</font></tt></body></html>