Should always be possible to view/revert to upstream translation

Bug #60029 reported by Matthew Paul Thomas on 2006-09-12
This bug report is a duplicate of:  Bug #32471: display differences from upstream. Edit Remove
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

Claude Paroz suggests: Rosetta should "...highlight the last upstream translation in the suggestions (using the same green colour as in status bars would be nice). Add a button "Revert to upstream" that put back the original upstream translation in place. It's important to note that manually copying the upstream translation has not the same effect, because if a modification is done upstream later, it won't automatically replace the manually added string.

"Alternatively, you could prevent adding this new button if the system automatically recognizes that when I manually add a string identical to upstream one, the string resynchronizes with upstream, that is the 'Translated by' field shows upstream data (translator and date) and the string is marked unchanged in Rosetta (green colour)."

I strongly support this idea. It would solve a lot of problems with upstream.

Changed in rosetta:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Nafallo Bjälevik (nafallo) wrote :

Noone assigned to this bug. Did it get lost or what's the status? :-)

Very much related to bug 32471.

Claude Paroz (paroz) wrote :

Yes, related but not the same. Bug #32471 is mainly about being able to return corrections/improvements to upstream, whereas this bug aims to resynchronize Rosetta with upstream in Rosetta interface.

Claude Paroz (paroz) wrote :

To ease resolution of this bug (and make it a possibly fix-it-friday bug), I've opened a new bug, with a first step to improve the situation: bug #81681

I've marked this as duplicate of bug #32471: it will provide an easy overview of only those messages which have been changed from packaged translations, and resolving bug #81681 should help with more easily detecting what message is coming from the package.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers