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
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 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
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ś On Tue, Sep 24, 2013 at 9:43 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
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 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
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
Hi, On Tue, Sep 24, 2013 at 2:44 PM, Ł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…
I agree here, log messages should not be translated or rather should not be made available in pot/po files for translation. Regards, Parag.
Hi, Maybe we should bring that issue up on OpenStack-dev for IceHouse again? IMHO every non user facing log message shouldn't be marked for translation, but then again the discussion in January http://lists.openstack.org/pipermail/openstack-dev/2013-January/004259.html made me wonder what the rationale for that was anyway (since I'm new to the community)... Regards, -- Łukasz [DeeJay1] Jernaś On Tue, Sep 24, 2013 at 2:19 PM, Parag N(पराग़) <panemade@gmail.com> wrote:
Hi,
On Tue, Sep 24, 2013 at 2:44 PM, Ł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…
I agree here, log messages should not be translated or rather should not be made available in pot/po files for translation.
Regards, Parag.
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Actually, I'm with you, Łukasz. We have done a wonderful job in Horizon translation in Havana release. I hope to resolve this issue in IceHouse. So that we can cover more components' translations in next release. But I haven't a clear mind about how to handle this issue yet. Remove _() from the log message? Move to another translation domain? Or introduce more configuration parameters to decide which level of log messages will be shown in locale language? I'm going to bring this discussion to the design summit. Before that, we can have a sufficient discussion within I18n mail list at first. Regards Ying Chun Guo (Daisy) Łukasz Jernaś <deejay1@srem.org> wrote on 2013/09/27 19:00:42:
Łukasz Jernaś <deejay1@srem.org> 2013/09/27 19:00
To
openstack-i18n <openstack-i18n@lists.openstack.org>,
cc
Subject
Re: [Openstack-i18n] Log messages translation
Hi,
Maybe we should bring that issue up on OpenStack-dev for IceHouse again? IMHO every non user facing log message shouldn't be marked for translation, but then again the discussion in January
http://lists.openstack.org/pipermail/openstack-dev/2013-January/004259.html
made me wonder what the rationale for that was anyway (since I'm new to the community)...
Regards, -- Łukasz [DeeJay1] Jernaś
On Tue, Sep 24, 2013 at 2:19 PM, Parag N(पराग़) <panemade@gmail.com> wrote:
Hi,
On Tue, Sep 24, 2013 at 2:44 PM, Ł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…
I agree here, log messages should not be translated or rather should not be made available in pot/po files for translation.
Regards, Parag.
_______________________________________________ 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
participants (4)
-
Gabriel Wainer
-
Parag N(पराग़)
-
Ying Chun Guo
-
Łukasz Jernaś