Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

2016-11-03 Thread Doug Hellmann
Excerpts from Ian Y. Choi's message of 2016-11-04 00:58:30 +0900: > Hello, > > I am from I18n team. Please see inline for my comments. > > Doug Hellmann wrote on 11/3/2016 2:19 AM: > > Excerpts from Brian Rosmaita's message of 2016-11-02 16:34:45 +: > >> This issue came up during a code

Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

2016-11-03 Thread Ian Y. Choi
Hello, I am from I18n team. Please see inline for my comments. Doug Hellmann wrote on 11/3/2016 2:19 AM: Excerpts from Brian Rosmaita's message of 2016-11-02 16:34:45 +: This issue came up during a code review; I've asked around a bit but haven't been able to find an answer. Some of the

Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

2016-11-02 Thread Brant Knudson
On Wed, Nov 2, 2016 at 11:34 AM, Brian Rosmaita < brian.rosma...@rackspace.com> wrote: > This issue came up during a code review; I've asked around a bit but > haven't been able to find an answer. > > Some of the help output for utility scripts associated with Glance aren't > being translated, so

Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

2016-11-02 Thread Doug Hellmann
Excerpts from Brian Rosmaita's message of 2016-11-02 16:34:45 +: > This issue came up during a code review; I've asked around a bit but > haven't been able to find an answer. > > Some of the help output for utility scripts associated with Glance aren't > being translated, so Li Wei put up a

[openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

2016-11-02 Thread Brian Rosmaita
This issue came up during a code review; I've asked around a bit but haven't been able to find an answer. Some of the help output for utility scripts associated with Glance aren't being translated, so Li Wei put up a patch to fix this [0], but there are at least two problematic cases. Case 1: