Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [incubation] I18n for feature.xml/plugin.xml


You are being very diligent in following all the old strong guidance.

Sadly much of it is now stale and/or widely ignored.

I'm not sure that any project is really internationalized these days; certainly it is a long time since I got an email from the IBM message translators asking what a message meant.

In the particular case of i18n, there appear to be some directory naming practices that went obsolete with PDE-build. Every so often some new attempt at compatibility by Tycho manages to resurrect old functionality and go confusingly wrong as a consequence of a stale refactoring. IMHO the less you have to do with i18n the better.


        Ed Willink

On 25/11/2020 08:06, Alexander Fedorov wrote:
Hi Christian,

You have a lot of questions in this message :)

I would say that internationalization (aka i18n) is important quality mark for a source code. However, localization (that brings the real value for a user) is a separate effort, whatever with the help of Babel or without it.

As for i18n for specific attributes like vendor, license, copyrights and so on. I think the i18n should be done to provide a hook for local legal names and formulations. For EPL-2.0 license in particular things are a bit easier since we can specify "license-feature" attribute to reuse standard content with two steps:

1) add to target 2) declare attribute


25.11.2020 10:29, Christian Pontesegger пишет:
I have in mind that one requirement of project graduation is I18N
support. Tried to find that in the handbook, but failed. So first
question: is there a list of requirements on the code and its
functionalities regarding graduation?

2nd: I see that I18N is used for feature.xml and plugin.xml for fields
* vendor
* license
* copyright

Do we really need this? Does Babel really translate the license terms
or copyright messages? The vendor will quite likely also stay the same.

thanks for clarification

incubation mailing list
To unsubscribe from this list, visit

incubation mailing list
To unsubscribe from this list, visit

This email has been checked for viruses by Avast antivirus software.

Back to the top