Add fuzzy match percentage e.g. [fuzzy00] in OmegaT for TXML files

[GoogleCodeExporter]

This is not a bug report but a feature request.

Sometimes a TXML file will contain existing translations from the client's TM, 
but those translations aren't always 100% matches.  The match percentage is 
indicated in the "target" tag in the TXML file.  If the match percentage is 
less than 100%, then the segment often needs to be reviewed by the translator.

Currently, OmegaT with the Okapi filter shows such fuzzy matched segments as 
"100%" matches.  I suggest that if a segment's "target" tag contains a match 
percentage (below 100), that it be included in OmegaT as a "fuzzy" marker with 
the percentage, e.g. [fuzzy74] for a 74% match.

In case not all translators want this, you can make it an option.

Original issue reported on code.google.com by afrika...@gmail.com on 27 Jan 2014 at 9:56

[GoogleCodeExporter]

Are you refering to the "score" attribute in the <target> element for the 
percentage value?
Could you provide an example file?

Original comment by yves.sav...@gmail.com on 2 Feb 2014 at 2:09

• Added labels: Component-TXMLFilter
• Removed labels: Component-

[GoogleCodeExporter]

We have cases similar to this (fuzzy match provided) for other file formats. I 
think we handle it by simply making the entry a fuzzy match (and not copy it by 
default in the target in OmegaT). Would that be an acceptable behavior here too?

Thanks,
-ys

Original comment by yves.sav...@gmail.com on 2 Feb 2014 at 2:15