[openstack-dev] Need for a String Freeze for documenters/translators

Sean Dague sdague at linux.vnet.ibm.com
Fri Jan 25 15:06:59 UTC 2013

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 to.

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.


Sean Dague
IBM Linux Technology Center
email: sdague at linux.vnet.ibm.com
alt-email: sldague at us.ibm.com

More information about the OpenStack-dev mailing list