<html><body>
<p><font size="2" face="sans-serif">Yeah, that one is a good reason.</font><br>
<br>
<font size="2" face="sans-serif">Can we have the agreement that </font><tt><font size="2">implicit i18n</font></tt><font size="2" face="sans-serif"> doesn't work for us?</font><br>
<font size="2" face="sans-serif">So we have to choose </font><tt><font size="2">explicit</font></tt><font size="2" face="sans-serif"> i18n and set clear rules for developers to follow.</font><br>
<br>
<tt><font size="2">Johannes Erdfelt <johannes@erdfelt.com> wrote on 2012/11/08 02:23:15:<br>
<br>
> Johannes Erdfelt <johannes@erdfelt.com> </font></tt><br>
<tt><font size="2">> 2012/11/08 02:23</font></tt><br>
<tt><font size="2">> <br>
> Please respond to<br>
> OpenStack Development Mailing List <openstack-dev@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> OpenStack Development Mailing List <openstack-dev@lists.openstack.org>, </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-dev] Less of coding standard for i18n of LOG messages</font></tt><br>
<tt><font size="2">> <br>
> On Wed, Nov 07, 2012, Kevin L. Mitchell <kevin.mitchell@rackspace.com> wrote:<br>
> > 1. The tools which extract strings to be translated expect those<br>
> > strings to be wrapped in _().<br>
> <br>
> Gah, I always forget this and I've had to explain to other people in the<br>
> past too :(<br>
> <br>
> JE<br>
> <br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> <br>
</font></tt></body></html>