Yeah I agree with that. If it shouldn't be translated, it would be better not to have it in Tx. Otherwise is hard to tell when to not translate some strings. Thanks, Gabriel. On Tue, Sep 24, 2013 at 6:14 AM, Łukasz Jernaś <deejay1@srem.org> wrote:
Hi,
Like I said in my previous mail I'd still opt for not marking them as translatable instead of seperating. This will break most log parsing systems and even if you could make translation aware log parsing systems, it would require coordination on both sides and frankly this is the first project I can remember which has translatable logs…
Regards, -- Łukasz Jernaś
Now log messages are not separated in Horizon, and even nova, glance and etc. I'm going to propose to separate log messages and user facing messages in next design summit. Thus our translation team can focus on the user facing messages
On Tue, Sep 24, 2013 at 9:43 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote: translation.
Sorry, no guidelines now.
Regards Ying Chun Guo (Daisy)
Gabriel Wainer <gabrielcw@gmail.com> wrote on 2013/09/24 04:44:43:
Gabriel Wainer <gabrielcw@gmail.com> 2013/09/24 04:44
To
openstack-i18n@lists.openstack.org,
cc
Subject
[Openstack-i18n] Log messages translation
I saw this in another post, so to avoid confusion I'll ask here.
How can we know what are log messages and what aren't in the translation strings? I ended up translating all messages, even logs I believe. Sure that some technical words and var names should be copied but i think it's ok to translate logs. Any guidelines on that?
Thanks, Gabriel Wainer _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n