On 01/25/2017 01:55 PM, Christian
Pontesegger wrote:
Hi,
I would like to know about project requirements for i18n. I see
that the whole platform seems to externalize string constants even
up to plugin names and the license text. On the other hand I have
never seen any plugin providing more than a language file for
English.
The translations are not provided directly by projects, but by
Babel, which wraps translation in fragments.
https://www.eclipse.org/babel/
So my question is if it is a requirement for eclipse projects to
externalize their string constants.
IIRC, it used to be a requirement for joining SimRel or EPP, but I
can't find a reference to it. The requirement may have been dropped
To me the current state seems to add some effort to
the devs without bringing any benefit for the users out there.
Having translation can be important for some use-cases. For example,
in France, I believe there is almost a requirement for software to
be translated in order to be made structural in some public
projects. It may not apply to the Eclipse IDE itself which is more a
developer tool, but some RCP apps really need to be translated, and
that requires downstream Eclipse bundles to be translation-friendly
ie to externalize their strings.
HTH
|