Launchpad itself

gobby's translations got nuked through an upstream upload

Asked by Philipp Kern

As you can see on https://translations.edge.launchpad.net/gobby/0.4/+pots/gobby gobby's translation got nuked. I synced the translations with upstream after doing a release. The pos were not empty, still most of the languages got resetted to being untranslated.

What went wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Philipp Kern
Solved:
Last query:
Last reply:
Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#1

Could it be that the PO files were for very different versions of the template than the latest version uploaded to Launchpad? In that case, the translation may contain mostly strings that aren't present in the current template.

When I download the current translations (see them here: http://launchpadlibrarian.net/17830824/launchpad-export.tar.gz ) it looks as if this is what happened. Most of the messages in at least the Catalan and German translations are marked as "obsolete," meaning they occurred in those translation files but not in the template.

Revision history for this message
Philipp Kern (pkern) said : 		#2

What is considered as "different"? Through the plain strings, or through the filename/line number information? It was from the same branch, and the template was regenerated with update-pot. It's possible though, that the pos were not regenerated with update-po...

Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#3

Only different in the English message strings (plus message context, if that feature is being used here).

It's also possible that the templates just changed a lot, and most of the messages that were translated really are obsolete now. Even a single-letter change to an English string can make its old translation "obsolete."

Revision history for this message
Philipp Kern (pkern) said : 		#4

Yeah, but they did not change a lot. I prepared the upstream release, it's not that we changed a lot of strings so that almost *all* of them got invalidated. But it seems that there is nothing fruitful coming out of this. Sorry for bothering you...

Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#5

Could it be that either (1) the wrong template got uploaded at some point, or (2) the POT creation date and/or PO file update date in the files' headers weren't updated, and so the system thought it could ignore them as old versions?