<html><body>
<p><font size="2" face="sans-serif">I18N is an architecture decision. Besides developers, we should also consult customers' options.</font><br>
<br>
<font size="2" face="sans-serif">I18N is a very big scope. It includes not only translation, but also Date/time format, number format, </font><br>
<font size="2" face="sans-serif">or even the input of non-English characters. Surely I18N will take some efforts. But considering</font><br>
<font size="2" face="sans-serif">OpenStack may have a long history, it deserve us to pay some time to work on it. We need to consider </font><br>
<font size="2" face="sans-serif">it carefully. Maybe we can just pick out several very popular locales/languages and work on these localization</font><br>
<font size="2" face="sans-serif">firstly. It will ensure we have a correct architecture to suppor I18N, with a not very big effort.</font><br>
<br>
<font size="2" face="sans-serif">I'd like to help on the process documenting.</font><br>
<br>
<font size="2" face="sans-serif">Regards</font><br>
<font size="2" face="sans-serif">Daisy</font><br>
<br>
<tt><font size="2">openstack-bounces+guoyingc=cn.ibm.com@lists.launchpad.net wrote on 05/09/2012 12:55:48 AM:<br>
<br>
> Thierry Carrez <thierry@openstack.org> </font></tt><br>
<tt><font size="2">> Sent by: openstack-bounces+guoyingc=cn.ibm.com@lists.launchpad.net<br>
> </font></tt><br>
<tt><font size="2">> 05/09/2012 12:55 AM</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> openstack@lists.launchpad.net, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack] i18n of log message</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo wrote:<br>
> > [...]<br>
> > So I prefer option 2. As it is said that option 3 being not<br>
> > significantly more work than option 2, so option 3 is also acceptable<br>
> > for me.<br>
> <br>
> So there is no strong consensus so far :) One important prerequisite of<br>
> whatever solution we end up choosing is that it should be the same level<br>
> across all OpenStack core projects. Consistency is important... So we<br>
> should definitely ask PTLs which options they are ready to support, as<br>
> it may seriously reduce our options.<br>
> <br>
> We should also have a I18N advocacy czar that will push whatever option<br>
> is chosen to completion by documenting the process, encouraging CI /<br>
> translators / devs to do any needed work. Anyone up to it ?<br>
> <br>
> -- <br>
> Thierry Carrez (ttx)<br>
> Release Manager, OpenStack<br>
> <br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
> Post to : openstack@lists.launchpad.net<br>
> Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
> <br>
</font></tt></body></html>