Hello, team I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made. Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... I want to move these assets to our repo. My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata. So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation. Let me know your thoughts to my design. Thank you. Best regards Ying Chun Guo (Daisy)
Thanks Daisy for moving this forward. Your plan sounds good to me. btw, I noticed that Japanese terminologies are completely out-of-date :-( We need to update it soon. Akihiro 2015-11-11 19:10 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Hello, team
I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made.
Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... I want to move these assets to our repo.
My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata.
So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation.
Let me know your thoughts to my design. Thank you.
Best regards Ying Chun Guo (Daisy)
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 11/11/2015 11:10 AM, Ying Chun Guo wrote:
Hello, team
I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made.
Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... I want to move these assets to our repo.
My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata.
So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation.
Let me know your thoughts to my design. Thank you.
Zanato comes with its own glossary support which is AFAIU the same as the terminology. Do you want to import the terminology as the Zanata glossary? Or should the glossary be only handled directly in Zanata without the repo? Andreas -- Andreas Jaeger aj@{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
On 11/11/2015 11:10 AM, Ying Chun Guo wrote:
Hello, team
I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made.
Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... I want to move these assets to our repo.
My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata.
So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation.
Let me know your thoughts to my design. Thank you.
Zanato comes with its own glossary support which is AFAIU the same as the terminology.
Do you want to import the terminology as the Zanata glossary? Or should the glossary be only handled directly in Zanata without the repo?
In a short word, yes. We want to use them as the Zanata glossary, and translate them in Zanata. Also, we want to maintain them at i18n repo as an official resource. We are trying to create a tool that upload them to Zanata as the Zanata glossary. To keep track all work, we have a blueprint: https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary (not approved yet :-) Thanks, KATO Tomoyuki
Hi :-) Korean terminology is out-of-date too..... Need update! :-) Thanks, Sungjin Kang 2015-11-12 0:00 GMT+09:00 KATO Tomoyuki <tomo@dream.daynight.jp>:
On 11/11/2015 11:10 AM, Ying Chun Guo wrote:
Hello, team
I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made.
Currently, I use a google doc to store the terms and the translations.
I want to move these assets to our repo.
My plan is to use pot and po files to store the terms and the
https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... translations.
Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata.
So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation.
Let me know your thoughts to my design. Thank you.
Zanato comes with its own glossary support which is AFAIU the same as the terminology.
Do you want to import the terminology as the Zanata glossary? Or should the glossary be only handled directly in Zanata without the repo?
In a short word, yes. We want to use them as the Zanata glossary, and translate them in Zanata. Also, we want to maintain them at i18n repo as an official resource.
We are trying to create a tool that upload them to Zanata as the Zanata glossary.
To keep track all work, we have a blueprint: https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary (not approved yet :-)
Thanks, KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 11/11/2015 04:00 PM, KATO Tomoyuki wrote:
On 11/11/2015 11:10 AM, Ying Chun Guo wrote:
Hello, team
I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made.
Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... I want to move these assets to our repo.
My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata.
So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation.
Let me know your thoughts to my design. Thank you.
Zanato comes with its own glossary support which is AFAIU the same as the terminology.
Do you want to import the terminology as the Zanata glossary? Or should the glossary be only handled directly in Zanata without the repo?
In a short word, yes. We want to use them as the Zanata glossary, and translate them in Zanata. Also, we want to maintain them at i18n repo as an official resource.
We are trying to create a tool that upload them to Zanata as the Zanata glossary.
To keep track all work, we have a blueprint: https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary (not approved yet :-)
Great! I've commented on Daisy's change. I suggest to follow the same directory layout we do for translation files everywhere - that allows easier reuse of our infra scripts, Andreas -- Andreas Jaeger aj@{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
From: Andreas Jaeger <aj@suse.com> To: Openstack-i18n <openstack-i18n@lists.openstack.org> Date: 2015/11/11 23:24 Subject: Re: [Openstack-i18n] Terminologies in repo
On 11/11/2015 04:00 PM, KATO Tomoyuki wrote:
On 11/11/2015 11:10 AM, Ying Chun Guo wrote:
Hello, team
I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made.
Currently, I use a google doc to store the terms and the
Thank you, Andreas and team. I will update according to Andreas suggestion. Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 2015/11/11 23:24:05: translations.
https://docs.google.com/spreadsheets/d/ 1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9IcyurGdrQ/edit#gid=0 I want to move these assets to our repo.
My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata.
So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation.
Let me know your thoughts to my design. Thank you.
Zanato comes with its own glossary support which is AFAIU the same as the terminology.
Do you want to import the terminology as the Zanata glossary? Or should the glossary be only handled directly in Zanata withoutthe repo?
In a short word, yes. We want to use them as the Zanata glossary, and translate them in Zanata. Also, we want to maintain them at i18n repo as an official resource.
We are trying to create a tool that upload them to Zanata as the Zanata glossary.
To keep track all work, we have a blueprint:
https://blueprints.launchpad.net/openstack-i18n/+spec/translation-glossary
(not approved yet :-)
Great!
I've commented on Daisy's change. I suggest to follow the same directory layout we do for translation files everywhere - that allows easier reuse of our infra scripts,
Andreas -- Andreas Jaeger aj@{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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (5)
-
Akihiro Motoki
-
Andreas Jaeger
-
KATO Tomoyuki
-
SungJin Kang
-
Ying Chun Guo