Horizon translation importing policy for Havana RC1
Hi all, We discussed the criteria of importing Horizon translation for Havana RC1 and agreed that we will import only 100% translations at the last I18N meeting. I have several questions to clarify. What do you think? I would like to know opinions from I18N team? (1) What is 100% translated? Does 100% mean that all **three** resources (Horizon, Horizon JavaScript, OpenStack Dashboard) are completed? (2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't remove them non-completed translations will be shipped in RC1. (3) What should the language list of the user preference form be? I believe the default language list is important. - All 100% translated languages should be listed. Some languages needs to be added. - Non 100% translated languages should be removed or listed? If so what is the criteria? Over 50% on Transifex? I would like to take care of importing translation into Horizon repo as a Horizon core member. Thanks, Akihiro Motoki <amotoki@gmail.com>
Hi, Akihiro See my answers below. Regards Ying Chun Guo (Daisy) Akihiro Motoki <amotoki@gmail.com> wrote on 2013/09/23 14:37:12:
Akihiro Motoki <amotoki@gmail.com> 2013/09/23 14:37
To
"openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org>,
cc
Subject
[Openstack-i18n] Horizon translation importing policy for Havana RC1
Hi all,
We discussed the criteria of importing Horizon translation for Havana RC1 and agreed that we will import only 100% translations at the last I18N meeting.
I have several questions to clarify. What do you think? I would like to know opinions from I18N team?
(1) What is 100% translated? Does 100% mean that all **three** resources (Horizon, Horizon JavaScript, OpenStack Dashboard) are completed?
I think, our goal is to translated the web UI. The log messages are not included. Completely translating all the strings displayed in the web UI should be regarded as 100% translation. If all the three resources will be displayed in web UI, all of them should be included.
(2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't
remove
them non-completed translations will be shipped in RC1.
I prefer to remove. I'd like to hear others opinion. Will users use partly translated dashboard? If users won't use, I think there is no concerns to remove uncompleted translation.
(3) What should the language list of the user preference form be? I believe the default language list is important. - All 100% translated languages should be listed. Some languages needs to be added. - Non 100% translated languages should be removed or listed? If so what is the criteria? Over 50% on Transifex?
I prefer to list the languages Horizon supports, i.e. those languages whose po/mo files packaged with Horizon. But the list should be easily added or customized. If some people want to provide their own language version after Havana release, they can easily change the language list, add their po files and mo files. They don't need to depend on the formal release.
I would like to take care of importing translation into Horizon repo as a Horizon core member.
Thanks, Akihiro Motoki <amotoki@gmail.com>
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Daisy and Akihiro! On Mon, Sep 23, 2013 at 8:54 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Akihiro Motoki <amotoki@gmail.com> wrote on 2013/09/23 14:37:12:
Akihiro Motoki <amotoki@gmail.com> 2013/09/23 14:37 I have several questions to clarify. What do you think? I would like to know opinions from I18N team?
(1) What is 100% translated? Does 100% mean that all **three** resources (Horizon, Horizon JavaScript, OpenStack Dashboard) are completed?
I think, our goal is to translated the web UI. The log messages are not included. Completely translating all the strings displayed in the web UI should be regarded as 100% translation. If all the three resources will be displayed in web UI, all of them should be included.
The log messages shouldn't even be translated (I knew, I've seen something about log messages, but well, another thread it is then), so we can just copy them over (as it was done for Chinese and I did in Polish)
(2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't remove them non-completed translations will be shipped in RC1.
I prefer to remove. I'd like to hear others opinion. Will users use partly translated dashboard? If users won't use, I think there is no concerns to remove uncompleted translation.
IMHO that depends on what is translated. I'd consider the out of the box horizon dashboards do be a measure of things translated. Everything that isn't enabled by default in the dashboard (like for example DBaaS) is in my opinion not a complete blocker. For example the installation I have at work doesn't have many of those features and probably even with havana they won't be enabled so the users won't ever see any untranslated parts (if they were any for my language ;) But it's hard to test for component completion and it would require putting your faith it in the hands of the specific language coordinators. So right now my proposal is - remove those translations and reconsider a process change for 2013.2.1 or IceHouse
(3) What should the language list of the user preference form be? I believe the default language list is important. - All 100% translated languages should be listed. Some languages needs to be added. - Non 100% translated languages should be removed or listed? If so what is the criteria? Over 50% on Transifex?
I prefer to list the languages Horizon supports, i.e. those languages whose po/mo files packaged with Horizon. But the list should be easily added or customized. If some people want to provide their own language version after Havana release, they can easily change the language list, add their po files and mo files. They don't need to depend on the formal release.
Can't really answer that because it depends on question 2 (and also I have no idea how to answer that anyway :( Regards, -- Łukasz [DeeJay1] Jernaś
HI,
(2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't remove them non-completed translations will be shipped in RC1.
I prefer to remove. I'd like to hear others opinion. Will users use partly translated dashboard? If users won't use, I think there is no concerns to remove uncompleted translation.
IMHO that depends on what is translated. I'd consider the out of the box horizon dashboards do be a measure of things translated. Everything that isn't enabled by default in the dashboard (like for example DBaaS) is in my opinion not a complete blocker. For example the installation I have at work doesn't have many of those features and probably even with havana they won't be enabled so the users won't ever see any untranslated parts (if they were any for my language ;)
AFAIK, strings only used in the following files are rarely visible in Web UI in Havana release. Around 100 strings can be omitted. openstack_dashboard/dashboards/project/databases (DBaaS incubated project) : ~50 openstack_dashboard/dashboards/project/database_backups (ditto) : ~25 openstack_dashboard/dashboards/router/nexus1000v (only needed by folks who use Neutron Cisco plugin) : ~30
But it's hard to test for component completion and it would require putting your faith it in the hands of the specific language coordinators. So right now my proposal is - remove those translations and reconsider a process change for 2013.2.1 or IceHouse
As I wrote in the other mail, I agree 100% is not the required criteria. The important criteria is how each language translators/coordinator has confidence on their ones. If they think it is ready to go, it is worth being shipped as a part of the release. Thanks, Akihiro On Tue, Sep 24, 2013 at 5:16 AM, Łukasz Jernaś <deejay1@srem.org> wrote:
Hi Daisy and Akihiro!
On Mon, Sep 23, 2013 at 8:54 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Akihiro Motoki <amotoki@gmail.com> wrote on 2013/09/23 14:37:12:
Akihiro Motoki <amotoki@gmail.com> 2013/09/23 14:37 I have several questions to clarify. What do you think? I would like to know opinions from I18N team?
(1) What is 100% translated? Does 100% mean that all **three** resources (Horizon, Horizon JavaScript, OpenStack Dashboard) are completed?
I think, our goal is to translated the web UI. The log messages are not included. Completely translating all the strings displayed in the web UI should be regarded as 100% translation. If all the three resources will be displayed in web UI, all of them should be included.
The log messages shouldn't even be translated (I knew, I've seen something about log messages, but well, another thread it is then), so we can just copy them over (as it was done for Chinese and I did in Polish)
(2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't remove them non-completed translations will be shipped in RC1.
I prefer to remove. I'd like to hear others opinion. Will users use partly translated dashboard? If users won't use, I think there is no concerns to remove uncompleted translation.
IMHO that depends on what is translated. I'd consider the out of the box horizon dashboards do be a measure of things translated. Everything that isn't enabled by default in the dashboard (like for example DBaaS) is in my opinion not a complete blocker. For example the installation I have at work doesn't have many of those features and probably even with havana they won't be enabled so the users won't ever see any untranslated parts (if they were any for my language ;) But it's hard to test for component completion and it would require putting your faith it in the hands of the specific language coordinators. So right now my proposal is - remove those translations and reconsider a process change for 2013.2.1 or IceHouse
(3) What should the language list of the user preference form be? I believe the default language list is important. - All 100% translated languages should be listed. Some languages needs to be added. - Non 100% translated languages should be removed or listed? If so what is the criteria? Over 50% on Transifex?
I prefer to list the languages Horizon supports, i.e. those languages whose po/mo files packaged with Horizon. But the list should be easily added or customized. If some people want to provide their own language version after Havana release, they can easily change the language list, add their po files and mo files. They don't need to depend on the formal release.
Can't really answer that because it depends on question 2 (and also I have no idea how to answer that anyway :(
Regards, -- Łukasz [DeeJay1] Jernaś
-- Akihiro MOTOKI <amotoki@gmail.com>
Hi all, Please find my comments inline. Can you coordinate which languages should be contained in the repo? On Mon, Sep 23, 2013 at 3:54 PM, Ying Chun Guo <guoyingc@cn.ibm.com<javascript:;>> wrote:
Hi, Akihiro
See my answers below.
Regards Ying Chun Guo (Daisy)
Akihiro Motoki <amotoki@gmail.com <javascript:;>> wrote on 2013/09/23 14:37:12:
Hi all,
We discussed the criteria of importing Horizon translation for Havana RC1 and agreed that we will import only 100% translations at the last I18N meeting.
I have several questions to clarify. What do you think? I would like to know opinions from I18N team?
(1) What is 100% translated? Does 100% mean that all **three** resources (Horizon, Horizon JavaScript, OpenStack Dashboard) are completed?
I think, our goal is to translated the web UI. The log messages are not included. Completely translating all the strings displayed in the web UI should be regarded as 100% translation. If all the three resources will be displayed in web UI, all of them should be included.
It is hard to distinguish user visible strings from log messages on Transifex. It depends on each language coordinators? Luckily enough, by grepping the code, there are only a few log messages marked as translatable, It means it doesn't matter much.
(2) Do we remove translations not completed (<100%) from Horizon repo? RC1 release is created from the repo. This means that if we don't remove them non-completed translations will be shipped in RC1.
I prefer to remove. I'd like to hear others opinion. Will users use partly translated dashboard? If users won't use, I think there is no concerns to remove uncompleted translation.
I would like to follow the community decision. I agree it is a good start line to remove non 100% translated languages from the repo. However IMO partly translated dashboard is still useful for some languages. If a language coordinator/translator requests to include it, it is worth included even if it is not 100% translated. I saw a similar opinion from a Dutch translator in the general list yesterday.
(3) What should the language list of the user preference form be? I believe the default language list is important. - All 100% translated languages should be listed. Some languages needs to be added. - Non 100% translated languages should be removed or listed? If so what is the criteria? Over 50% on Transifex?
I prefer to list the languages Horizon supports, i.e. those languages whose po/mo files packaged with Horizon.
Fair enough. Agree.
But the list should be easily added or customized. If some people want to provide their own language version after Havana release, they can easily change the language list, add their po files and mo files. They don't need to depend on the formal release.
Yes, Users can customize the language list by editing OpenStack Dashboard setting files (settings.py). Note that OpenStack Dashboard has two settings files: settings.py and local_settings.py, local_settings.py contains configuration parameters which users usually configure, and settings.py contains parameters which are less required to configure. Regards, Akihiro
I would like to take care of importing translation into Horizon repo as a Horizon core member.
Thanks, Akihiro Motoki <amotoki@gmail.com <javascript:;>>
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <javascript:;> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Akihiro MOTOKI <amotoki@gmail.com <javascript:;>> -- Akihiro MOTOKI <amotoki@gmail.com>
participants (3)
-
Akihiro Motoki
-
Ying Chun Guo
-
Łukasz Jernaś