Internationalization for Oxygen

[SSC]

Hello,

in our projects we pass the information, of which kind the internationalization should be used, as program arguments to our application.
What has to be done when I want to set certain internationalization for the Oxygen plugin?
I only found some general information about the internationalization in Oxygen (http://www.oxygenxml.com/unicode_and_in ... ation.html), but not how to set it.

Can anyone give me a hint?

Regards Simon

[adrian]

Hello,

Are you referring to internationalization for the Oxygen Eclipse plugin or the internationalization of a plugin/customization for Oxygen(either standalone or Eclipse)?

Can you please provide more details about the context of your Oxygen deployment?

Regards,
Adrian

[SSC]

My Question concerns the whole Eclipse plugins of the Oxygen Editor.

For instance the oxygen views are in english and our own views are in german, like they are supposed to.
So my actual question is how to set a certain localization for the Oxygen Eclipse Plugins?

[Radu]

Hi Simon,

Our standalone version of Oxygen has in the Preferences dialog a combo box in which you can choose the user interface language.

Right now our plugin for Eclipse only displays messages/labels using English translations.
We already have a feature request logged in to make our plugin use the same language that the Eclipse workbench is using.
This involves three parts:

1) The plugin.xml instead of hard-coding English labels for actions, views, needs to point using macros to properties files containing the translations.

2) Our core Java code also adds a lot of actions and shows a lot of dialogs, so this code needs to look at the current language used by Eclipse and provide translations for it instead of using English as it does now.

3) The actions provided by a Document Type/framework for a certain type of XML vocabulary right now have names and descriptions only in English (names and descriptions which can be found in the ".framework" configuration files which is in XML format).

So what you would be able to do with an Oxygen 13.2 (or 13.1) would be to manually translate (1) the plugin.xml and (3) the ".framework" configuration file to German. But you cannot control in any way (2).

We plan for Oxygen 14 (which is scheduled for the summer of 2012) to work on these existing limitations.
We have not done this until now because we've had limited requests in this regard from users.

Another problem involves validation errors reported by the various XML validators which come with Oxygen (for example Xerces, the default XML validator).
These problems are also presented in English although Xerces from example has the messages translated using a .properties file (which is available only in English) so translations might also be possible for the messages given by these validators.

Regards,
Radu

[CheryBen]

Hi, this thread is a bit old and now Oxygen 15 has been released.
You did a great work about i18n, especially in custom frameworks.

But, i think that tere is still some missing points (i'm still working on 14.1):
1 - XML Schema errors messages provided by Xerces are still in english only. Is there a way to provide i18n for those messages? i see, in the xercesImpl jar, a Resource Bundle with those message, but there is only english. Could a Oxygen Component integration provide more resources with a property file placed in another jar but with the same package?

2 - When a user paste or drop content at an invalide position, the displayed popup is not totally translated. The popup title and problem description are ok, but the choices are still in english. (for exemple : "inside the closest p element, to the right of the current position"). How could we fix it, or is it planned?

Regards,

Benoit.

[adrian]

Hello Benoit,

1. Yes, Xerces comes only with an English translation but it has some property files for the messages which can be translated and overwritten by you.

These are the Xerces messages for v14.1 (including Oxygen patches):
http://www.oxygenxml.com/userFiles/xercesMsg.zip
The archive contains a folder structure (which needs to be identically preserved) and a set of property files which you can translate.
After translating the messages, repack the folder structure and place the zip (or jar) in the folder:
Oxygen/lib/endorsed (create the 'endorsed' folder there).

The French character set contains Unicode characters which may need to be escaped in Java property files, so I would suggest using a special Java property file editor when editing the files (search the web for an open source editor).

2. This has been fixed in v15.0.

Regards,
Adrian