Open Stack

Whole idea with log translation is half-backed anyway. About the half of
important log messages contain output of things outside openstack. Libvirt,
ip, sudo, kernel, etc. In any i18n installation there going to be some
amount of untranslated messages. This kills whole idea of localization.

Modern operator ought to know English at 'technical reading' level anyway.
Therefore, localization does not achieve it goal, but cause pain instead:
search segmentation, slightly misleading translation (f.e. 'stream' and
'thread' both translate into Russian 'поток', which brings ambiguity),
different system may use slightly different translation, causing even more
mess.

As Russian speaker and openstack operator I definitely don't want to have
logs translation.

On Mar 10, 2017 4:42 PM, "Doug Hellmann" <doug at doughellmann.com> wrote:

There is a discussion on the -dev mailing list about the i18n team
decision to stop translating log messages [1]. The policy change means
that we may be able to clean up quite a lot of "clutter" throughout the
service code, because without anyone actually translating the messages
there is no need for the markup code used to tag those strings.

If we do remove the markup from log messages, we will be effectively
removing "multilingual logs" as a feature. Given the amount of work
and code churn involved in the first roll out, I would not expect
us to restore that feature later.

Therefore, before we take what would almost certainly be an
irreversible action, we would like some input about whether log
message translations are useful to anyone. Please let us know if
you or your customers use them.

Thanks,
Doug

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-
March/113365.html

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170311/5e7f38ef/attachment.html>