Modify

Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#10509 closed defect (irreproducible)

imagery layer names suddenly untranslated on Launchpad

Reported by: aceman Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: i18n launchpad Cc: stoecker

Description

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

Attachments (0)

Change History (16)

comment:1 by skyper, 10 years ago

Another problem of recently server upgrade ?

comment:2 by aceman, 10 years ago

Summary: imagery layer names suddently unstranslatedimagery layer names suddently untranslated

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.

comment:3 by Don-vip, 10 years ago

Owner: changed from team to aceman
Status: newneedinfo

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?

comment:4 by aceman, 10 years ago

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

comment:5 by Don-vip, 10 years ago

Cc: stoecker added
Component: Core imageryCore
Keywords: i18n launchpad added; i10n removed
Owner: changed from aceman to team
Status: needinfonew
Summary: imagery layer names suddently untranslatedimagery layer names suddenly untranslated on Launchpad

Ok. Dirk, do you have any idea?

comment:6 by stoecker, 10 years ago

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.

Last edited 10 years ago by stoecker (previous) (diff)

comment:7 by aceman, 10 years ago

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

comment:8 by anonymous, 10 years ago

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.

in reply to:  7 comment:9 by skyper, 10 years ago

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.

in reply to:  8 comment:10 by stoecker, 10 years ago

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 :-)

comment:11 by aceman, 10 years ago

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

in reply to:  11 comment:12 by stoecker, 10 years ago

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

comment:13 by Don-vip, 10 years ago

Resolution: irreproducible
Status: newclosed

comment:14 by aceman, 9 years ago

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.

in reply to:  14 comment:15 by stoecker, 9 years ago

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.

comment:16 by aceman, 9 years ago

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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.