On 04/03/2014 10:19 PM, Peng Wu wrote:
Hi,
Recently I read the "Separate translation domain for log messages"
blueprint[1], and I found that we can store both English Message Log and
Translated Message Log with some configurations.
I am an i18n Software Engineer, and we are thinking about "Add message
IDs for log messages" blueprint[2]. My thought is that if we can store
both English Message Log and Translated Message Log, we can skip the
need of Log Message ID Generation.
I also commented the "Add message IDs for log messages" blueprint[2].
If the servers always store English Log Messages, maybe we don't need
the "Add message IDs for log messages" blueprint[2] any more.
Feel free to comment this proposal.
Thanks,
Peng Wu
Refer URL:
[1]
https://blueprints.launchpad.net/oslo/+spec/log-messages-translation-domain
[2] https://blueprints.launchpad.net/oslo/+spec/log-messages-id
As I recall, there were more reasons for log message ids than just i18n
issues. There's also the fact that an error message might change
significantly from one release to another, but if it's still addressing
the same issue then the message id could be left alone so searching for
it would still return relevant results, regardless of the release.
That said, I don't know if anyone is actually working on the message id
blueprint so I'm not sure how much it matters at this point. :-)
-Ben
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
