To language team coordinators: get ready for Mitaka translation
Dear coordinators, Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on. Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects. Before Mitaka translation starts, there are several things you can do: 1. Update glossary. If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly. 2. Document your local team communication method in the team wiki page[2]. While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together. 3. Join IRC channel[3] #openstack-i18n with your zanata ID As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles. If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
Thanks Daisy for initiating this. 2016-02-25 17:53 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
I would like to raise a question how the glossary work? Is it actually working? As one of coordinators of Japanese team, the glossary list itself is out-of-date. In addition to update per-language glossary, can we update a list of glossary itself? Beyond this, the current format of PO file for the glossary lacks an essential feature as I described before. There is no way to describe the context. I wonder how the glossary help translations without the contextual information. As a result, Japanese team is forced to describe contextual information in translated strings. This is the reason we preferred to Wiki style glossary.
From the above observation, does it sound a good option to clear the whole entry of Zanata glossary of a specific language?
2. Document your local team communication method in the team wiki page[2].
While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together.
I missed the previous team meeting (it is not special to me due to the meeting time). I would like to make some follow-up comments on a local communication. I personally would like to continue to use Gitter (hosted by Github) as a communication channel in Japanese team. From my past experience, it has various good merits. I felt the first point is really useful in the crunch time of Liberty translation reviews. * Pros: * it has a notification mechanism. Unread messages will be notified via email. * It can be used via browser (without any extra application) * Unlimited archive as long as gitter room is open to everyone * Cons * it is not provided by OpenStack infra Kato-san and Japanese team members, feel free to comment it. Your feedbacks would be really appreciated.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
"with Zanata ID"? It is just an option. It is not a requirement. It is not a surprising thing someone uses an IRC nickname different from Zanata ID. Note that it is important we need to know each other who you are but it is not a requirement to use Zanata ID as IRC nickname if you already use a different IRC nick.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n.
I can help you too. My nick is 'amotoki'. I am usually online from 0200UTC to 1600UTC. # It will be easier to find me compared to finding Daisy on IRC :) # Just joking.. never mind Daisy! Akihiro
Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Thanks Daisy for initiating this.
2016-02-25 17:53 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
I would like to raise a question how the glossary work? Is it actually working?
As one of coordinators of Japanese team, the glossary list itself is out-of-date. In addition to update per-language glossary, can we update a list of glossary itself?
Beyond this, the current format of PO file for the glossary lacks an essential feature as I described before. There is no way to describe the context. I wonder how the glossary help translations without the contextual information. As a result, Japanese team is forced to describe contextual information in translated strings. This is the reason we preferred to Wiki style glossary.
From the above observation, does it sound a good option to clear the whole entry of Zanata glossary of a specific language?
+1 to clear, as long as Japanese, as of now.
2. Document your local team communication method in the team wiki page[2].
While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together.
I missed the previous team meeting (it is not special to me due to the meeting time). I would like to make some follow-up comments on a local communication.
I personally would like to continue to use Gitter (hosted by Github) as a communication channel in Japanese team. From my past experience, it has various good merits. I felt the first point is really useful in the crunch time of Liberty translation reviews.
* Pros: * it has a notification mechanism. Unread messages will be notified via email. * It can be used via browser (without any extra application) * Unlimited archive as long as gitter room is open to everyone * Cons * it is not provided by OpenStack infra
Kato-san and Japanese team members, feel free to comment it. Your feedbacks would be really appreciated.
I agree to using Gitter in Japanese team. In my understand, using IRC channel for local team is not mandatory, just an option.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
"with Zanata ID"? It is just an option. It is not a requirement. It is not a surprising thing someone uses an IRC nickname different from Zanata ID.
I'm using different IDs :) And, I'm not always join IRC because of my business reason and equipments. To coordinate my local language team, I'd like to use Gitter and local mailing list. Regards, KATO Tomoyuki
Note that it is important we need to know each other who you are but it is not a requirement to use Zanata ID as IRC nickname if you already use a different IRC nick.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n.
I can help you too. My nick is 'amotoki'. I am usually online from 0200UTC to 1600UTC.
# It will be easier to find me compared to finding Daisy on IRC :) # Just joking.. never mind Daisy!
Akihiro
Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki < kato.tomoyuki@jp.fujitsu.com> wrote:
Beyond this, the current format of PO file for the glossary lacks an essential feature as I described before. There is no way to describe the context. I wonder how the glossary help translations without the contextual information. As a result, Japanese team is forced to describe contextual information in translated strings. This is the reason we preferred to Wiki style glossary.
From the above observation, does it sound a good option to clear the whole entry of Zanata glossary of a specific language?
FYI, as of Zanata 3.8, we support same source string with unique "description" and "pos" field for each glossary entry. This will help translator with more context information and able to have similar string with different context. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
2016-02-29 6:58 GMT+09:00 Alex Eng <aeng@redhat.com>:
On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com> wrote:
Beyond this, the current format of PO file for the glossary lacks an essential feature as I described before. There is no way to describe the context. I wonder how the glossary help translations without the contextual information. As a result, Japanese team is forced to describe contextual information in translated strings. This is the reason we preferred to Wiki style glossary.
From the above observation, does it sound a good option to clear the whole entry of Zanata glossary of a specific language?
FYI, as of Zanata 3.8, we support same source string with unique "description" and "pos" field for each glossary entry. This will help translator with more context information and able to have similar string with different context.
Good to hear that. Sounds a really nice feature :-) Once the feature is available in the openstack zanata instance, we will explore how to use it. Akihiro
---------------------------------------------
Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com
From: Alex Eng <aeng@redhat.com> To: "Kato, Tomoyuki" <kato.tomoyuki@jp.fujitsu.com> Cc: Akihiro Motoki <amotoki@gmail.com>, Ying Chun Guo/China/ IBM@IBMCN, Openstack-i18n <openstack-i18n@lists.openstack.org> Date: 2016/02/29 05:59 Subject: Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com
wrote: Beyond this, the current format of PO file for the glossary lacks an essential feature as I described before. There is no way to describe
Thank you for the information, Alex. I know Zanata allows to import glossaries from CSV and po files. I can see a sample of CSV file, with "description" and "pos" field[1]. Can you provide us a sample of po file, with "description" and "pos" field for an entry ? Best regards Ying Chun Guo (Daisy) [1] http://docs.zanata.org/en/release/user-guide/glossary/upload-glossaries/ Alex Eng <aeng@redhat.com> wrote on 2016/02/29 05:58:23: the
context. I wonder how the glossary help translations without the contextual information. As a result, Japanese team is forced to describe contextual information in translated strings. This is the reason we preferred to Wiki style glossary.
From the above observation, does it sound a good option to clear the whole entry of Zanata glossary of a specific language?
FYI, as of Zanata 3.8, we support same source string with unique "description" and "pos" field for each glossary entry. This will help translator with more context information and able to have similar string with different context.
---------------------------------------------
Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com
On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki < kato.tomoyuki@jp.fujitsu.com> wrote:
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
"with Zanata ID"? It is just an option. It is not a requirement. It is not a surprising thing someone uses an IRC nickname different from Zanata ID.
I'm using different IDs :) And, I'm not always join IRC because of my business reason and equipments. To coordinate my local language team, I'd like to use Gitter and local mailing list.
Just a though, in other community project, we used same ID all the place for easy keep track and other system integration i.e IRC Bot to record contribution, attendees. But of course, its not mandatory, but you will lose the record. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
2016-02-29 7:03 GMT+09:00 Alex Eng <aeng@redhat.com>:
On Sat, Feb 27, 2016 at 7:08 PM, Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com> wrote:
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
"with Zanata ID"? It is just an option. It is not a requirement. It is not a surprising thing someone uses an IRC nickname different from Zanata ID.
I'm using different IDs :) And, I'm not always join IRC because of my business reason and equipments. To coordinate my local language team, I'd like to use Gitter and local mailing list.
Just a though, in other community project, we used same ID all the place for easy keep track and other system integration i.e IRC Bot to record contribution, attendees. But of course, its not mandatory, but you will lose the record.
Totally agree with you.
From that reason, I am using one ID for all OpenStack related system: gerrit, launchpad, IRC, Zanata.
Akihiro
---------------------------------------------
Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com
From: "Kato, Tomoyuki" <kato.tomoyuki@jp.fujitsu.com> To: "'Akihiro Motoki'" <amotoki@gmail.com>, Ying Chun Guo/China/IBM@IBMCN Cc: Openstack-i18n <openstack-i18n@lists.openstack.org> Date: 2016/02/27 17:40 Subject: RE: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
Thanks Daisy for initiating this.
2016-02-25 17:53 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
I would like to raise a question how the glossary work? Is it actually working?
As one of coordinators of Japanese team, the glossary list itself is out-of-date. In addition to update per-language glossary, can we update a list of glossary itself?
Beyond this, the current format of PO file for the glossary lacks an essential feature as I described before. There is no way to describe
context. I wonder how the glossary help translations without the contextual information. As a result, Japanese team is forced to describe contextual information in translated strings. This is the reason we preferred to Wiki style glossary.
From the above observation, does it sound a good option to clear the whole entry of Zanata glossary of a specific language?
+1 to clear, as long as Japanese, as of now.
2. Document your local team communication method in the team wiki
Thank you for the input, Akihiro and Kato. I'm not strict in local communication method and IRC ID. If you have clearly documented them in your team wiki, that's fine. As to the glossary, I still think git repository is better than wiki to store glossaries. Git repo has strict control, while wiki has no controls at all. Wiki is used for frequently update purpose. After it turns to mature, Git repo is good to store. And, using pot/po file can make all translation teams to easily follow the same glossary list. I understand Japanese glossaries are out of date and your team don't like the current one in Zanata. If that's your team decision, I'm OK to delete it from Zanata. Thoughts? Best regards Ying Chun Guo (Daisy) "Kato, Tomoyuki" <kato.tomoyuki@jp.fujitsu.com> wrote on 2016/02/27 17:08:46: the page[2].
While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together.
I missed the previous team meeting (it is not special to me due to the meeting time). I would like to make some follow-up comments on a local communication.
I personally would like to continue to use Gitter (hosted by Github) as a communication channel in Japanese team. From my past experience, it has various good merits. I felt the first point is really useful in the crunch time of Liberty translation reviews.
* Pros: * it has a notification mechanism. Unread messages will be notified via email. * It can be used via browser (without any extra application) * Unlimited archive as long as gitter room is open to everyone * Cons * it is not provided by OpenStack infra
Kato-san and Japanese team members, feel free to comment it. Your feedbacks would be really appreciated.
I agree to using Gitter in Japanese team.
In my understand, using IRC channel for local team is not mandatory, just an option.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
"with Zanata ID"? It is just an option. It is not a requirement. It is not a surprising thing someone uses an IRC nickname different from Zanata ID.
I'm using different IDs :) And, I'm not always join IRC because of my business reason and equipments. To coordinate my local language team, I'd like to use Gitter and local mailing list.
Regards, KATO Tomoyuki
Note that it is important we need to know each other who you are but it is not a requirement to use Zanata ID as IRC nickname if you already use a different IRC nick.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n.
I can help you too. My nick is 'amotoki'. I am usually online from 0200UTC to 1600UTC.
# It will be easier to find me compared to finding Daisy on IRC :) # Just joking.. never mind Daisy!
Akihiro
Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
Hi Daisy,
Thank you for the input, Akihiro and Kato.
I'm not strict in local communication method and IRC ID. If you have clearly documented them in your team wiki, that's fine.
Already enough clear in wiki, but only in Japanse :) because of local communication method.
As to the glossary, I still think git repository is better than wiki to store glossaries. Git repo has strict control, while wiki has no controls at all. Wiki is used for frequently update purpose. After it turns to mature, Git repo is good to store. And, using pot/po file can make all translation teams to easily follow the same glossary list.
Yeah, I myself am generally agree to managing glossary on git repository. But, as of now, it doesn't meet the requirements from Japanese team fully. We need a little more work.
I understand Japanese glossaries are out of date and your team don't like the current one in Zanata. If that's your team decision, I'm OK to delete it from Zanata.
I think so. It's Japanese team dicision at now. Thanks, KATO Tomoyuki
Thoughts?
Best regards Ying Chun Guo (Daisy)
Daisy and Tomo, Thanks for dropping Japanese glossaries (+ follow-up). We Japanese team are happy to re-join the standard way of I18n team once we support contextual information. It was not an easy choice, but from our discussion one-to-one mapping from the source lang to Japanese does not work. Akihiro 2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Hi, KATO
I have deleted Japanese glossaries. You can check now.
Best regards Ying Chun Guo (Daisy)
----- Original message ----- From: KATO Tomoyuki <tomo@dream.daynight.jp> To: Ying Chun Guo/China/IBM@IBMCN Cc: Openstack-i18n <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation Date: Tue, Mar 1, 2016 7:21 PM
Hi Daisy,
Thank you for the input, Akihiro and Kato.
I'm not strict in local communication method and IRC ID. If you have clearly documented them in your team wiki, that's fine.
Already enough clear in wiki, but only in Japanse :) because of local communication method.
As to the glossary, I still think git repository is better than wiki to store glossaries. Git repo has strict control, while wiki has no controls at all. Wiki is used for frequently update purpose. After it turns to mature, Git repo is good to store. And, using pot/po file can make all translation teams to easily follow the same glossary list.
Yeah, I myself am generally agree to managing glossary on git repository. But, as of now, it doesn't meet the requirements from Japanese team fully. We need a little more work.
I understand Japanese glossaries are out of date and your team don't like the current one in Zanata. If that's your team decision, I'm OK to delete it from Zanata.
I think so. It's Japanese team dicision at now.
Thanks, KATO Tomoyuki
Thoughts?
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
Daisy, What should I do for https://review.openstack.org/285725 ? Should abandon it? 2016-03-02 19:05 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
Daisy and Tomo,
Thanks for dropping Japanese glossaries (+ follow-up).
We Japanese team are happy to re-join the standard way of I18n team once we support contextual information. It was not an easy choice, but from our discussion one-to-one mapping from the source lang to Japanese does not work.
Akihiro
2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Hi, KATO
I have deleted Japanese glossaries. You can check now.
Best regards Ying Chun Guo (Daisy)
----- Original message ----- From: KATO Tomoyuki <tomo@dream.daynight.jp> To: Ying Chun Guo/China/IBM@IBMCN Cc: Openstack-i18n <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation Date: Tue, Mar 1, 2016 7:21 PM
Hi Daisy,
Thank you for the input, Akihiro and Kato.
I'm not strict in local communication method and IRC ID. If you have clearly documented them in your team wiki, that's fine.
Already enough clear in wiki, but only in Japanse :) because of local communication method.
As to the glossary, I still think git repository is better than wiki to store glossaries. Git repo has strict control, while wiki has no controls at all. Wiki is used for frequently update purpose. After it turns to mature, Git repo is good to store. And, using pot/po file can make all translation teams to easily follow the same glossary list.
Yeah, I myself am generally agree to managing glossary on git repository. But, as of now, it doesn't meet the requirements from Japanese team fully. We need a little more work.
I understand Japanese glossaries are out of date and your team don't like the current one in Zanata. If that's your team decision, I'm OK to delete it from Zanata.
I think so. It's Japanese team dicision at now.
Thanks, KATO Tomoyuki
Thoughts?
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
I hope you can agree to abandon it. We can work on the improvement after the po format for new glossary feature is clear. Best regards Ying Chun Guo (Daisy) Akihiro Motoki <amotoki@gmail.com> wrote on 03/02/2016 09:01:12 PM:
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Tomoyuki KATO <tomo@dream.daynight.jp>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/02/2016 09:02 PM Subject: Re: [Openstack-i18n] To language team coordinators: get ready for Mitaka translation
Daisy,
What should I do for https://review.openstack.org/285725 ? Should abandon it?
2016-03-02 19:05 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
Daisy and Tomo,
Thanks for dropping Japanese glossaries (+ follow-up).
We Japanese team are happy to re-join the standard way of I18n team once we support contextual information. It was not an easy choice, but from our discussion one-to-one mapping from the source lang to Japanese does not work.
Akihiro
2016-03-01 22:45 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Hi, KATO
I have deleted Japanese glossaries. You can check now.
Best regards Ying Chun Guo (Daisy)
----- Original message ----- From: KATO Tomoyuki <tomo@dream.daynight.jp> To: Ying Chun Guo/China/IBM@IBMCN Cc: Openstack-i18n <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] To language team coordinators: get
ready for
Mitaka translation Date: Tue, Mar 1, 2016 7:21 PM
Hi Daisy,
Thank you for the input, Akihiro and Kato.
I'm not strict in local communication method and IRC ID. If you have clearly documented them in your team wiki, that's fine.
Already enough clear in wiki, but only in Japanse :) because of local communication method.
As to the glossary, I still think git repository is better than wiki to store glossaries. Git repo has strict control, while wiki has no controls at all. Wiki is used for frequently update purpose. After it turns to mature, Git repo is good to store. And, using pot/po file can make all translation teams to easily follow the same glossary list.
Yeah, I myself am generally agree to managing glossary on git repository. But, as of now, it doesn't meet the requirements from Japanese team fully. We need a little more work.
I understand Japanese glossaries are out of date and your team don't like the current one in Zanata. If that's your team decision, I'm OK to delete it from Zanata.
I think so. It's Japanese team dicision at now.
Thanks, KATO Tomoyuki
Thoughts?
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
Dear language coordinators and also translators, Although I think this telling is so late compared to Mitaka translation, I would like to kindly remind that we need to speed up for Newton translation, since the cut-off date for final RCs (when translation results will be finally imported) is *October 1st*. According to the dashboard on translate.openstack.org, our targeted priorities are as the followings: - Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low) Note that recently, stable-newton version was created in translate.o.o. Please translate to *stable-newton* branch, not master branch (exception: releasenotes should be translated on master branch). I tried to check whether there will be IBM translations or not, so I sent an e-mail to Douglas Fish (drfish@us.ibm.com), but unfortunately, his e-mail address is not active. Since we do not have enough time, let's first focus on Horizon for translation, and then translate Horizon related projects. (Surely, translation on server projects are also welcome!) Hope that we will have as much translation as we did previously, and I really hope that we will be able to keep on translation effort for Ocata and further releases as one team. If you have any questions, feel free to send an e-mail to me or call "ianychoi" nickname on Freenode #openstack-i18n channel. Sometimes my response can be slow, but I will respond :) Thank you very much. With many thanks, /Ian Ying Chun Guo wrote on 2/25/2016 5:53 PM:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be affected, focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
2. Document your local team communication method in the team wiki page[2].
While Mitaka translation starts, it's good to open your local communication channel to all of your language translators. Good communication is quite important for people from different places to work well together.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale <https://wiki.openstack.org/wiki/IRC> [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
One thing to note on the final date. The week of Sep 26 (- Oct 1) is the final release candidate week. The previous mail said Oct 1 is the deadline, but most OpenStack projects will release the next RC in the middle of the week. I would suggest to finish translations by Sep 27 0600UTC if possible. 0600UTC is the time of the daily translation import. Akihiro 2016-09-19 13:26 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Dear language coordinators and also translators,
Although I think this telling is so late compared to Mitaka translation, I would like to kindly remind that we need to speed up for Newton
since the cut-off date for final RCs (when translation results will be finally imported) is *October 1st*.
According to the dashboard on translate.openstack.org, our targeted
translation, priorities are as the followings:
- Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low)
Note that recently, stable-newton version was created in translate.o.o. Please translate to *stable-newton* branch, not master branch (exception:
releasenotes should be translated on master branch).
I tried to check whether there will be IBM translations or not, so I sent an e-mail to Douglas Fish (drfish@us.ibm.com), but
unfortunately, his e-mail address is not active.
Since we do not have enough time, let's first focus on Horizon for
translation, and then translate Horizon related projects.
(Surely, translation on server projects are also welcome!) Hope that we will have as much translation as we did previously, and I really hope that we will be able to keep on translation effort for Ocata and further releases as one team.
If you have any questions, feel free to send an e-mail to me or call "ianychoi" nickname on Freenode #openstack-i18n channel. Sometimes my response can be slow, but I will respond :) Thank you very much.
With many thanks,
/Ian
Ying Chun Guo wrote on 2/25/2016 5:53 PM:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be
focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
2. Document your local team communication method in the team wiki
affected, page[2].
While Mitaka translation starts, it's good to open your local
communication channel to
all of your language translators. Good communication is quite important for people from different places to work well together.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale < https://wiki.openstack.org/wiki/IRC> [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
Hello Akihiro-san, Thank you for this remainder :) I have one question. For Mitaka release, we set the criteria for Horizon translation as 66% [1] For Newton, currently the following 14 languages satisfy the criteria - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw + id Note that Indonesian was not included in Mitaka, but now the translation progress is very good (76.12% for Horizon). Unfortunately, the two following languages are near the cutting edges - pl-PL: 65.36% - tr-TR: 63.19% I have checked the translation ratios for those two languages one week ago, and now, the translation ratios are unfortunately the same. Should we remove those two languages in Horizon for Newton? I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice. And Akihiro-san, what would be the final due to include or exclude language lists in Horizon? [1] http://lists.openstack.org/pipermail/openstack-i18n/2016-March/002012.html With many thanks, /Ian Akihiro Motoki wrote on 9/26/2016 12:53 PM:
One thing to note on the final date.
The week of Sep 26 (- Oct 1) is the final release candidate week. The previous mail said Oct 1 is the deadline, but most OpenStack projects will release the next RC in the middle of the week.
I would suggest to finish translations by Sep 27 0600UTC if possible. 0600UTC is the time of the daily translation import.
Akihiro
2016-09-19 13:26 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>>:
>
Dear language coordinators and also translators,
Although I think this telling is so late compared to Mitaka translation, I would like to kindly remind that we need to speed up for Newton translation, since the cut-off date for final RCs (when translation results will be finally imported) is *October 1st*.
According to the dashboard ontranslate.openstack.org <http://translate.openstack.org>, our targeted priorities are as the followings:
- Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low)
Note that recently, stable-newton version was created in translate.o.o. Please translate to *stable-newton* branch, not master branch (exception: releasenotes should be translated on master branch).
I tried to check whether there will be IBM translations or not, so I sent an e-mail to Douglas Fish (drfish@us.ibm.com <mailto:drfish@us.ibm.com>), but unfortunately, his e-mail address is not active.
Since we do not have enough time, let's first focus on Horizon for translation, and then translate Horizon related projects. (Surely, translation on server projects are also welcome!) Hope that we will have as much translation as we did previously, and I really hope that we will be able to keep on translation effort for Ocata and further releases as one team.
If you have any questions, feel free to send an e-mail to me or call "ianychoi" nickname on Freenode #openstack-i18n channel. Sometimes my response can be slow, but I will respond :) Thank you very much.
With many thanks,
/Ian
Ying Chun Guo wrote on 2/25/2016 5:53 PM:
>>
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be
focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
2. Document your local team communication method in the team wiki
affected, page[2].
While Mitaka translation starts, it's good to open your local
communication channel to
all of your language translators. Good communication is quite important for people from different places to work well together.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you.
Best regards Ying Chun Guo (Daisy)
[1]http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale <http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale> <https://wiki.openstack.org/wiki/IRC> [2]https://wiki.openstack.org/wiki/I18nTeam/team <https://wiki.openstack.org/wiki/I18nTeam/team> [3]https://wiki.openstack.org/wiki/IRC <https://wiki.openstack.org/wiki/IRC>
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto:Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello Akihiro-san,
Thank you for this remainder :)
I have one question. For Mitaka release, we set the criteria for Horizon translation as 66% [1]
For Newton, currently the following 14 languages satisfy the criteria - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw + id
Note that Indonesian was not included in Mitaka, but now the translation progress is very good (76.12% for Horizon).
Unfortunately, the two following languages are near the cutting edges - pl-PL: 65.36% - tr-TR: 63.19%
I have checked the translation ratios for those two languages one week ago, and now, the translation ratios are unfortunately the same.
Should we remove those two languages in Horizon for Newton?
I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice.
And Akihiro-san, what would be the final due to include or exclude language lists in Horizon?
AFAIK the horizon team has not decided the exact date for the final RC, but my guess is around the middle of the week. If there is a special reason, the horizon team can prepare RC3. I can propose the update of the language list appropriately and coordinate the date. My vote on the language list is to add languages with good progress aggresively and not to hurry to remove languages with non-good progress from the existing list. Thus, my suggestion is only to add Indonesian and remove nothing. How about apply the similar rule for translation import? For translation import, 75% for inclusion and 60% for exclusion. Akihiro
[1] http://lists.openstack.org/pipermail/openstack-i18n/2016- March/002012.html
With many thanks,
/Ian
Akihiro Motoki wrote on 9/26/2016 12:53 PM:
One thing to note on the final date.
The week of Sep 26 (- Oct 1) is the final release candidate week. The previous mail said Oct 1 is the deadline, but most OpenStack projects will release the next RC in the middle of the week.
I would suggest to finish translations by Sep 27 0600UTC if possible. 0600UTC is the time of the daily translation import.
Akihiro
2016-09-19 13:26 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Dear language coordinators and also translators,
Although I think this telling is so late compared to Mitaka translation, I would like to kindly remind that we need to speed up for Newton translation, since the cut-off date for final RCs (when translation results will be finally imported) is *October 1st*.
According to the dashboard on translate.openstack.org, our targeted priorities are as the followings:
- Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low)
Note that recently, stable-newton version was created in translate.o.o. Please translate to *stable-newton* branch, not master branch (exception: releasenotes should be translated on master branch).
I tried to check whether there will be IBM translations or not, so I sent an e-mail to Douglas Fish (drfish@us.ibm.com), but unfortunately, his e-mail address is not active.
Since we do not have enough time, let's first focus on Horizon for translation, and then translate Horizon related projects. (Surely, translation on server projects are also welcome!) Hope that we will have as much translation as we did previously, and I really hope that we will be able to keep on translation effort for Ocata and further releases as one team.
If you have any questions, feel free to send an e-mail to me or call "ianychoi" nickname on Freenode #openstack-i18n channel. Sometimes my response can be slow, but I will respond :) Thank you very much.
With many thanks,
/Ian
Ying Chun Guo wrote on 2/25/2016 5:53 PM:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be
focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
2. Document your local team communication method in the team wiki
affected, page[2].
While Mitaka translation starts, it's good to open your local
communication channel to
all of your language translators. Good communication is quite important for people from different places to work well together.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale < https://wiki.openstack.org/wiki/IRC> [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
2016-09-26 15:21 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Hello Akihiro-san,
Thank you for this remainder :)
I have one question. For Mitaka release, we set the criteria for Horizon translation as 66% [1]
For Newton, currently the following 14 languages satisfy the criteria - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw + id
Note that Indonesian was not included in Mitaka, but now the translation progress is very good (76.12% for Horizon).
Unfortunately, the two following languages are near the cutting edges - pl-PL: 65.36% - tr-TR: 63.19%
I have checked the translation ratios for those two languages one week ago, and now, the translation ratios are unfortunately the same.
Should we remove those two languages in Horizon for Newton?
I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice.
And Akihiro-san, what would be the final due to include or exclude language lists in Horizon?
AFAIK the horizon team has not decided the exact date for the final RC, but my guess is around the middle of the week. If there is a special reason, the horizon team can prepare RC3. I can propose the update of the language list appropriately and coordinate the date.
My vote on the language list is to add languages with good progress aggresively and not to hurry to remove languages with non-good progress from the existing list. Thus, my suggestion is only to add Indonesian and remove nothing. How about apply the similar rule for translation import? For translation import, 75% for inclusion and 60% for exclusion.
The above numbers might be wrong.
Akihiro
[1] http://lists.openstack.org/pipermail/openstack-i18n/2016-Mar ch/002012.html
With many thanks,
/Ian
Akihiro Motoki wrote on 9/26/2016 12:53 PM:
One thing to note on the final date.
The week of Sep 26 (- Oct 1) is the final release candidate week. The previous mail said Oct 1 is the deadline, but most OpenStack projects will release the next RC in the middle of the week.
I would suggest to finish translations by Sep 27 0600UTC if possible. 0600UTC is the time of the daily translation import.
Akihiro
2016-09-19 13:26 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Dear language coordinators and also translators,
Although I think this telling is so late compared to Mitaka translation, I would like to kindly remind that we need to speed up for Newton translation, since the cut-off date for final RCs (when translation results will be finally imported) is *October 1st*.
According to the dashboard on translate.openstack.org, our targeted priorities are as the followings:
- Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - Murano Dashboard (Low) - Magnum UI (Low) - Designate Dashboard (Low)
Note that recently, stable-newton version was created in translate.o.o. Please translate to *stable-newton* branch, not master branch (exception: releasenotes should be translated on master branch).
I tried to check whether there will be IBM translations or not, so I sent an e-mail to Douglas Fish (drfish@us.ibm.com), but unfortunately, his e-mail address is not active.
Since we do not have enough time, let's first focus on Horizon for translation, and then translate Horizon related projects. (Surely, translation on server projects are also welcome!) Hope that we will have as much translation as we did previously, and I really hope that we will be able to keep on translation effort for Ocata and further releases as one team.
If you have any questions, feel free to send an e-mail to me or call "ianychoi" nickname on Freenode #openstack-i18n channel. Sometimes my response can be slow, but I will respond :) Thank you very much.
With many thanks,
/Ian
Ying Chun Guo wrote on 2/25/2016 5:53 PM:
Dear coordinators,
Mitaka translation will be started at the beginning of March, and probably ended in the week of March 28. We need to get ourselves ready for Mitaka translation from now on.
Because of the join of IBM professional translators, we will be able to cover more projects in our translation plan of this release. Generally, the jobs of existing community translators will not be
focus on Horizon, same as before. IBM translators will focus on "other" projects.
Before Mitaka translation starts, there are several things you can do:
1. Update glossary.
If you don't have glossary translations in i18n repo[1], or you want to update glossary translations, you can send a patch with your translations or your updates to i18n repo directly.
2. Document your local team communication method in the team wiki
affected, page[2].
While Mitaka translation starts, it's good to open your local
communication channel to
all of your language translators. Good communication is quite important for people from different places to work well together.
3. Join IRC channel[3] #openstack-i18n with your zanata ID
As a coordinator, you have the responsibility to coordinate your language translations. A good practise is to show up in IRC and have your people to get you easily when they have troubles.
If you have any questions, talk to me. My IRC ID is "Daisy" in the channel of #openstack-i18n. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale < https://wiki.openstack.org/wiki/IRC> [2] https://wiki.openstack.org/wiki/I18nTeam/team [3] https://wiki.openstack.org/wiki/IRC
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
[snip] I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice.
And Akihiro-san, what would be the final due to include or exclude language lists in Horizon?
AFAIK the horizon team has not decided the exact date for the final RC, but my guess is around the middle of the week. If there is a special reason, the horizon team can prepare RC3. I can propose the update of the language list appropriately and coordinate the date.
My vote on the language list is to add languages with good progress aggresively and not to hurry to remove languages with non-good progress from the existing list. Thus, my suggestion is only to add Indonesian and remove nothing.
+1 to "add Indonesian and remove nothing"
How about apply the similar rule for translation import? For translation import, 75% for inclusion and 60% for exclusion.
The above numbers might be wrong.
40% for exclusion https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/s... Thanks, KATO Tomoyuki
On 2016-09-26 08:21, Akihiro Motoki wrote:
2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>>:
Hello Akihiro-san,
Thank you for this remainder :)
I have one question. For Mitaka release, we set the criteria for Horizon translation as 66% [1]
For Newton, currently the following 14 languages satisfy the criteria - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw + id
Note that Indonesian was not included in Mitaka, but now the translation progress is very good (76.12% for Horizon).
Unfortunately, the two following languages are near the cutting edges - pl-PL: 65.36% - tr-TR: 63.19%
I have checked the translation ratios for those two languages one week ago, and now, the translation ratios are unfortunately the same.
Should we remove those two languages in Horizon for Newton?
I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice.
And Akihiro-san, what would be the final due to include or exclude language lists in Horizon?
AFAIK the horizon team has not decided the exact date for the final RC, but my guess is around the middle of the week. If there is a special reason, the horizon team can prepare RC3. I can propose the update of the language list appropriately and coordinate the date.
My vote on the language list is to add languages with good progress aggresively and not to hurry to remove languages with non-good progress from the existing list. Thus, my suggestion is only to add Indonesian and remove nothing. How about apply the similar rule for translation import? For translation import, 75% for inclusion and 60% for exclusion.
Those are right. 75 % is enforced for inclusion. Right now the tools use 40 % for exclusion - but we have decided on 60 % as agreed lower bound on "properly translated" and sometimes manually removed content below the 60 %, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: 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
I filed a bug https://bugs.launchpad.net/horizon/+bug/1627673 and proposed a patch https://review.openstack.org/376357 (for master). It will be backported to stable/newton in https://review.openstack.org/376359 (cherry-pick for stable/newton). What in my mind is to automate this process in near future (hopefully in Ocata cycle). Akihiro 2016-09-26 15:45 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-09-26 08:21, Akihiro Motoki wrote:
2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>>:
Hello Akihiro-san,
Thank you for this remainder :)
I have one question. For Mitaka release, we set the criteria for Horizon translation as 66% [1]
For Newton, currently the following 14 languages satisfy the criteria - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw
+ id
Note that Indonesian was not included in Mitaka, but now the translation progress is very good (76.12% for Horizon).
Unfortunately, the two following languages are near the cutting edges - pl-PL: 65.36% - tr-TR: 63.19%
I have checked the translation ratios for those two languages one week ago, and now, the translation ratios are unfortunately the same.
Should we remove those two languages in Horizon for Newton?
I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice.
And Akihiro-san, what would be the final due to include or exclude language lists in Horizon?
AFAIK the horizon team has not decided the exact date for the final RC, but my guess is around the middle of the week. If there is a special reason, the horizon team can prepare RC3. I can propose the update of the language list appropriately and coordinate the date.
My vote on the language list is to add languages with good progress aggresively and not to hurry to remove languages with non-good progress from the existing list. Thus, my suggestion is only to add Indonesian and remove nothing. How about apply the similar rule for translation import? For translation import, 75% for inclusion and 60% for exclusion.
Those are right. 75 % is enforced for inclusion.
Right now the tools use 40 % for exclusion - but we have decided on 60 % as agreed lower bound on "properly translated" and sometimes manually removed content below the 60 %,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: 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
Thank you very much for all with reminding language in(ex)clusion policy and submitting a patch to include Indonesian in Horizon. I quite agree that I18n team should encourage translations, rather than just removing language supports. And I especially appreciate kind contribution from Suhartono, who translates to Indonesian a lot. I see that there has been lots of Indonesian translations [1], and also now there is Indonesian landing page [2] for translated documents. Let's congratulate for active Indonesian translation :) [1] http://stackalytics.com/?metric=translations&release=newton [2] http://docs.openstack.org/id/ With many thanks, /Ian Akihiro Motoki wrote on 9/26/2016 7:17 PM:
I filed a bug https://bugs.launchpad.net/horizon/+bug/1627673 and proposed a patch https://review.openstack.org/376357 (for master). It will be backported to stable/newton in https://review.openstack.org/376359 (cherry-pick for stable/newton).
What in my mind is to automate this process in near future (hopefully in Ocata cycle).
Akihiro
2016-09-26 15:45 GMT+09:00 Andreas Jaeger <aj@suse.com <mailto:aj@suse.com>>:
On 2016-09-26 08:21, Akihiro Motoki wrote: > > > 2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com> > <mailto:ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>>>: > > Hello Akihiro-san, > > Thank you for this remainder :) > > I have one question. > For Mitaka release, we set the criteria for Horizon translation as > 66% [1] > > For Newton, currently the following 14 languages satisfy the criteria > - cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw + id > > Note that Indonesian was not included in Mitaka, but now the > translation progress is very good (76.12% for Horizon). > > Unfortunately, the two following languages are near the cutting edges > - pl-PL: 65.36% > - tr-TR: 63.19% > > I have checked the translation ratios for those two languages one > week ago, and now, the translation ratios are unfortunately the same. > > Should we remove those two languages in Horizon for Newton? > > I would like to discuss this issue with i18n members. > IMO since my kind announcement for Horizon translation was a little > bit late, > I think just including Indonesian and so total 16 languages for > Newton would be nice. > > And Akihiro-san, what would be the final due to include or exclude > language lists in Horizon? > > > AFAIK the horizon team has not decided the exact date for the final RC, > but my guess is around the middle of the week. > If there is a special reason, the horizon team can prepare RC3. > I can propose the update of the language list appropriately and > coordinate the date. > > My vote on the language list is to add languages with good progress > aggresively > and not to hurry to remove languages with non-good progress from the > existing list. > Thus, my suggestion is only to add Indonesian and remove nothing. > How about apply the similar rule for translation import? > For translation import, 75% for inclusion and 60% for exclusion.
Those are right. 75 % is enforced for inclusion.
Right now the tools use 40 % for exclusion - but we have decided on 60 % as agreed lower bound on "properly translated" and sometimes manually removed content below the 60 %,
Andreas -- Andreas Jaeger aj@{suse.com <http://suse.com>,opensuse.org <http://opensuse.org>} Twitter: 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
Thanks attention of all. After involving in the OpenStack translation, I want to implement it in the Jakarta region. Unfortunately, I do not see any company working on openstack projects. Is there any suggestion to pursue openstack jobs in my regions ? Best regards, Suhartono. 2016-09-27 10:28 GMT+07:00 Ian Y. Choi <ianyrchoi@gmail.com>:
Thank you very much for all with reminding language in(ex)clusion policy and submitting a patch to include Indonesian in Horizon.
I quite agree that I18n team should encourage translations, rather than just removing language supports.
And I especially appreciate kind contribution from Suhartono, who translates to Indonesian a lot. I see that there has been lots of Indonesian translations [1], and also now there is Indonesian landing page [2] for translated documents.
Let's congratulate for active Indonesian translation :)
[1] http://stackalytics.com/?metric=translations&release=newton [2] http://docs.openstack.org/id/
With many thanks,
/Ian
Akihiro Motoki wrote on 9/26/2016 7:17 PM:
I filed a bug https://bugs.launchpad.net/horizon/+bug/1627673 and proposed a patch https://review.openstack.org/376357 (for master). It will be backported to stable/newton in https://review.openstack.org/ 376359 (cherry-pick for stable/newton).
What in my mind is to automate this process in near future (hopefully in Ocata cycle).
Akihiro
2016-09-26 15:45 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-09-26 08:21, Akihiro Motoki wrote:
2016-09-26 13:05 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>>:
Hello Akihiro-san,
Thank you for this remainder :)
I have one question. For Mitaka release, we set the criteria for Horizon translation as 66% [1]
For Newton, currently the following 14 languages satisfy the
criteria
- cs, de, en-gb, en-au, es, fr, it, ja, ko, pt-br, ru, zh-cn, zh-tw
+ id
Note that Indonesian was not included in Mitaka, but now the translation progress is very good (76.12% for Horizon).
Unfortunately, the two following languages are near the cutting
edges
- pl-PL: 65.36% - tr-TR: 63.19%
I have checked the translation ratios for those two languages one week ago, and now, the translation ratios are unfortunately the
same.
Should we remove those two languages in Horizon for Newton?
I would like to discuss this issue with i18n members. IMO since my kind announcement for Horizon translation was a little bit late, I think just including Indonesian and so total 16 languages for Newton would be nice.
And Akihiro-san, what would be the final due to include or exclude language lists in Horizon?
AFAIK the horizon team has not decided the exact date for the final RC, but my guess is around the middle of the week. If there is a special reason, the horizon team can prepare RC3. I can propose the update of the language list appropriately and coordinate the date.
My vote on the language list is to add languages with good progress aggresively and not to hurry to remove languages with non-good progress from the existing list. Thus, my suggestion is only to add Indonesian and remove nothing. How about apply the similar rule for translation import? For translation import, 75% for inclusion and 60% for exclusion.
Those are right. 75 % is enforced for inclusion.
Right now the tools use 40 % for exclusion - but we have decided on 60 % as agreed lower bound on "properly translated" and sometimes manually removed content below the 60 %,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: 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 listOpenStack-I18n@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Ian, I just see one link in page http://docs.openstack.org/zh_CN/ for release Liberty/Mitakta. Our Chinese translators are wondering whether we can have the page updated with links on what we have translated? BTW, there are installation guides links for Chinese (zh_CN) on page http://docs.openstack.org/draft/draft-index.html. Does it mean links would be available to page http://docs.openstack.org/zh_CN/ after the draft links went to release? Thanks -- --------------------------------------------- 周正喜 Mobile: 13701280947 WeChat: 472174291
On 2016-09-28 10:06, Will Zhou wrote:
Hi Ian,
I just see one link in page http://docs.openstack.org/zh_CN/ for release Liberty/Mitakta. Our Chinese translators are wondering whether we can have the page updated with links on what we have translated?
What content exactly? Note that we do not yet link to Newton specific content, this will only be done once Newton is released.
BTW, there are installation guides links for Chinese (zh_CN) on page http://docs.openstack.org/draft/draft-index.html. Does it mean links would be available to page http://docs.openstack.org/zh_CN/ after the draft links went to release? Thanks
Not automatically, language teams need to update the index page themselves. Before we publish a link, you should review that the rendered version really looks fine and that there are no problems. A few missing translations are fine - but review it so that it works. For example the link on the top of http://docs.openstack.org/draft/zh_CN/install-guide-obs/keystone-openrc.html looks broken - something a review should catch and fix. Once that review has happened, propose a change to the index page, it lives in openstack-manuals/www/ Andreas
--
--------------------------------------------- 周正喜 Mobile: 13701280947 <tel:13701280947> WeChat: 472174291
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: 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
Hello Will Zhou! As Andreas mentioned, it is not a good idea to include each language landing page in draft translated results. However, in my opinion, there are several Chinese-translated documents such as : http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/ : http://docs.openstack.org/liberty/zh_CN/install-guide-obs/ . For Liberty and Mitaka translated documents, sure! Would you list up and prioritize which Chinese documents are needed to include in your landing page? Andreas Jaeger wrote on 9/28/2016 5:12 PM:
On 2016-09-28 10:06, Will Zhou wrote:
Hi Ian,
I just see one link in page http://docs.openstack.org/zh_CN/ for release Liberty/Mitakta. Our Chinese translators are wondering whether we can have the page updated with links on what we have translated? What content exactly?
Note that we do not yet link to Newton specific content, this will only be done once Newton is released.
BTW, there are installation guides links for Chinese (zh_CN) on page http://docs.openstack.org/draft/draft-index.html. Does it mean links would be available to page http://docs.openstack.org/zh_CN/ after the draft links went to release? Thanks Not automatically, language teams need to update the index page themselves.
Before we publish a link, you should review that the rendered version really looks fine and that there are no problems. A few missing translations are fine - but review it so that it works.
For example the link on the top of http://docs.openstack.org/draft/zh_CN/install-guide-obs/keystone-openrc.html looks broken - something a review should catch and fix.
Once that review has happened, propose a change to the index page, it lives in openstack-manuals/www/ Note that this *review* is another important thing for the presentation of translated documents. Although translation progress is 100%, some translated strings may cause errors and somethings might see differently than originally expected.
To modify your landing page, you can propose a patch like : https://review.openstack.org/#/c/355108/ (Indonesian landing page) on openstack/openstack-manuals repository in master branch (it should not be other stable branches for landing pages). Of course, i18n team members would like to happily help to revise your landing page with containing more translated documents :) With many thanks, /Ian
Andreas
--
--------------------------------------------- 周正喜 Mobile: 13701280947 <tel:13701280947> WeChat: 472174291
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (9)
-
Akihiro Motoki
-
Alex Eng
-
Andreas Jaeger
-
Cloud Suhartono
-
Ian Y. Choi
-
KATO Tomoyuki
-
Kato, Tomoyuki
-
Will Zhou
-
Ying Chun Guo