A few key points:
1. I would re-frame the options as â€œEnglish Onlyâ€, â€œUser-Facing Messagesâ€, or â€œAll Stringsâ€. These three categories more accurately cover the purposes of translating different scopes in the application. The key difference being that web interfaces and API/CLI messages are both user-facing, and should be treated similarly.
2. Horizon has already strongly committed to i18n for user-facing messages, and weâ€™re keeping an eye on l10n (localization) as well in the future. Nova also has strong i18n support; as such Iâ€™d see â€œEnglish Onlyâ€ as a regression and a disservice to the community.
3. With all due consideration of input from the community, this is ultimately going to have to be decided by the PPB since it needs to span all projects and since unanimous community consensus is unlikely.
I, personally, will continue to advocate for translation, internationalization and localization for all user-facing messages; and Iâ€™ll do what I can to keep supporting the community in its translation efforts. Iâ€™m happy to answer questions as well.
All the best,
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Hua ZZ Zhang
Sent: Thursday, May 10, 2012 5:05 PM
Cc: firstname.lastname@example.org; Thierry Carrez; email@example.com
Subject: Re: [Openstack] i18n of log message
From the perspective of developer and English user, totally agree with you to keep it simple. But OpenStack is an BIG community includes lots of countries and users, we should also consider their requirements and opinions. To mature this platform and community, it is really important.
[Inactive hide details for å½å‹‡ ---2012-05-10 ä¸‹åˆ 11:57:19---å½å‹‡ <firstname.lastname@example.org>]å½å‹‡ ---2012-05-10 ä¸‹åˆ 11:57:19---å½å‹‡ <email@example.com<mailto:firstname.lastname@example.org>>
Sent by: email@example.com<mailto:firstname.lastname@example.org>
2012-05-10 ä¸‹åˆ 10:46
Ying Chun Guo/China/IBM@IBMCN,
Thierry Carrez <email@example.com<mailto:firstname.lastname@example.org>>, email@example.com<mailto:firstname.lastname@example.org>
Re: [Openstack] i18n of log message
we are here talking about I18N of log information
i prefer to English only log:
1. easy to search and share
2. easy to maintain
2012/5/10 Ying Chun Guo <email@example.com<mailto:firstname.lastname@example.org>>: > I18N is an architecture decision. Besides developers, we should also consult
> customers' options.
> I18N is a very big scope. It includes not only translation, but also
> Date/time format, number format,
> or even the input of non-English characters. Surely I18N will take some
> efforts. But considering
> OpenStack may have a long history, it deserve us to pay some time to work on
> it. We need to consider
> it carefully. Maybe we can just pick out several very popular
> locales/languages and work on these localization
> firstly. It will ensure we have a correct architecture to suppor I18N, with
> a not very big effort.
> I'd like to help on the process documenting.
> email@example.com<mailto:firstname.lastname@example.org> wrote on
> 05/09/2012 12:55:48 AM:
>> Thierry Carrez <email@example.com<mailto:firstname.lastname@example.org>>
>> Sent by: email@example.com<mailto:firstname.lastname@example.org>
>> 05/09/2012 12:55 AM
>> Re: [Openstack] i18n of log message
>> Ying Chun Guo wrote:
>> > [...]
>> > So I prefer option 2. As it is said that option 3 being not
>> > significantly more work than option 2, so option 3 is also acceptable
>> > for me.
>> So there is no strong consensus so far :) One important prerequisite of
>> whatever solution we end up choosing is that it should be the same level
>> across all OpenStack core projects. Consistency is important... So we
>> should definitely ask PTLs which options they are ready to support, as
>> it may seriously reduce our options.
>> We should also have a I18N advocacy czar that will push whatever option
>> is chosen to completion by documenting the process, encouraging CI /
>> translators / devs to do any needed work. Anyone up to it ?
>> Thierry Carrez (ttx)
>> Release Manager, OpenStack
>> Mailing list: https://launchpad.net/~openstack
>> Post to : email@example.com<mailto:firstname.lastname@example.org>
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
> Mailing list: https://launchpad.net/~openstack
> Post to : email@example.com<mailto:firstname.lastname@example.org>
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
å½å‹‡ (Peng Yong)
Mailing list: https://launchpad.net/~openstack
Post to : email@example.com<mailto:firstname.lastname@example.org>
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp