[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[babel-dev] Eclipse i18n guidelines

Hi all,
I submitted a patch over the Babel Editor to migrate it to the Eclipse way of doing things.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=215036

I discussed this patch with Pascal and we had some questions we wanted to address to this list.

I worked using this document [0], "Teach Your Eclipse to Speak the Local Lingo" for reference.

Pascal, however, referred to [1] "How to Internationalize your Eclipse Plug-In".


Apparently the document I used was more recent, and contradicts the other documents on some points.
We would like to clarify those points.

1. Should the properties files be placed in the nl folder, or should they be suffixed with the locale (messages_fr.properties for example ?)
2. Are the properties for the root locale and the plugin required to live in the plugin ? Could they be located in the fragment ? Pascal argues with reason that it would be a good way to economize hard drive space, and users could choose the fragment they are interested in. The document I referred to does not seem to allow this.

I have more questions on the subject that I didn't have the opportunity to discuss with Pascal.

3. Are we required to create one properties file per package, as [1] requires ? What are the advantages of such a method ? It does not seem to work well with the NLS approach.

4. Can you list all the suffixes used for the translation packs ? Apparently they follow the ISO 639-1 codes (http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ), but for some reason brazilian portuguese is added (pt_BR).

I would be very grateful if you could answer those questions; Eventually we could clarify more on this page [2].

Thanks for reading,

Antoine

[0]: http://www.eclipse.org/articles/Article-Speak-The-Local-Language/article.html
[1]: http://www.eclipse.org/articles/Article-Internationalization/how2I18n.html
[2]: http://wiki.eclipse.org/Eclipse_Globalization_Guidelines
--
http://www.lunar-ocean.com/blog