[josm-dev] JOSM Translations
henrik.niehaus at gmx.de
Tue Oct 21 18:06:44 BST 2008
>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
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.
But there could be a way, how plugins register there i18n, if the core
needs access to it.
- no i18n plugins
- core i18n in the core
- plugin i18n in the plugins (maybe register at the core)
Marcin Floryan schrieb:
> Recently someone on the list asked why JOSM is localised using plugins.
> Since I work on JOSM translation a bit myself it made me think about
> this particular approach and it seems like there might be some problems
> with the current approach.
> First and foremost the current approach effectively make it impossible
> to release JOSM with complete and stable translation since there is no
> relation between the JOSM code source code and the language plugins.
> Potentially there could be JOSM bundle with the lang-* plugins included
> but it would still not be accurate. On the other hand, if the lang-*
> plugins get tied with JOSM core then creating translations for plugins
> becomes questionable. And finally I recently noticed that OpenStreetBugs
> plugin decided to take its own localisation approach - by including the
> translation with the plugin itself.
> Perhaps this is a good moment to consider whether some refactoring of
> translations could be carried out to tidy things up.
> I wonder what would people think about:
> * Migrating JOSM core translations to JOSM core and out of the plugin so
> the core can be localised consistently and released with good
> translations. This would also eliminate problem with some messages
> that are currently non-translatable (before plugin is loaded)
> Perhaps launchpad could be use to maintain translations and then
> someone could maintain periodically updating the core.
> * Keeping the lang-* plugins to hold translations for plugins that
> change more often.
> Just a thought.
> Marcin Floryan
> http://marcin.floryan.pl/ [GPG Key ID: 0D5581C5]
> josm-dev mailing list
> josm-dev at openstreetmap.org
More information about the josm-dev