[josm-dev] JOSM Translations

[Dirk Stöcker]

On Tue, 21 Oct 2008, Henrik Niehaus wrote:

Please fix you quoting style. Top-quoting is not the best idea and 
starting your own text with a quoting sign is also not so good. Thanks.

> From my point of view, the idea, to remove the i18n plugins and move the
> i18n to the core is good. It makes things easier, if you just have to
> put a language file into the jar or anywhere in a directory. The

Whereas I agree, that having the translations directly in the JOSM core to 
make usage easier I disagree at some other points.

> translation of the core and the translation of the plugins should be
> decoupled. That's why I put the i18n of the OpenStreetBugs plugin into
> the plugin jar and didn't use the (for java) unusual gettext mechanism.

This has already been discussed. Gettext is an established system for 
translations whereas the Java way has a lot of drawbacks.

Making a different approach for OpenStreetBugs plugin is nothing I 
consider useful. Altogether this also means that the JOSM translators wont 
translate the OpenStreetBugs plugin.

> But there could be a way, how plugins register there i18n, if the core
> needs access to it.

Why should the core require access to translation of plugins?

> Resumee:
> - no i18n plugins
> - core i18n in the core
> - plugin i18n in the plugins (maybe register at the core)

The management overhead to separate the plugin and core translations is 
nothing I would accept.

What I would accept is moving the translations as they are now into the 
core and abandon the language plugins. That means JOSM core would include 
translations of plugins which may not be loaded, but that is a minor issue 
in my eyes.

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)