Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [Galileo bug 252795] NLS vs EMF ResourceLocator

Hello Kit,

 JWT included translation for French and German  as .properties files using ResourceLocator, and it works. We did not test it yet with Babel language fragments, but I imagine it should work fine too.

I don't know exactly how a ResourceLocator works, but it does not seem to be a problem for localization.

Any other idea "against" ResourceLocator?


On Mon, 19 Jan 2009 12:38:33 -0500, Kit Lo wrote:

Hi Mickael,

The Eclipse Babel Project extracts all Java Resource Bundle (.properties) files from all Eclipse projects who participate in Babel and define their map files in Babel. Contributors in the community around the world will translate the .properties files and contribute the translations back to Babel. We will then build language fragments for the Eclipse projects and make them available back to the community.

If you continue to use ResourceLocator, will you be able to find the translations of the .properties files from the language fragments?

Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead

Mickael Istria
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

01/19/2009 05:02 AM

Please respond to
Cross project issues

[cross-project-issues-dev] [Galileo bug 252795] NLS vs EMF        ResourceLocator



In JWT, we are using org.eclipse.emf.common.util.ResourceLocator to get
values from our file.

Is using ResourceLocator is OK for Galileo, so that we can keep using it
instead of NLS Message Bundles ?

Thanks in advance for your answers.

cross-project-issues-dev mailing list


Back to the top