<font size=2 face="sans-serif">Doug,</font>
<br>
<br><font size=2 face="sans-serif">I am glad that this has come up as Mike
Perez and I were talking about this on Friday and even the documentation
that you point to here: </font><a href=https://wiki.openstack.org/wiki/LoggingStandards#Log_Translation target=_blank><font size=2 color=blue face="Calibri"><u>https://wiki.openstack.org/wiki/LoggingStandards#Log_Translation</u></font></a><font size=2 face="Calibri">
</font><font size=2 face="sans-serif">is not clear. At least, not
to me.</font>
<br>
<br><font size=2 face="sans-serif">Should I interpret that to mean that
debug messages should be created using LOG.debug and not use _() on the
message being sent? If that is the case, there are many places where
LOG.debug is using _() on the message being passed. Should we be
planning to remove those? I just want to understand what the plan
going forward is there, especially given that the documentation currently
says: "</font><font size=3>Debug messages are not translated,
for now. </font><font size=2 face="sans-serif">"</font>
<br>
<br><font size=2 face="sans-serif">With regards to _LI(), etc. It
appears that this should be used in place of LOG.info _("Message").
Should we be enforcing a move from LOG.* to _L* in new code that
is coming in?</font>
<br>
<br><font size=2 face="sans-serif">Appreciate your thoughts on the subject!<br>
</font>
<br><font size=3><b><i><br>
Jay S. Bryant</i></b><br>
<i>IBM Cinder Subject Matter Expert
& Cinder Core Member</i><br>
Department 7YLA, Building 015-2, Office E125, Rochester, MN<br>
Telephone: (507) 253-4270, FAX (507) 253-6410<br>
TIE Line: 553-4270<br>
E-Mail: jsbryant@us.ibm.com<br>
--------------------------------------------------------------------<br>
All the world's a stage and most of us are desperately unrehearsed.<br>
-- Sean
O'Casey<br>
--------------------------------------------------------------------</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Doug Hellmann <doug.hellmann@dreamhost.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Joshua Harlow <harlowja@yahoo-inc.com>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"OpenStack Development
Mailing List \(not for usage questions\)" <openstack-dev@lists.openstack.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">03/14/2014 03:54 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
does exception need localize or not?</font>
<br>
<hr noshade>
<br>
<br>
<br>
<br><font size=3><br>
</font>
<br><font size=3>On Thu, Mar 13, 2014 at 6:44 PM, Joshua Harlow <</font><a href="mailto:harlowja@yahoo-inc.com" target=_blank><font size=3 color=blue><u>harlowja@yahoo-inc.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=2 face="Calibri"><b>From: </b>Doug Hellmann <</font><a href=mailto:doug.hellmann@dreamhost.com target=_blank><font size=2 color=blue face="Calibri"><u>doug.hellmann@dreamhost.com</u></font></a><font size=2 face="Calibri">><b><br>
Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)"
<</font><a href="mailto:openstack-dev@lists.openstack.org" target=_blank><font size=2 color=blue face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size=2 face="Calibri">><b><br>
Date: </b>Thursday, March 13, 2014 at 12:44 PM<b><br>
To: </b>"OpenStack Development Mailing List (not for usage questions)"
<</font><a href="mailto:openstack-dev@lists.openstack.org" target=_blank><font size=2 color=blue face="Calibri"><u>openstack-dev@lists.openstack.org</u></font></a><font size=2 face="Calibri">><b><br>
Subject: </b>Re: [openstack-dev] does exception need localize or not?</font>
<br>
<br>
<br><font size=2 face="Calibri"><br>
</font>
<br><font size=2 face="Calibri">On Thu, Feb 27, 2014 at 3:45 AM, yongli
he <</font><a href=mailto:yongli.he@intel.com target=_blank><font size=2 color=blue face="Calibri"><u>yongli.he@intel.com</u></font></a><font size=2 face="Calibri">>
wrote:</font>
<br><font size=2 face="Calibri">refer to :</font><font size=2 color=blue face="Calibri"><u><br>
</u></font><a href=https://wiki.openstack.org/wiki/Translations target=_blank><font size=2 color=blue face="Calibri"><u>https://wiki.openstack.org/wiki/Translations</u></font></a><font size=2 face="Calibri"><br>
<br>
now some exception use _ and some not. the wiki suggest do not to
do that. but i'm not sure.<br>
<br>
what's the correct way?<br>
<br>
<br>
F.Y.I <br>
</font>
<br><font size=3 face="Calibri"><b>What To Translate</b></font>
<br><font size=2 color=#2f2f2f face="Arial">At present the convention is
to translate <i>all</i> user-facing strings. This means API messages,
CLI responses, documentation, help text, etc.</font>
<br><font size=2 color=#2f2f2f face="Arial">There has been a lack of consensus
about the translation of log messages; the current ruling is that while
it is not against policy to mark log messages for translation if your project
feels strongly about it, translating log messages is not actively encouraged.</font>
<p>
<br><font size=2 face="Calibri">I've updated the wiki to replace that paragraph
with a pointer to </font><a href=https://wiki.openstack.org/wiki/LoggingStandards#Log_Translation target=_blank><font size=2 color=blue face="Calibri"><u>https://wiki.openstack.org/wiki/LoggingStandards#Log_Translation</u></font></a><font size=2 face="Calibri">
which explains the log translation rules. We will be adding the job needed
to have different log translations during Juno.</font>
<br>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 color=#2f2f2f face="Arial">Exception text should <i>not</i> be
marked for translation, becuase if an exception occurs there is no guarantee
that the translation machinery will be functional.</font>
<p>
<br><font size=2 face="Calibri">This makes no sense to me. Exceptions should
be translated. By far the largest number of errors will be presented to
users through the API or through Horizon (which gets them from the API).
We will ensure that the translation code does its best to fall back to
the original string if the translation fails.</font>
<br>
<br><font size=2 face="Calibri">Doug</font>
<br>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"><br>
<br>
Regards</font><font size=2 color=#8f8f8f face="Calibri"><br>
Yongli He<br>
</font>
<br><font size=2 face="Calibri"><br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size=2 color=blue face="Calibri"><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target=_blank><font size=2 color=blue face="Calibri"><u>OpenStack-dev@lists.openstack.org</u></font></a><font size=2 color=blue face="Calibri"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target=_blank><font size=2 color=blue face="Calibri"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size=2 face="Calibri"><br>
</font>
<br>
<br>
<br><font size=2 face="Calibri">I think this question comes up every 3
months, haha ;)</font>
<br>
<br><font size=2 face="Calibri">As we continue to expand all the libraries
in </font><a href="https://github.com/openstack/requirements/blob/master/global-requirements.txt" target=_blank><font size=2 color=blue face="Calibri"><u>https://github.com/openstack/requirements/blob/master/global-requirements.txt</u></font></a><font size=2 face="Calibri"> and
knowing that those libraries likely don't translate there exceptions (probably
in the majority of cases, especially in non-openstack/oslo 3rd party libraries)
are we chasing a ideal that can not be caught?</font>
<br>
<br><font size=2 face="Calibri">Food for thought,</font>
<br>
<br><font size=2>We can't control what the other projects do, but that
doesn't prevent us from doing more. </font>
<br>
<br><font size=2>Doug</font>
<br>
<br><font size=3> </font>
<br>
<br><font size=2 face="Calibri">-Josh</font>
<br><tt><font size=2>_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>