Yeah, that one is a good reason. Can we have the agreement that implicit i18n doesn't work for us? So we have to choose explicit i18n and set clear rules for developers to follow. Johannes Erdfelt <johannes at erdfelt.com> wrote on 2012/11/08 02:23:15: > Johannes Erdfelt <johannes at erdfelt.com> > 2012/11/08 02:23 > > Please respond to > OpenStack Development Mailing List <openstack-dev at lists.openstack.org> > > To > > OpenStack Development Mailing List <openstack-dev at lists.openstack.org>, > > cc > > Subject > > Re: [openstack-dev] Less of coding standard for i18n of LOG messages > > On Wed, Nov 07, 2012, Kevin L. Mitchell <kevin.mitchell at rackspace.com> wrote: > > 1. The tools which extract strings to be translated expect those > > strings to be wrapped in _(). > > Gah, I always forget this and I've had to explain to other people in the > past too :( > > JE > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121108/bedd92de/attachment.html>