Open Stack

Hi,

To make it be able to be translated is to give people a choice.

Even if openstack is not a consumer product (That depends on what level 
we are speaking.), some one will build their own products basing on 
openstack.

These products may be kind of consumer products. If we do not even give 
them a choice, it will be painful for them to do that.


Yong Sheng Gong

On 12/14/2012 07:19 AM, Juergen Brendel (jbrendel) wrote:
> Hello!
>
> I noticed that we have the occasional use of _("...") to be able to internationalize/translate various messages in the system.
>
> Is this really necessary? I don't see the need to internationalize the messages produced by a highly technical system such as OpenStack. Firstly, proper internationalization is quite tricky and often requires additional annotations in the code in order to get it right.
>
> Secondly, I don't think it's helpful for the user to receive a localized version of an error, translated into a not-so-common language, which then makes it close to impossible for them to google for it to find a solution.
>
> I'm not a native English speaker, but I believe that most of the OpenStack users will have sufficient command of English to at least get the gist of what's happening. And if they don't, it's much easier for them to ask for help on the mailing list (which is in English!) or in the community if they can simply quote the message as is, rather than trying to translate it back into English.
>
> If OpenStack would be a consumer product, it would be a completely different story. But it's not.
>
> Juergen
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>