On 04/07/2014 11:57 PM, Peng Wu wrote:
Thanks for the comments.
Maybe we could just search the English log. :-)
Right, but the problem is that the English log is not guaranteed to
remain the same. An (extremely contrived) example:
Say we have a log message like Failed to not find entity:
Thanks, I see. :-)
On Tue, 2014-04-08 at 10:23 -0500, Ben Nemec wrote:
On 04/07/2014 11:57 PM, Peng Wu wrote:
Thanks for the comments.
Maybe we could just search the English log. :-)
Right, but the problem is that the English log is not guaranteed to
remain the same. An (extremely
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
Thanks for the comments.
Maybe we could just search the English log. :-)
But I just find it is hard to meet all requirements of log message id,
Just some thought that we can avoid the message id generation by using
the English log.
For debug purpose, we can just read the English log.
Regards,
