[openstack-dev] Need for a String Freeze for documenters/translators
jogo at cloudscaling.com
Fri Jan 25 15:41:08 UTC 2013
On Fri, Jan 25, 2013 at 10:06 AM, Sean Dague <sdague at linux.vnet.ibm.com>wrote:
> On 01/25/2013 09:14 AM, Daniel P. Berrange wrote:
> IMHO, LOG.error/warn/info can be marked for translation, since those
>> are used for scenarios where we are trying to alert the sysadmin to
>> something, but LOG.debug should be left untranslated as they are for
>> vendors/developers primarily.
>> In other words, if we remove translation from all LOG.debug() messages,
>> I'd be fine with a string freeze on what's left.
> A lot of that has come from not having a formal policy on what's
> translatable, so it's all adhoc, and eventually that's where we've gotten
> I'd be +1 on to LOG.error/warn/info as i18n, and LOG.debug to have that
> removed if we could bake that into policy. There would still be time to fix
> that for grizzly, and maybe even get a hacking.py extension to check for
> and enforce that.
A quick git grep in nova shows that about half the LOG messages are
LOG.debug, so not translating them should have a significant impact on the
number of strings requiring translation.
nova$ git grep "LOG\.error" | wc
129 795 11477
nova$ git grep "LOG\.warn" | wc
150 1023 13736
$ git grep "LOG\.info" | wc
184 1107 16886
nova$ git grep "LOG\.debug" | wc
689 4141 63752
> Sean Dague
> IBM Linux Technology Center
> email: sdague at linux.vnet.ibm.com
> alt-email: sldague at us.ibm.com
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev