Prevent accidental overwrite of translations
This bug report was converted into a question: question #165699: Prevent accidental overwrite of translations.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Miro Launchpad French translations recently got replaced by Galician translations for Limewire, and people started translating the new string resources into French soon after, leading to a wrong PO file with some French translations on top.
http://
Is there a way from preventing this from happening, or at least require confirmation for such major changes?
I suppose for instance each translation resource is individually tagged with a language ID, since the translations are shared across products, so it should be easy for instance to check that the individual language ID matches the global language ID of the file or table you are about to overwrite.
The product ID could be checked too (in this case Limewire vs. Miro).
This looks like a bulk replace of a whole PO file or translation database table. In that case also it is easy to block the overwrite operation if the number of changes is too important, or at least require a manual confirmation.
In any case, it would be great to display or log the changes in the translations so the incident can be easily traced and rolled back.
There are of course other checks to validate the language as well, but they would require linguistic experts for each language, so these are out of scope.
If you have any suggestion about what happened to Miro and how to restore the French translation, feel free to edit the Miro bug 17887.
There may be a bug or two in here, but this seems more of a series of questions. Someone with more translations knowledge can link to the appropriate bugs that we know about or spin off this question into one or more bugs as we understand better.