comparing original strings

Bug #515536 reported by Martin Lukeš
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

Case:
Project has some string.
Translator translates this string.
Editor for some reason (e.g. correcting a typo) changes the original string.
Rosetta will delete the original string AND its translation and will establish a new original-language string with no translation.
And translator will have to translate that string again.

Motivation:
Now imagine that that poor translator will have to retranslate HUNDREDS of strings like this one and multiply it by a number of languages to which the project is translated!

My point:
It would be marvelous if would Rosetta compare these strings (old and new) and then, based on how much the new string differs from the old one, will add the old original and old translated string to the new string for example as "a suggestion" or "previous translation".

Request:
I know that it probably isn't so useful for ordinary application translating where strings are so short like 'Open', or 'View'. But for projects with longer strings like in 'Ubuntu Manual' it is quite essential and would ease work for a number of translators.

Revision history for this message
Данило Шеган (danilo) wrote :

Agreed. However, implementing a feature like that would take some time. We've long ago registered this as an interesting idea. See https://blueprints.launchpad.net/rosetta/+spec/rosetta-fuzzy-merge

Changed in rosetta:
status: New → Invalid
Revision history for this message
Данило Шеган (danilo) wrote :

(marked as 'invalid' since we have a blueprint to track it)

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

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.