Re: [josm-dev] JOSM-Tested

[Dirk Stöcker]

On Fri, 11 Jun 2010, Matthias Julius wrote:

 In my eyes the current release is more stable and bug-free than any
 release before, so tested can be set. Except in case translators do major
 texts today I would vote for making todays nightly build tested tomorrow.

 It might be a good idea to declare a feature and string freeze and
 issue a call for translation updates for a few days before each
 testing release.  This would give translators a chance to catch up.
 It might also boost their motivation a little bit when they know that
 their perfect 100% translation actually will make it into a release.

 Are there any translators on this list?  How would you like that to be
 handled?

Yes. I'am. I always tell me before release that everything must be 
translated. Usually I try to do so :-)

No really. Usually in the time after announcing tested stage first time 
only bug-fixes are done and they don't usually add new user visible 
strings, but mainly error messages or the like (or new plugin strings). I 
also take care that the translators have a chance to catch up before, so 
the languages which currently try the 100% (German, Ukrainian, Russian, 
Italian, ...) have the chance to do so.

On the other hand JOSM is in flux always, so texts in updated plugins 
become outdated and many language miss newer strings anyways. Until now it 
seems impossible to get a release handling for JOSM translations. There 
are always only few people who really actively translate texts and most 
languages stay in the incomplete state. And there are really many strings 
in JOSM and always comming a lot of new strings.

I know this situation from other projects and it seems it is unsolvable, 
so I don't really want to stop development because of missing 
translations. Only solution would be a release branching each time we hav 
a tested, but due to various reason explained in length in other mails I 
still don't think the currently working josm process should be changed 
without need.

This does not mean that when there is a chance to better motivate our 
translators we shouldn't try it.

... Giving each of them a free copy of the software?


... (hmm, wrong development model  :-)

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


___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev

Re: [josm-dev] JOSM-Tested

[Frederik Ramm]

Hi,

Ævar Arnfjörð Bjarmason wrote:
 This wouldn't solve the issue of having 100% complete translations at
 time of release. But it seems that for overall translation
 completeness Translatewiki is working great for OSM. We both have
 active OSM contributors, and an active general translation community
 contributing.

To be honest I'm not keen on having anything translated by members of a 
general translation community. There are many things which, I believe, 
need the OSM context to be translated properly.

I recently changed the E-D translation on launchpad for a number of 
OAuth related items. I don't remember what the problem was exactly but 
it was clear that the translator did not know anything about how OAuth 
works, but just chose context-free translations of the terms involved. 
This resulted in a very skewed overall picture. The person did have an 
OSM background but it seems no OAuth knowledge.

I would expect many more problems of that caliber to show up if we let 
people without OSM exposure translate stuff. It may just about work for 
the web site (but even there I'm skeptical) but not for a sophisticated 
editor.

In my eyes, a *bad* (or half-good) translation is worse than no 
translation at all. If members of the JOSM or at least OSM community do 
not have the time to translate JOSM into Ancient Greek then I'd prefer 
not to have an Ancient Greek JOSM at all, rather than having an Ancient 
Greek JOSM which has been translated by Ancient Greek enthusiast who 
knew nothing of OSM.

Unfortunately the statistics capture quantity, not quality.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09 E008°23'33

___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev