[josm-dev] JOSM Translations

[lists at sumpfralle.de]

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
>
>I think the problem with this approach would be that launchpad already
>references all projects that are translated there - both current and
>future - it would seem an overhead to extract it manually. Just think of
>what kind of size we would be talking here...

According to the expected benefit of a terminology database, it does not really sound worthwhile to me, to use a huge amount of translation to fill it.
But you are right: regarding the terminology, launchpad has an advantage over something like pootle.


>>> 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.
>
>Perhaps launchpad would be willing to extend their functionality and
>allow for some kind of automation - just a thought but perhaps worth
>suggesting.

These issues have been raised quite a long time ago (e.g. 2006) by the KDE translation team:
http://wiki.kde.org/tiki-index.php?page=KDERosettaCollaboration
Additionally there is a bug filed for this issue (no replies, yet):
https://bugs.launchpad.net/rosetta/+bug/197891

Vaguely, this goal is on launchpad's roadmap - at least in connection with launchpad's bazaar repositories:
https://launchpad.net/launchpad-bazaar

Due to Rosetta's (the name of launchpad's translation web interface) focus on Ubuntu package translations, the missing synchronization with external upstream is a big issue for many projects. But it was not addressed within the last years, so I doubt, that this will change soon.


>> There seem to be three options from my point of view:
>
>> A) would someone volunteer to maintain the launchpad translations?
>
>Since I have already messed up with the translations in the first place
>I think I can spare some time and look after this aspect. Obviously the
>key to success then would be to make sure that everyone uses launchpad
>and only launchpad. Fortunately it provides for both - translations
>on-line and working with .po files (which many translators prefer). Also
>it keeps track of who changed what.

good.


>> B) Should we just try to see, if the submissions via the automated process 
>of
>>    pootle suit the quality standards of the current translators?
>
>I think my problem with this approach is the inability to work with .po
>files directly. Way too often I work on translations when I am on the
>train or the like and have no Internet access.

Pootle can synchronize its translations with the upstream (subversion) repository in both directions. Thus you can still continue to use your favorite svn client to work on your translations offline.
Additionally you can download and upload .po files via the pootle web interface.


>> C) We just keep the current state of translations being submitted via svn.
>
>Perhaps this is the least favourable but will always exist as a 'fallback'

agreed.

regards,
Lars

PS: I am neither an active translator of josm, nor an active developer. Please understand my remarks on this issue just as helpful clarifications for the people who are really involved in development. The decision is up to you, anyway :)