[josm-dev] i18n -- why not Locales & Bundles?

[Ulf Lamping]

Hi!

As a slightly related side note:

The current i18n uses the GNU tools which just fails miserably under MS 
Windows and SUN JAVA to compile the translation plugins.

I spend some effort months ago to get the build of the language plugins 
running under Windows and SUN JAVA, but the GNU tools simply doesn't 
support this combination (at least at the time I tried it). IIRC, there 
was a strange problem with temporary files.

This effectively hindered me to update the german translation plugin for 
JOSM and still hinders me to build the i18n plugins under MS Windows at 
all ...

So while the current toolchain is "well established" it also has it's 
problems.

Regards, ULFL

P.S: I never did any i18n on JAVA, so this might also be tricky ;-)


Frederik Ramm schrieb:
> Hi,
> 
> I don't know why we're using what we're using; maybe a design decision 
> by Imi. Anyway whatever reasons were valid then must not necessarily be 
> valid now.
> 
>> My primary reason for asking is that I can't get JOSM to build under 
>> NetBeans -- the latest version of the xnap-commons library lacks the 
>> translation functions used.
> 
> I believe Petr Nejedly has successfully run JOSM with NetBeans.
> 
>> I'm willing to start hacking at the code to eliminate this dependency, 
>> but I want to check it won't be wasted effort first...
> 
> I'm not into i18n that much but if the change you are proposing would 
> mean that every single class that contains a "tr(...)" or "marktr(...)" 
> will have to be changed, then I'd like to have a code example beforehand 
> which also explains how language plugins will work under the new scheme, 
> and how the work of translators will change.
> 
> We have a working system which programmers, translators and users have 
> grown used to. Replacing that with something else will almost certainly 
> mean inconvenience for them; so that "something else" must bring solid 
> benefits to be worth it.
>