Hello, In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources. Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic... Best regards Ying Chun Guo (Daisy)
Hi Daisy, that's an excellent idea and thanks for taking the action! I assume this is going to be extended by several other languages and consequently will significantly grow. How do you expect this to be maintained? Is there some version control and the option to see who's working on it? Not sure if google docs provides that ... I guess we're going to do a translation freeze for the terminologies before working on the rest of the content, is that the idea? -- Regards, Robert On Thursday 18 June 2015, 17:44:40 Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Hello,
In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources.
Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic yurGdrQ/edit?usp=sharing
Best regards Ying Chun Guo (Daisy)
On 06/18/2015 12:04 PM, Robert Simai wrote:
Hi Daisy,
that's an excellent idea and thanks for taking the action!
I assume this is going to be extended by several other languages and consequently will significantly grow. How do you expect this to be maintained? Is there some version control and the option to see who's working on it? Not sure if google docs provides that ...
Setting up a git repository on git.openstack.org is one way of doing it.
I guess we're going to do a translation freeze for the terminologies before working on the rest of the content, is that the idea?
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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hello, I think, it would be better to create a project on Transifex Best, F. Le 18/06/2015 14:12, Andreas Jaeger a écrit :
On 06/18/2015 12:04 PM, Robert Simai wrote:
Hi Daisy,
that's an excellent idea and thanks for taking the action!
I assume this is going to be extended by several other languages and consequently will significantly grow. How do you expect this to be maintained? Is there some version control and the option to see who's working on it? Not sure if google docs provides that ...
Setting up a git repository on git.openstack.org is one way of doing it.
I guess we're going to do a translation freeze for the terminologies before working on the rest of the content, is that the idea?
Andreas
Hello All, On Thu, Jun 18, 2015 at 5:44 PM, François Bureau < francois.bureau@cloudwatt.com> wrote:
Hello,
I think, it would be better to create a project on Transifex
Best,
F.
Le 18/06/2015 14:12, Andreas Jaeger a écrit :
On 06/18/2015 12:04 PM, Robert Simai wrote:
Hi Daisy,
that's an excellent idea and thanks for taking the action!
I assume this is going to be extended by several other languages and consequently will significantly grow. How do you expect this to be maintained? Is there some version control and the option to see who's working on it? Not sure if google docs provides that ...
Setting up a git repository on git.openstack.org is one way of doing it.
I guess we're going to do a translation freeze for the terminologies
before working on the rest of the content, is that the idea?
There is already a list of cloud terminology created by fuel project. I think we can look at this: https://fedorahosted.org/fuel/wiki/fuel-terminology/fuel-cloud
Here is the terminology link: https://git.fedorahosted.org/cgit/fuel.git/tree/language/en/terminology/clou... It is already getting translated in various language: http://fuelproject.org/stats/index (open this url, under cloud section, click on icons, it will take you to the translated version.) This project is also available on pootle/zanata for translation.: https://translate.zanata.org/zanata/iteration/view/fuel-project/FUEL-cloud Please have a look Thanks, Chandan Kumar
Hello, since we're transfering from Transifex to Zanata, may be create a project in Zenata? Git repo works for me as well. Kind regards, Ilya Alekseyev. 2015-06-18 15:14 GMT+03:00 François Bureau <francois.bureau@cloudwatt.com>:
Hello,
I think, it would be better to create a project on Transifex
Best,
F.
Le 18/06/2015 14:12, Andreas Jaeger a écrit :
On 06/18/2015 12:04 PM, Robert Simai wrote:
Hi Daisy,
that's an excellent idea and thanks for taking the action!
I assume this is going to be extended by several other languages and consequently will significantly grow. How do you expect this to be maintained? Is there some version control and the option to see who's working on it? Not sure if google docs provides that ...
Setting up a git repository on git.openstack.org is one way of doing it.
I guess we're going to do a translation freeze for the terminologies
before working on the rest of the content, is that the idea?
Andreas
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hello Daisy, I am happily sharing this Korean terminologies. Ujuc and me added the Korean part. Please see the link: https://docs.google.com/spreadsheets/d/1w0JWJ3LJEeH9xmyWfKP_UA6zcTWfh6q2LRzm... Please reflect Korean terminoligies to the URL you shared to us. With many thanks, /Ian (IRC: ianychoi) Ying Chun Guo wrote on 6/18/2015 6:44 PM:
Hello,
In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources.
Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9Ic...
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
Thank you all for the comments. In the IRC meeting yesterday, we discussed about terminologies and the feedback. Here are the summaries. 1. Using singular or plural ? Agreement: singular only 2. Starting with capital letter or lower case letter ? Agreement: all letters non-capital except abbreviations 3. Do we need version control? Agreement: Yes, we will use git to store these terminologies. Translation tool ( Zanata or Transifex ) will be used for translate these terminologies. 4. Do we want string freeze management for terminologies? Agreement: No, there is no string freeze for terminologies. 5. Maintaining Agreement: If somebody wants to change a term, remove a term or add new terms, submit a patch to the git repo. I18n team will vote through Girret. If somebody wants to change a term translation, please discuss within local translation team to get team agreement. Any feedback is welcomed. If you have different opinions, please let the team know. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM@IBMCN wrote on 2015/06/18 17:44:40:
From: Ying Chun Guo/China/IBM@IBMCN To: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Date: 2015/06/18 17:45 Subject: [Openstack-i18n] Terminologies
Hello,
In Vancouver translation workshop, we decided to compose the translation terminologies. I merged the terminologies used by Japanese team, German team and French team and made out the first version of translation terms. When we generate it, terminology will be the first contents to be translated in any translation teams. It is a good way to get the consistency among different translators and different translation resources.
Please take a look and let me know if you have any comments and suggestions. https://docs.google.com/spreadsheets/d/ 1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9IcyurGdrQ/edit?usp=sharing
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 06/19/2015 07:40 AM, Ying Chun Guo wrote:
[...] 3. Do we need version control? Agreement: Yes, we will use git to store these terminologies. Translation tool ( Zanata or Transifex ) will be used for translate these terminologies.
The Infra Manual describes how to setup a git repository in our CI infrastructure: http://docs.openstack.org/infra/manual/creators.html If you need any help with that, please ask, 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Friday 19 June 2015, 13:40:28 Ying Chun Guo <guoyingc@cn.ibm.com> wrote (shortened):
Thank you all for the comments. In the IRC meeting yesterday, we discussed about terminologies and the feedback. Here are the summaries.
LGTM, just two remarks:
1. Using singular or plural ? Agreement: singular only
I don't know how the Transifex/Zanata/whatsoever setup is progressing and what's feasible but I wonder if the translators can finally have some highlighting of the available terminologies in the to be translated strings. I believe that would really help to avoid looking up these manually and consequently to improve consistency and quality, in particular if somebody new starts. It however requires singular _and_ plural. I recommend to rethink this and the overhead seem low.
4. Do we want string freeze management for terminologies? Agreement: No, there is no string freeze for terminologies.
In case you've discussed this because of my comment, apparently I was talking about freezing the term translations to make sure we keep consistency and I understand it should be with the local teams. Thanks! -- Regards, Robert
participants (7)
-
Andreas Jaeger
-
chandan kumar
-
François Bureau
-
Ian Y. Choi
-
Ilya Alekseyev
-
Robert Simai
-
Ying Chun Guo