openstack team mailing list archive

["Ahn, Jaesuk" <bluejay.ahn@xxxxxxxxx>]

We have a small discussion at OpenStack Korea Community about logging in local language. 
Most of participants said that they prefers having logging message in English only. 

Reasons are: 
1. Logging messages are searchable keywords. Having a single entry point for searching is important. 
2. Keeping the exact translation for logging message is very important for the localization. It is not an easy task to do. 

Suggestions are:    
    - It would be helpful if we can have a place (website) to look-up for the translation. 
    - It would be good if each error message has corresponding error code, and a look-up website to search for localized translation with the error-code. 
    - It is also possible that we can have an option to generate localized error message along with original English message. 
    - Having an official website to put feedback, related information, possible cause of error message in various languages is more important than having translated logging message.  

This is just an opinion from small set of developers in Korea Community. 
We are happy to join a discussion on this subject at Folsom design summit, or we can try to gather much broader consensus on this subject within Korea Community. 

Cheers,   


-- 
Jaesuk Ahn, Ph.D.
Team Leader | Cloud OS Dev. Team
Cloud Infrastructure Department
KT (Korea Telecom)
T. +82-10-9888-0328 | F. +82-303-0993-5340
Active member on OpenStack Korea Community


Feb 20, 2012, 7:39 PM, Thierry Carrez 작성:

> Diego Parrilla Santamaría wrote:
>> Joshua, most of non-english speaking developers I know try to use
>> english for class names, methods, fields, constants... English is the
>> 'lingua franca' for code, so even developers with bad english level like
>> me try to use english all the time... so internationalized logging
>> messages do not make sense from my perspective. And sometimes
>> translations are awful, or even hilarious.
>> 
>> So +1 for english only logging messages in the code.
> 
> Currently only Nova is set up for message translations (through
> Launchpad Rosetta [1]). We used to have 100% coverage in Japanese and
> French, and good Spanish coverage. Today the coverage dropped to 20%. I
> agree that it has value only if done properly and across the board.
> 
> The original translations effort was pushed by the Japanese community to
> get Japanese errors in logs. We should definitely have a discussion at
> the Folsom design summit to get some consistency in core projects in
> that area.
> 
> [1] https://translations.launchpad.net/nova
> 
> -- 
> Thierry Carrez (ttx)
> Release Manager, OpenStack
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp