Closed Bug 627908 Opened 14 years ago Closed 1 year ago

History of changes in Verbatim translations

Categories

(Webtools Graveyard :: Verbatim, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: thomas.lendo, Unassigned)

References

Details

For communities with several translators in Verbatim it would be informative to have such a thing like history of changes of the translations of a project in a language or of the translations of a whole language. This would make transparent the changes people made.
What is the main activity that you want this change to support? Is it to see the quality/volume of contributions by a user, or is it to inspect change to a string over time? What is the question/questions that you want to be able to answer with such a new feature?
I'm gathering use cases for this bug as I'm working on it now. It would be great if you can help with some ideas on what the important parts of the right solution would be. Thanks!
The main intention of this feature for me was to be able to check the changes of strings in a whole project (like SUMO, AMO or Firefox Input) over time. I (as reviewer and uploader) want to see who has made which changes. So I can go through these changes quickly and do corrections without using other tools outside of Verbatim. History should help for quality and efficiency.
We've put in the infrastructure in Pootle that allows us to track history of translation, states and comments. The focus has been on the unit level, not the project level. If you are in the translation interface you can now see all history for the unit and see its progression and who is responsible for each change. While this doesn't address comment 3 directly the core part of tracking history lays the groundwork for the next step which would be a project or language view of changes that have been made.
Product: Webtools → Webtools Graveyard
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.