[josm-dev] JOSM Translations

[Lars Kruse]

Hi,

> A significant benefit of launchpad based translation is that many
> other opensource applications are translated there, giving translators
> a wide range of suggestions about how to translate strings.
> Applications benefit a lot from consistent translations.

if this is important for the josm translators, then I could create a
terminology database extracted from the po files of relevant projects.
See http://translate.sourceforge.net/wiki/pootle/terminology_matching


> Downside of launchpad based translation is the need for an account in
> launchpad, no automated SVN integration and forced BSD license [1] on
> translated strings (lowest common denominator of varoius licenses).
> I'd say these are minor inconveniences, but i might be wrong.

I guess, it just depends on the one, who would be willing to maintain the
translation entered via the web interface.
For launchpad this would involve regular manual synchronization - maybe once a
week.
For pootle it would be mainly poking at the specific language maintainers do
review translations and submit them (via the web interface). The committing
could also be done automatically. Then language maintainers would just need to
review the committed changes and revert them, if necessary.


There seem to be three options from my point of view:

A) would someone volunteer to maintain the launchpad translations?
B) Should we just try to see, if the submissions via the automated process of
   pootle suit the quality standards of the current translators?
C) We just keep the current state of translations being submitted via svn.

regards,
Lars