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" <a...@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 <guoyi...@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
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
