[josm-dev] Translators and Context driven translation

[Ævar Arnfjörð Bjarmason]

On Mon, Sep 21, 2009 at 10:21 AM, Dirk Stöcker
<openstreetmap at dstoecker.de> wrote:
> On Sun, 20 Sep 2009, Ævar Arnfjörð Bjarmason wrote:
>> I don't know what native support of context actually means in
>> Launchpad. Hopefully it means that if you have "_:Ctxt1\nBar" and
>> "_:Ctxt1\nBar" and only translate the first string the second string
>> will still show up translated. I.e. context will have been something
>> optional the translator can add if he or she wants.
>
> Launchpad has context support and detects this automatically.

When you translate a string which is duplicated in the .po file (but
with different msgctxt) the string you entered will show up as a
suggestion for the rest. If we were post-process the files downloaded
from Launchpad so that we would automatically use these suggestions
context /could/ be added to every occurrence of a duplicate string
without additional burden on translators who aren't interested in
context. Other than an inflation in the number of translatable strings
that is.

Here's an example of Launchpad suggesting a translation with msgctxt:

    https://translations.launchpad.net/esmska/trunk/+pots/esmska/is/+translate?batch=10&show=all&search=%26Gateway

I'm not advocating context for every duplicate string in the program
unless it doesn't bother anyone. But if that's the case then it would
be nicer for translators to translate JOSM. Most of whom are probably
non-technical and won't even think to ask if the string that's used in
30 places they're struggling to translate can be modified to fix that
issue.

> For SVN access currently my rules are that some high quality patches must
> have been provided for some time. You do not yet qualify for this.

Oh well. It's your cathedral to manage.