openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #11577
Re: i18n of log message
+1
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.
彭勇
<ppyy@xxxxxxxxxx>
Sent by: To
openstack-bounces Ying Chun Guo/China/IBM@IBMCN,
+zhuadl=cn.ibm.co cc
m@lists.launchpad Thierry Carrez
.net <thierry@xxxxxxxxxxxxx>,
openstack@xxxxxxxxxxxxxxxxxxx
Subject
2012-05-10 下午 Re: [Openstack] i18n of log message
10:46
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 <guoyingc@xxxxxxxxxx>:
> 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.
>
> Regards
> Daisy
>
> openstack-bounces+guoyingc=cn.ibm.com@xxxxxxxxxxxxxxxxxxx wrote on
> 05/09/2012 12:55:48 AM:
>
>> Thierry Carrez <thierry@xxxxxxxxxxxxx>
>> Sent by: openstack-bounces+guoyingc=cn.ibm.com@xxxxxxxxxxxxxxxxxxx
>>
>> 05/09/2012 12:55 AM
>>
>> To
>>
>> openstack@xxxxxxxxxxxxxxxxxxx,
>>
>> cc
>
>
>>
>> Subject
>>
>> 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 : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
--
彭勇 (Peng Yong)
常州贝特康姆(BitComm)软件技术有限公司
地址:常州市科教城信息产业园南4楼
电话:+86.519.68887168
传真:+86.519.68887169
手机:+86.18915883399
邮箱:ppyy@xxxxxxxxxx
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Follow ups
References