translations are not version controlled
Bug #197891 reported by
Lime Wire
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It'd be great if rosetta could offer version control for translation changes to allow admins to revert unwanted changes and also tag releases of the translations.
Uploading a new translation file could be considered as an atomic change.
A diff view that would make it easy to track changes as it is possible with a user as the point of focus would be nice too.
| Changed in rosetta: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| summary: |
- Offer version control for translation changes + translations are not version controlled |
| Changed in launchpad: | |
| importance: | Medium → Low |
Revision history for this message
| Jiri Grönroos (jiri-gronroos) wrote | #1 |
| Changed in launchpad: | |
| status: | Triaged → Confirmed |
| Changed in launchpad: | |
| status: | Confirmed → Triaged |
To post a comment you must log in.
Wiki style diff per import would very useful.
Here we have a live example:
Post-release changes (probably corrections, not likely additions) to ubuntu-docs when you have complete chapters translated. Now, you have 75 % of ubuntu-docs translated and this change happens. Should the translator(s) go through all the 25 % (that's still a lot of strings) just to hunt that one correction in one chapter?
Having a diff would help:
a) to give a fuzzy by the translation memory (when only one word/some percentage of sentence changes or when just two letters change the place, one letter gets dropped etc.)
b) to let translators actually see what happened during the import
c) etc.
Would need a blueprint and coding.