<html><body><p>Thank you, Andreas and team.<br>I will update according to Andreas suggestion.<br><br>Best regards<br>Ying Chun Guo (Daisy)<br><br><br><tt>Andreas Jaeger <aj@suse.com> wrote on 2015/11/11 23:24:05:<br><br>> From: Andreas Jaeger <aj@suse.com></tt><br><tt>> To: Openstack-i18n <openstack-i18n@lists.openstack.org></tt><br><tt>> Date: 2015/11/11 23:24</tt><br><tt>> Subject: Re: [Openstack-i18n] Terminologies in repo</tt><br><tt>> <br>> On 11/11/2015 04:00 PM, KATO Tomoyuki wrote:<br>> >> On 11/11/2015 11:10 AM, Ying Chun Guo wrote:<br>> >>> Hello, team<br>> >>><br>> >>> I have submitted a patch to our repo for review, containing all the<br>> >>> terminologies and translations we made.<br>> >>> <a href="https://review.openstack.org/244031">https://review.openstack.org/244031</a><br>> >>> I want to discuss about how to handle these assets we made.<br>> >>><br>> >>> Currently, I use a google doc to store the terms and the translations.<br>> >>> <a href="https://docs.google.com/spreadsheets/d/">https://docs.google.com/spreadsheets/d/</a><br>> 1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9IcyurGdrQ/edit#gid=0<br>> >>> I want to move these assets to our repo.<br>> >>><br>> >>> My plan is to use pot and po files to store the terms and the <br>> translations.<br>> >>> Then create a project named as "terminology" in Zanata, and<br>> >>> create auto jobs to manage the synchronization between i18n repo and<br>> >>> Zanata.<br>> >>><br>> >>> So the process to update terms are:<br>> >>> - If a people wants to add a new term to the terminology,<br>> >>> submit a patch to i18n repo to change the original term.pot file.<br>> >>> - If a people want to update a translation of a term,<br>> >>> go to Zanata to update the translation.<br>> >>><br>> >>> Let me know your thoughts to my design.<br>> >>> Thank you.<br>> >><br>> >> Zanato comes with its own glossary support which is AFAIU the same as<br>> >> the terminology.<br>> >><br>> >> Do you want to import the terminology as the Zanata glossary?<br>> >> Or should the glossary be only handled directly in Zanata withoutthe repo?<br>> ><br>> > In a short word, yes.<br>> > We want to use them as the Zanata glossary, and translate them in Zanata.<br>> > Also, we want to maintain them at i18n repo as an official resource.<br>> ><br>> > We are trying to create a tool that upload them to Zanata as the <br>> Zanata glossary.<br>> ><br>> > To keep track all work, we have a blueprint:<br>> > <a href="https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary">https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary</a><br>> > (not approved yet :-)<br>> <br>> Great!<br>> <br>> I've commented on Daisy's change. I suggest to follow the same directory <br>> layout we do for translation files everywhere - that allows easier reuse <br>> of our infra scripts,<br>> <br>> Andreas<br>> -- <br>> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi<br>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>> GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>> HRB 21284 (AG Nürnberg)<br>> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>> <br>> <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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>> <br></tt><BR>
</body></html>