imagery layer names suddenly untranslated on Launchpad

[aceman]

Why are all imagery layer names suddenly untranslated? It is no fun translating those crazy names again. Which commit touched them and why?

[skyper]

Another problem of recently server upgrade ?

[aceman]

Must have happened in recent days as I check for new strings regularly. In r7529 (which had localization merge at r7479) the strings are fine (translated). I noticed this in the SK language, maybe you can check others.

[Don-vip]

can you please add more details:

• example of impacted string
• last working version
• first failing version
• by "untranslated" you mean inside GUI only or disappeared translations on Launchpad?

[aceman]

Example string: "NRW-Atlas: Automatisierte Liegenschaftskarte (Vektor)"
The messages are untranslated on Launchpad. In JOSM GUI they are still fine, imported at r7479.

[Don-vip]

Ok. Dirk, do you have any idea?

[stoecker]

Not really. Usually that happened, when broken ".pot" file has been uploaded. Then an reupload of all the translations before that issue helped (extract from bzr). Launchpad automatically detects newer changes and rejects these strings, so an upload of an old file (previously downloaded from launchpad) does not destroy anything.

[aceman]

Can you check if the problem is also seen in other languages?

[anonymous]

Is it possible for you to just restore the file of my language from an older version? I can find out what date is a good candidate.

[skyper]

Replying to aceman:

Can you check if the problem is also seen in other languages?

No problem in German, French is only partly translated but I am not sure if it ever was complete.

[stoecker]

Replying to anonymous:

Is it possible for you to just restore the file of my language from an older version? I can find out what date is a good candidate.

If you take the file as is, then launchpad will reject any modification of strings changed after the file was created, so you don't overwrite newer stuff. So it should do no harm upload any older file which contains missing strings (that's the reason, why I added the bzr repo at all).

​https://code.launchpad.net/~openstreetmap/josm/josm_trans

For security I'd nevertheless download the current state before :-)

[aceman]

The catch is I probably do not have a good file stored.

[stoecker]

Replying to aceman:

The catch is I probably do not have a good file stored.

Quoting myself: that's the reason, why I added the bzr repo at all: ​​https://code.launchpad.net/~openstreetmap/josm/josm_trans

[aceman]

This happened again with the Smoothness preset and its values. Did the Launchpad screw it or have you remove the strings and readded them again? It is really no fun translating things again.

[stoecker]

Replying to aceman:

This happened again with the Smoothness preset and its values. Did the Launchpad screw it or have you remove the strings and readded them again? It is really no fun translating things again.

Are you sure there wasn't a change? Maybe adding the translation context to smoothness? Launchpad is not clever enough to at least suggest the strings without context in such a case.

[aceman]

I asked for adding context in the "Smoothness-adding ticket", but it was specifically rejected. I do not see context or any other change happening to the strings. But it also happened to other strings, like the "updated GPS" or "style of inner way of multipolygon the same as multipolygon". It is as if the whole state of translation was reverted several days back.