Open Stack

"API facing messages", I will call it user-facing API messages, which
means, these API is provided for users to invoke,
these messages will be used for the interaction with users. For example
Glance and Keystone provide command line for
users to operate, these command line will invoke user-facing APIs. The
output of these user-facing APIs will displayed in the
console.

These command lines can also be called "user interface", i.e. command line
interfaces, while Horizon is web user interfaces.
(see http://en.wikipedia.org/wiki/User_interface). The importance of
command line interface and web user interface are same.
If we want to translate Horizon, we should also translate those user-facing
APIs message.

So I prefer option 2. As it is said that option 3 being not significantly
more work than option 2, so option 3 is also acceptable for me.

Regards
Daisy

Joshua Harlow <harlowja at yahoo-inc.com> wrote on 05/08/2012 01:46:32 AM:

> Joshua Harlow <harlowja at yahoo-inc.com>
> 05/08/2012 01:46 AM
>
> To
>
> Andrew Clay Shafer <acs at parvuscaptus.com>, Ying Chun Guo/China/IBM at IBMCN,
>
> cc
>
> Thierry Carrez <thierry at openstack.org>, openstack
> <openstack at lists.launchpad.net>
>
> Subject
>
> Re: [Openstack] i18n of log message
>
> I think option 1 is needed, for obvious reasons.
>
> API facing messages, not so sure about that, I would say english for
> those, since they are meant for people interacting with an API and
> not front-end users.
>
> I would think this would be pretty easily solvable by basically
> following what other open source projects already do. It would be
> useful possibly to have a survey of other projects and just follow
> the same pattern??
>
> On 5/7/12 7:53 AM, "Andrew Clay Shafer" <acs at parvuscaptus.com> wrote:

>
> I would vote for 0 or 1 on the cost versus benefit. Option 0 is the
> least overhead, but option 1 would be nice for a lot of reasons.
>
> The downside to i18n of the logs and errors in the dilution of
> information available to find solutions can be higher than the
> benefit of providing messages in a native language.
>
> The level of effort is certainly much much higher to provide option 3.
>
> I'd vote for effort to go to improving the OpenStack core technology
> and features over something that adds a lot of overhead and also
> some downside.
>
>
> On Mon, May 7, 2012 at 3:40 AM, Ying Chun Guo <guoyingc at cn.ibm.com>
wrote:
> I will vote option 3, because I think API-user-facing messages is as
> important as
> user interface messages. Since the workload of option 3 is not much
> more than option 2,
> option 3 will be a better choice.
>
> btw, I see documentation, e.g. OpenStack manuals, is excluded in
> these four options.
> Does that mean there is no comments against the globalization of
> documentation?
>
> Regards
> Daisy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120508/a6699265/attachment.html>