<html><body>
<p><font size="2" face="sans-serif">Another solution might be making the LOG message easily to switch languages.</font><br>
<br>
<font size="2" face="sans-serif">We can find some easy ways for users to change languages at run time, for example, </font><br>
<font size="2" face="sans-serif">changing languages by setting an environment variable.</font><br>
<br>
<font size="2" face="sans-serif">Thus the users can both take the advantages of localized LOG messages and English LOG</font><br>
<font size="2" face="sans-serif">messages.</font><br>
<br>
<font size="2" face="sans-serif">How about this idea?</font><br>
<br>
<font size="2" face="sans-serif">Daisy</font><br>
<br>
<tt><font size="2">Eric Windisch <eric@cloudscaling.com> wrote on 2012/11/08 01:26:28:<br>
<br>
> Eric Windisch <eric@cloudscaling.com> </font></tt><br>
<tt><font size="2">> 2012/11/08 01:26</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 Wednesday, November 7, 2012 at 11:57 AM, Sean Dague wrote:</font></tt><br>
<tt><font size="2">> I think that assumes that everyone uses the same search engines and user </font></tt><br>
<tt><font size="2">> forums for their content. I think if you look at China in particular </font></tt><br>
<tt><font size="2">> this isn't going to be the case. </font></tt><br>
<tt><font size="2">> <a href="http://chineseseoshifu.com/china-search-engine-market-share/">http://chineseseoshifu.com/china-search-engine-market-share/</a></font></tt><br>
<tt><font size="2">> <br>
> As previously discussed, there is the option to add universal <br>
> identifiers for logs. Then, logs could be searched by either their <br>
> universal identifier, or their native text. It could also be used <br>
> to translate messages post-defacto. Unfortunately, this does <br>
> introduce some complex problems to making the numbers unique, <br>
> relatively static between releases, etc.</font></tt><br>
<tt><font size="2">> <br>
> One advantage is that we could potentially use such identifiers to <br>
> allow searching across differences in the text within the same <br>
> language, across releases. If a log message were changed between <br>
> releases, but the triggering event has not changed, the universal <br>
> identifier could potentially remain unchanged. Again, that might <br>
> not be easy to implement, but it is a nice concept.</font></tt><br>
<tt><font size="2">> <br>
> In fact, now that I think abut it, is there a reason we use _() from<br>
> callers instead of just having the log formatter wrap this for us?</font></tt><br>
<tt><font size="2">> <br>
> Regards,</font></tt><br>
<tt><font size="2">> Eric Windisch_______________________________________________<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>
</font></tt></body></html>