Rosetta Fuzzy Merge

Registered by Carlos Perelló Marín on 2005-11-03

This spec is about the implementation of the fuzzy feature that gettext has when merges a new potemplate so translations can be reused more.

This is specially handy when the msgid changes only to fix a typo, like a missing comma, with our current system, that string will appear without translation but with this feature, the old translation will be still there but set as fuzzy so the translator can just review it instead of translate it again.

Blueprint information

Status:
Not started
Approver:
Mark Shuttleworth
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Whiteboard

Reviewed by smurf, 9 Nov.

See link for sugested UI
http://ubuntuone.com/p/GlK/

This is a must have, translators waist larg amount of time retranslating thing.

Case sample:
Recently a line in Ubuntu documentation was change becaused it had "the Ubuntu <link>Ubuntu site</link>", most traslators would probably have picked up on this when first translating it, but with the current system the translation is discarted and you will have 50x translators scrabeling to translating it, then have 50x othere translators reviewing that line.

If fuzzy had been suported it would probably have been just 50 mouse clicks, and probably woudn't have needed to be by people that spoak the given languages (they could just look for "Ubuntu Ubntu" in the fuzzy translation).

It is a huge waist of time!

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.