Re: [Openstack-i18n] Criteria of Horizon language list forMitakarelease
Hi Doug and all, I needed to spend some time to look for the history. Roughly speaking our history can be broken donw into three categories: [1] Liberty Horizon [2] documentation translation from 2014. [3] up to Kilo Horizon I think following the history clarified what happened. --- [1] Liberty Horizon In Liberty, we migrated the translation platform to Zanata and all imports were done by Jenkins jobs (thanks to Andreas). [2] documentation translation from 2014 In parallel, there was the ongoing efforts to automate documentation translations. The thread is [2] and we discussed the threshold for translation addition (75%) and removal (60%). It is documented very well at https://wiki.openstack.org/wiki/Translations/Infrastructure. [3] up to Kilo Horizon The following are my translation import patch for Horizon up to Kilo: * KIlo : https://github.com/openstack/horizon/commit/56d5683c8c49558ae22200bc01ec87ea... (The commit message was wrong not Juno but Kilo :p) * Juno : https://github.com/openstack/horizon/commit/9b0ba951c07af13aa4c386b19876474b... * Icehouse : https://github.com/openstack/horizon/commit/a9cf547d20065b2bd49e101364b46cff... * Havana : https://github.com/openstack/horizon/commit/4910222356fbd2aeb0dab1b3cebe0033... All of these commit messages said "Import ~100% completed translaitons". It seems we used almost all are translated. I could not find the meeting log where we discussed this criteria first for Havana or Icehouse. According to [1] it seems we had the criteria of 95% for Juno. --- commit 56d5683c8c49558ae22200bc01ec87ea83144003 Author: Akihiro Motoki <motoki@da.jp.nec.com> Date: Thu Apr 23 06:58:49 2015 +0900 Import translations from Transifex for Juno * Import ~100% completed translations (translations available for 12 languages) * Delete incomplete languages * Update language list in openstack_dashboard settings.py --- That's all what I succeeded to gather. Akihiro [1] http://lists.openstack.org/pipermail/openstack-i18n/2014-October/000806.html [2] http://lists.openstack.org/pipermail/openstack-i18n/2014-October/thread.html... 2016-03-22 22:32 GMT+09:00 Douglas Fish <drfish@us.ibm.com>:
Akihiro,
I've been trying to find where we documented the 90% cutoff used by Horizon in past releases. I can't find it (and I'm afraid I'm the one who documented it). Were you able to find that reference?
I think it's reasonable to manage the Horizon language list to match the same set of languages for which we have PO files included in the project. The 66% cutoff would apply in both cases then. It should be easy for a consumer or distro to provide a shorter list than what we've defaulted by changing the value of the LANGUAGES setting in local_settings.py or a local_settings.d file.
Doug Fish
"Ying Chun Guo" <guoyingc@cn.ibm.com> wrote on 03/22/2016 05:56:45 AM:
From: "Ying Chun Guo" <guoyingc@cn.ibm.com> To: Akihiro Motoki <amotoki@gmail.com> Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/22/2016 05:59 AM Subject: Re: [Openstack-i18n] Criteria of Horizon language list for Mitakarelease
Akihiro Motoki <amotoki@gmail.com> wrote on 03/22/2016 06:43:33 PM:
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/22/2016 06:45 PM Subject: Re: [Openstack-i18n] Criteria of Horizon language list for
Mitakarelease
Akihiro Motoki <amotoki@gmail.com> wrote on 03/22/2016 02:27:21 AM:
From: Akihiro Motoki <amotoki@gmail.com> To: "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org> Date: 03/22/2016 02:29 AM Subject: [Openstack-i18n] Criteria of Horizon language list for Mitaka release
Hi i18n team,
As Horizon liaison, I would like to ask you all about the criteria of Horizon language list for Mitaka release.
The same topic was discussed several releases ago and the consensus at that time were: * remove all translations with less than 90% progress * update the language list accordingly.
Translations were imported manually at that time and the situation may be changed now. I don't have an opinion and will just follow the i18n project decision. If no response or well-defined criteria, I will just keep the current language list [1].
Thank you for taking care of that, Akihiro. I don't see any requests to change the language list.
The following is just information: We have four PO files (django/djangojs for horizon and
openstack_dashboard).
The current translation import policy for each PO file is documentedhere [2]. Each PO file is imported once the translation percentage becomes over 75% and it will be removed when the translation percentage becomes less
2016-03-22 18:00 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>: than
20%.
What is our criteria?
My opinion is to follow the previous guidelines.
Do you mean we should remove <90% translations and update the lang list accordingly?
I made a quick survey. The result is not so happy, but I will just follow the team decision.
We have four PO files per language for horizon. My understanding is 90% means 90% translations for all these PO files. Unfortunately, as of today, only four languages satisfy this criteria (90%): de, fr, ja, ko If we change the criteria to 66%, we will have three more languages: pt-br, ru, zh-cn.
It is too sad statistics. openstack_dashboard/djangojs is the bottleneck of the progress.
On the other hand, the current language list contains 15 translated languages: cs, de, en-gb, en-au, es, fr, it, ja, ko, pl, pt-br, ru, tr, zh-cn, zh-tw.
No, I didn't mean to remove <90% translations. Did we do that before ? I thought the criteria was 66%.
I just realized the difference situation we met in this release. We have included plugin projects. Before mitaka, we only focus on Horizon translation. If we only take a look at the completion rate of Horizon[1], I think most active translation team have achieved >66%. So it means, we don't need to remove any languages from the list. If we consider the overall completion rate of plugin projects together with Horizon projects, some languages are less than 66%. My suggestion is to only consider the progress of Horizon project. 90% is too strict, I think. 66% is better.
Akihiro
In future releases, I think we should automate this as a part of translation import jobs. I will reduce the work of horizon liaison.
I agree.
Akihiro
[1] https://github.com/openstack/horizon/blob/master/ openstack_dashboard/settings.py#L198-L215 [2] https://wiki.openstack.org/wiki/Translations/ Infrastructure#Translation_percentage_changes
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://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
From: Akihiro Motoki <amotoki@gmail.com> To: Douglas Fish/Rochester/IBM@IBMUS Cc: Ying Chun Guo <guoyingc@cn.ibm.com>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/22/2016 09:12 AM Subject: Re: [Openstack-i18n] Criteria of Horizon language list forMitakarelease
Hi Doug and all,
I needed to spend some time to look for the history. Roughly speaking our history can be broken donw into three categories:
[1] Liberty Horizon [2] documentation translation from 2014. [3] up to Kilo Horizon
I think following the history clarified what happened.
--- [1] Liberty Horizon In Liberty, we migrated the translation platform to Zanata and all imports were done by Jenkins jobs (thanks to Andreas).
[2] documentation translation from 2014 In parallel, there was the ongoing efforts to automate documentation translations. The thread is [2] and we discussed the threshold for translation addition (75%) and removal (60%). It is documented very well at https://wiki.openstack.org/wiki/Translations/Infrastructure.
[3] up to Kilo Horizon The following are my translation import patch for Horizon up to Kilo: * KIlo : https://github.com/openstack/horizon/commit/ 56d5683c8c49558ae22200bc01ec87ea83144003 (The commit message was wrong not Juno but Kilo :p) * Juno : https://github.com/openstack/horizon/commit/ 9b0ba951c07af13aa4c386b19876474b971e7946 * Icehouse : https://github.com/openstack/horizon/commit/ a9cf547d20065b2bd49e101364b46cffed4b6aee * Havana : https://github.com/openstack/horizon/commit/ 4910222356fbd2aeb0dab1b3cebe00330c2641f7
All of these commit messages said "Import ~100% completed translaitons". It seems we used almost all are translated. I could not find the meeting log where we discussed this criteria first for Havana or Icehouse. According to [1] it seems we had the criteria of 95% for Juno. --- commit 56d5683c8c49558ae22200bc01ec87ea83144003 Author: Akihiro Motoki <motoki@da.jp.nec.com> Date: Thu Apr 23 06:58:49 2015 +0900
Import translations from Transifex for Juno
* Import ~100% completed translations (translations available for 12 languages) * Delete incomplete languages * Update language list in openstack_dashboard settings.py ---
That's all what I succeeded to gather.
Akihiro
[1] http://lists.openstack.org/pipermail/openstack-i18n/2014- October/000806.html [2] http://lists.openstack.org/pipermail/openstack-i18n/2014- October/thread.html#813
2016-03-22 22:32 GMT+09:00 Douglas Fish <drfish@us.ibm.com>:
Akihiro,
I've been trying to find where we documented the 90% cutoff used by Horizon in past releases. I can't find it (and I'm afraid I'm the one who documented it). Were you able to find that reference?
I think it's reasonable to manage the Horizon language list to match
same set of languages for which we have PO files included in the
I am aware of this additional bug for Liberty: https://bugs.launchpad.net/horizon/+bug/1502326 where we adjusted the list of languages available by default. In Liberty we did not use the same criteria for deciding to include the PO files in the project that we did for including a language in the selection widget in the UI. Looking back, that seems like a strange choice now. Looking in horizon/openstack_dashboard/locale I see there are 30 or so langauges. I know we don't have that many languages translated to 66% in Horizon. Is there some cleanup that is still remaining, or is this the result of the criteria not quite matching what I'd expect? Doug Fish Akihiro Motoki <amotoki@gmail.com> wrote on 03/22/2016 09:10:48 AM: the project.
The 66% cutoff would apply in both cases then. It should be easy for a consumer or distro to provide a shorter list than what we've defaulted by changing the value of the LANGUAGES setting in local_settings.py or a local_settings.d file.
Doug Fish
"Ying Chun Guo" <guoyingc@cn.ibm.com> wrote on 03/22/2016 05:56:45 AM:
From: "Ying Chun Guo" <guoyingc@cn.ibm.com> To: Akihiro Motoki <amotoki@gmail.com> Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/22/2016 05:59 AM Subject: Re: [Openstack-i18n] Criteria of Horizon language list for Mitakarelease
Akihiro Motoki <amotoki@gmail.com> wrote on 03/22/2016 06:43:33 PM:
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 03/22/2016 06:45 PM Subject: Re: [Openstack-i18n] Criteria of Horizon language list for
Mitakarelease
Akihiro Motoki <amotoki@gmail.com> wrote on 03/22/2016 02:27:21 AM:
From: Akihiro Motoki <amotoki@gmail.com> To: "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org> Date: 03/22/2016 02:29 AM Subject: [Openstack-i18n] Criteria of Horizon language list for Mitaka release
Hi i18n team,
As Horizon liaison, I would like to ask you all about the criteria of Horizon language list for Mitaka release.
The same topic was discussed several releases ago and the consensus at that time were: * remove all translations with less than 90% progress * update the language list accordingly.
Translations were imported manually at that time and the situation may be changed now. I don't have an opinion and will just follow the i18n project decision. If no response or well-defined criteria, I will just keep the current language list [1].
Thank you for taking care of that, Akihiro. I don't see any requests to change the language list.
The following is just information: We have four PO files (django/djangojs for horizon and
openstack_dashboard).
The current translation import policy for each PO file is documentedhere [2]. Each PO file is imported once the translation percentage becomes over 75% and it will be removed when the translation percentage becomes less
2016-03-22 18:00 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>: than
20%.
What is our criteria?
My opinion is to follow the previous guidelines.
Do you mean we should remove <90% translations and update the lang list accordingly?
I made a quick survey. The result is not so happy, but I will just follow the team decision.
We have four PO files per language for horizon. My understanding is 90% means 90% translations for all these PO files. Unfortunately, as of today, only four languages satisfy this criteria (90%): de, fr, ja, ko If we change the criteria to 66%, we will have three more languages: pt-br, ru, zh-cn.
It is too sad statistics. openstack_dashboard/djangojs is the bottleneck of the progress.
On the other hand, the current language list contains 15 translated languages: cs, de, en-gb, en-au, es, fr, it, ja, ko, pl, pt-br, ru, tr, zh-cn, zh-tw.
No, I didn't mean to remove <90% translations. Did we do that before ? I thought the criteria was 66%.
I just realized the difference situation we met in this release. We have included plugin projects. Before mitaka, we only focus on Horizon translation. If we only take a look at the completion rate of Horizon[1], I think most active translation team have achieved >66%. So it means, we don't need to remove any languages from the list. If we consider the overall completion rate of plugin projects together with Horizon projects, some languages are less than 66%. My suggestion is to only consider the progress of Horizon project. 90% is too strict, I think. 66% is better.
Akihiro
In future releases, I think we should automate this as a part of translation import jobs. I will reduce the work of horizon liaison.
I agree.
Akihiro
[1] https://github.com/openstack/horizon/blob/master/ openstack_dashboard/settings.py#L198-L215 [2] https://wiki.openstack.org/wiki/Translations/ Infrastructure#Translation_percentage_changes
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org
http://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
On 2016-03-22 15:37, Douglas Fish wrote:
I am aware of this additional bug for Liberty: https://bugs.launchpad.net/horizon/+bug/1502326 where we adjusted the list of languages available by default. In Liberty we did not use the same criteria for deciding to include the PO files in the project that we did for including a language in the selection widget in the UI. Looking back, that seems like a strange choice now.
Looking in horizon/openstack_dashboard/locale I see there are 30 or so langauges. I know we don't have that many languages translated to 66% in Horizon. Is there some cleanup that is still remaining, or is this the result of the criteria not quite matching what I'd expect?
We applied the 66 % translation per file - but not overall. So, if you say, you translate 3 out of the 4 files into language XY and then remove them from the tree, the next import will bring them back ;( If you want to change this to: All 4 files need to be sufficiently translated, it would be a different logic we have to apply. What languages we list per default in the dropdown is another criteria, 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
Is there any consensus as the i18n project?
Is it okay that I just update the language list with >66% progress?
Everyone can see the progress at https://translate.openstack.org/iteration/view/horizon/stable-mitaka/languag... I will decide the progress based on this.
This got +1 from Daisy. If okay, I will update the language list based on this. To reduce the change, I don't have a plan to delete translations of languages which do not satisfy the criteria. We continue translations for Mitaka, so more languages can be added in the future stable update. Akihiro 2016-03-23 0:18 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-03-22 15:37, Douglas Fish wrote:
I am aware of this additional bug for Liberty: https://bugs.launchpad.net/horizon/+bug/1502326 where we adjusted the list of languages available by default. In Liberty we did not use the same criteria for deciding to include the PO files in the project that we did for including a language in the selection widget in the UI. Looking back, that seems like a strange choice now.
Looking in horizon/openstack_dashboard/locale I see there are 30 or so langauges. I know we don't have that many languages translated to 66% in Horizon. Is there some cleanup that is still remaining, or is this the result of the criteria not quite matching what I'd expect?
We applied the 66 % translation per file - but not overall.
So, if you say, you translate 3 out of the 4 files into language XY and then remove them from the tree, the next import will bring them back ;(
If you want to change this to: All 4 files need to be sufficiently translated, it would be a different logic we have to apply.
What languages we list per default in the dropdown is another criteria,
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
Is there any consensus as the i18n project?
Is it okay that I just update the language list with >66% progress?
Everyone can see the progress at https://translate.openstack.org/iteration/view/horizon/stable-mitaka/languag... I will decide the progress based on this.
This got +1 from Daisy. If okay, I will update the language list based on this.
+1
To reduce the change, I don't have a plan to delete translations of languages which do not satisfy the criteria. We continue translations for Mitaka, so more languages can be added in the future stable update.
+1 Thanks, KATO Tomoyuki
Akihiro
2016-03-23 0:18 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-03-22 15:37, Douglas Fish wrote:
I am aware of this additional bug for Liberty: https://bugs.launchpad.net/horizon/+bug/1502326 where we adjusted the list of languages available by default. In Liberty we did not use the same criteria for deciding to include the PO files in the project that we did for including a language in the selection widget in the UI. Looking back, that seems like a strange choice now.
Looking in horizon/openstack_dashboard/locale I see there are 30 or so langauges. I know we don't have that many languages translated to 66% in Horizon. Is there some cleanup that is still remaining, or is this the result of the criteria not quite matching what I'd expect?
We applied the 66 % translation per file - but not overall.
So, if you say, you translate 3 out of the 4 files into language XY and then remove them from the tree, the next import will bring them back ;(
If you want to change this to: All 4 files need to be sufficiently translated, it would be a different logic we have to apply.
What languages we list per default in the dropdown is another criteria,
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
As of now, 15 languages satisfy the criteria. https://translate.openstack.org/version-group/view/mitaka-translation/projec... and http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/set... match, so there is no need to update. This is the final check from my side. If your language satisfies this criteria after this mail, feel free to propose a patch to update the language list in Horizon by yourself. I believe various projects will release RC including translations this week. Akihiro 2016-03-25 21:42 GMT+09:00 KATO Tomoyuki <tomo@dream.daynight.jp>:
Is there any consensus as the i18n project?
Is it okay that I just update the language list with >66% progress?
Everyone can see the progress at https://translate.openstack.org/iteration/view/horizon/stable-mitaka/languag... I will decide the progress based on this.
This got +1 from Daisy. If okay, I will update the language list based on this.
+1
To reduce the change, I don't have a plan to delete translations of languages which do not satisfy the criteria. We continue translations for Mitaka, so more languages can be added in the future stable update.
+1
Thanks, KATO Tomoyuki
Akihiro
2016-03-23 0:18 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2016-03-22 15:37, Douglas Fish wrote:
I am aware of this additional bug for Liberty: https://bugs.launchpad.net/horizon/+bug/1502326 where we adjusted the list of languages available by default. In Liberty we did not use the same criteria for deciding to include the PO files in the project that we did for including a language in the selection widget in the UI. Looking back, that seems like a strange choice now.
Looking in horizon/openstack_dashboard/locale I see there are 30 or so langauges. I know we don't have that many languages translated to 66% in Horizon. Is there some cleanup that is still remaining, or is this the result of the criteria not quite matching what I'd expect?
We applied the 66 % translation per file - but not overall.
So, if you say, you translate 3 out of the 4 files into language XY and then remove them from the tree, the next import will bring them back ;(
If you want to change this to: All 4 files need to be sufficiently translated, it would be a different logic we have to apply.
What languages we list per default in the dropdown is another criteria,
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
participants (4)
-
Akihiro Motoki
-
Andreas Jaeger
-
Douglas Fish
-
KATO Tomoyuki