<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style='font-family: Verdana,Geneva,sans-serif'>
<p>On 2014-02-27 02:45, yongli he wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->refer to :<br /><a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Translations">https://wiki.openstack.org/wiki/Translations</a><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 /><br />
<h4 style="margin: 10px 0px; font-weight: bold; line-height: 20px; color: #333333; text-rendering: optimizelegibility; font-size: 17.5px; font-style: normal; font-variant: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span id="What_To_Translate" class="mw-headline">What To Translate</span></h4>
<p style="margin: 0px 0px 10px; color: #333333; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 20px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">At present the convention is to translate<span class="Apple-converted-space"> </span><em>all</em><span class="Apple-converted-space"> </span>user-facing strings. This means API messages, CLI responses, documentation, help text, etc.</p>
<p style="margin: 0px 0px 10px; color: #333333; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 20px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">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.</p>
<p style="margin: 0px 0px 10px; color: #333333; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 20px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Exception text should<span class="Apple-converted-space"> </span><em>not</em><span class="Apple-converted-space"> </span>be marked for translation, becuase if an exception occurs there is no guarantee that the translation machinery will be functional.</p>
<br /><br /> Regards<br /> Yongli He</blockquote>
<p>Interestingly, although that is very clear that we should not translate exceptions, we do anyway in many (most?) OpenStack projects. For the time being I would say go with whatever the project you're contributing to does, but it's a discussion we may need to have since the reasoning on the wiki page seems sound to me, especially now that lazy translation makes the translation mechanism so much more complicated.</p>
<p>-Ben</p>
<div> </div>
</body></html>