[josm-dev] JOSM Translations
Dirk Stöcker
openstreetmap at dstoecker.de
Wed Oct 22 10:03:56 BST 2008
On Wed, 22 Oct 2008, Marcin Floryan wrote:
>> This has already been discussed. Gettext is an established system for
>> translations whereas the Java way has a lot of drawbacks.
>
> I do agree - gettext approach is better not least because it provides
> better tools for translators.
Not only that. It is also much better for programmer.
>> The management overhead to separate the plugin and core translations is
>> nothing I would accept.
>
> Even if this meant just two translations - one for core and one for all
> plugins? I can see where this gets more complicated but than plugins
> change much more frequently than core does.
That is not true. The text changes for plugins and core aren't so much
different.
And the main problem would be to have one translation file but separate
that afterwards into different plugin files. It is possible, but I would
avoid that.
>> 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.
>
> If this is a general consensus then is there anyone taking up this task?
> I am willing to volunteer for this one.
When you create the infrastructure to have the translation stuff in main
core - Fine. Thought we also need a way to interlink the language plugin
SVN structure as it is now with the new system, as I would not like to
move translation into JOSM core SVN (restricted write access, you know).
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
More information about the josm-dev
mailing list