<html><body>
<p><font size="2" face="sans-serif">Actually, I'm with you, </font><tt><font size="2">Łukasz</font></tt><font size="2" face="sans-serif">.</font><br>
<br>
<font size="2" face="sans-serif">We have done a wonderful job in Horizon translation in Havana release.</font><br>
<font size="2" face="sans-serif">I hope to resolve this issue in IceHouse.</font><br>
<font size="2" face="sans-serif">So that we can cover more components' translations in next release.</font><br>
<br>
<font size="2" face="sans-serif">But I haven't a clear mind about how to handle this issue yet.</font><br>
<font size="2" face="sans-serif">Remove _() from the log message?</font><br>
<font size="2" face="sans-serif">Move to another translation domain?</font><br>
<font size="2" face="sans-serif">Or introduce more configuration parameters to decide which level of log</font><br>
<font size="2" face="sans-serif">messages will be shown in locale language?</font><br>
<br>
<font size="2" face="sans-serif">I'm going to bring this discussion to the design summit.</font><br>
<font size="2" face="sans-serif">Before that, we can have a sufficient discussion within I18n mail list at first.</font><br>
<br>
<font size="2" face="sans-serif">Regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<tt><font size="2">Łukasz Jernaś <deejay1@srem.org> wrote on 2013/09/27 19:00:42:<br>
<br>
> Łukasz Jernaś <deejay1@srem.org> </font></tt><br>
<tt><font size="2">> 2013/09/27 19:00</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> openstack-i18n <openstack-i18n@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-i18n] Log messages translation</font></tt><br>
<tt><font size="2">> <br>
> Hi,<br>
> <br>
> Maybe we should bring that issue up on OpenStack-dev for IceHouse<br>
> again? IMHO every non user facing log message shouldn't be marked for<br>
> translation, but then again the discussion in January<br>
> <a href="http://lists.openstack.org/pipermail/openstack-dev/2013-January/004259.html">http://lists.openstack.org/pipermail/openstack-dev/2013-January/004259.html</a><br>
> made me wonder what the rationale for that was anyway (since I'm new<br>
> to the community)...<br>
> <br>
> Regards,<br>
> -- <br>
> Łukasz [DeeJay1] Jernaś<br>
> <br>
> On Tue, Sep 24, 2013 at 2:19 PM, Parag N(पराग़) <panemade@gmail.com> wrote:<br>
> > Hi,<br>
> ><br>
> > On Tue, Sep 24, 2013 at 2:44 PM, Łukasz Jernaś <deejay1@srem.org> wrote:<br>
> >><br>
> >> Hi,<br>
> >><br>
> >> Like I said in my previous mail I'd still opt for not marking them as<br>
> >> translatable instead of seperating. This will break most log parsing<br>
> >> systems and even if you could make translation aware log parsing<br>
> >> systems, it would require coordination on both sides and frankly this<br>
> >> is the first project I can remember which has translatable logs…<br>
> >><br>
> ><br>
> ><br>
> > I agree here, log messages should not be translated or rather should not be<br>
> > made available in pot/po files for translation.<br>
> ><br>
> > Regards,<br>
> > Parag.<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Openstack-i18n mailing list<br>
> > Openstack-i18n@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> ><br>
> <br>
> _______________________________________________<br>
> Openstack-i18n mailing list<br>
> Openstack-i18n@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
</font></tt></body></html>