List of XTM XLF state-qualifiers and their meanings

Forum: XTM Cloud support
Topic: List of XTM XLF state-qualifiers and their meanings
Poster: Samuel Murray

Hello

For a while now, I've been translating XTM XLF files via OmegaT, using the Okapi filter and non-sentence segmentation.

I have now discovered a quirk in XTM's XLF format, namely that populated fuzzy matches are marked as [b]state="translated"[/b], even though it is an unconfirmed fuzzy match. Certain fuzzy matches are marked as [b]state="translated" state-qualifier="fuzzy-match"[/b], but none of the programs that I opened the XTM XLF file in (e.g. OmegaT, Trados 2015, Wordfast 4, Virtaal) recognise the "state-qualifier", and so all of those programs assume that all those unedited fuzzy matches are in fact correct translations.

I don't really need/use inserted fuzzy matches, because I generally have the TM from which the fuzzy match came from to begin with. So, for me it would be okay to simply blank out the target field of segments marked as populated fuzzies. I assume this means that I simply have to delete all target texts of segments that use [b]state="translated" state-qualifier="fuzzy-match"[/b] from the XLF file, before loading it into the editor.

However, this discovery of state-qualifiers has led me to unearth more of them, e.g.:

state="translated" state-qualifier="fuzzy-match"
state="translated" state-qualifier="x-fuzzy-forward"
state="translated" state-qualifier="leveraged-inherited"
state="translated" state-qualifier="leveraged-tm"
state="translated" state-qualifier="exact-match"

...and I'm not sure what they mean. I mean, I don't know which of them relate to translations that I can trust, and which of them indicate that the existing translation is almost certainly incorrect.

Does anyone have a list of these state-qualifiers, and/or know what they mean?

Thanks
Samuel

[Edited at 2016-08-19 09:11 GMT]