Localisation Issues about oxbow

[eugener]

Martin,

The library fully supports java i18n using resource bundles with property
files. This means that you can always create custom resource bundles with
or without country specification.

Eugene

On Wed, Mar 6, 2013 at 2:54 PM, Martin Miller [email protected]:

Hi, I completely forgot the issue I opened a while back, ie:
http://code.google.com/p/oxbow/issues/detail?id=51&can=1.

As my users want french but we are not in France (and don't want their
weird Localization stuff about calendar and other stuff) I think you should
create (copy) the properties files and leave the country out of the file
name.

In my case, I copied in your library task-dialog_fr_FR.properties to
task-dialog_fr.properties so I can still use my
Locale.setDefault(Locale.FRENCH) as usual. This way you can support
language locales when the country is not specified.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17
.

[martinm1000]

Hi,

Then why Locale.setDefault(Locale.FRENCH) doesn't work without a specific task-dialog_fr.properties in your library but as you indicated in the old issue 51 Locale.FRANCE would pickup your task-dialog_fr_FR.properties ?

Or are you telling me I could add my own task-dialog_fr.properties in my project, and not have to remember to update your jar on the next releases ?

[eugener]

That is exactly what I mean - you can add your own property file.

[martinm1000]

Thanks, it worked !