Forum: XTM Cloud support
Topic: List of XTM XLF state-qualifiers and their meanings
Poster: XTM Intl
Post title: Work with TMs to see source differences, populate target with fuzzy matches only for work in XTM
Dear Samuel,
In order to display source differences between the source text existing in the source file and source text of the applied fuzzy match you have to connect the translation memory from which these fuzzy matches come from when you work in Trados.
Working without source text differences displayed for fuzzy matches can lead to substantial quality issues or can greatly impact translation productivity. For this reason, XTM advises to work with the TM and without populating target text with fuzzy matches, especially as the feature to populate target text with fuzzy matches is disabled by default and will only facilitate the translation process in XTM Editor. On the other hand, XLF file which is not populated with fuzzy matches does not lose leverage because these TM matches are applied from the TM.
In such case, provided that you follow XTM advice, you do not need to analyse the structure of XTM XLF files to know which segments contain correct and which contain almost certainly incorrect translation.
However, below please see explanations of XTM state qualifiers:
state="translated" state-qualifier="fuzzy-match"— means that the highest match on the list is a fuzzy match
state="translated" state-qualifier="x-fuzzy-forward"— means that the highest match on the list is a fuzzy repetition
state="translated" state-qualifier="leveraged-inherited"— means that the highest match on the list is a 100% repetition
state="translated" state-qualifier="leveraged-tm"— means that the highest match on the list is a leveraged TM match (a 100% match from a TM)
state="translated" state-qualifier="exact-match"— means that the highest match on the list is an ICE exact match
We hope this will help you. Should you have any other questions, please contact XTM support directly at [email removed] .
Best regards,
XTM Support
Topic: List of XTM XLF state-qualifiers and their meanings
Poster: XTM Intl
Post title: Work with TMs to see source differences, populate target with fuzzy matches only for work in XTM
Dear Samuel,
In order to display source differences between the source text existing in the source file and source text of the applied fuzzy match you have to connect the translation memory from which these fuzzy matches come from when you work in Trados.
Working without source text differences displayed for fuzzy matches can lead to substantial quality issues or can greatly impact translation productivity. For this reason, XTM advises to work with the TM and without populating target text with fuzzy matches, especially as the feature to populate target text with fuzzy matches is disabled by default and will only facilitate the translation process in XTM Editor. On the other hand, XLF file which is not populated with fuzzy matches does not lose leverage because these TM matches are applied from the TM.
In such case, provided that you follow XTM advice, you do not need to analyse the structure of XTM XLF files to know which segments contain correct and which contain almost certainly incorrect translation.
However, below please see explanations of XTM state qualifiers:
state="translated" state-qualifier="fuzzy-match"— means that the highest match on the list is a fuzzy match
state="translated" state-qualifier="x-fuzzy-forward"— means that the highest match on the list is a fuzzy repetition
state="translated" state-qualifier="leveraged-inherited"— means that the highest match on the list is a 100% repetition
state="translated" state-qualifier="leveraged-tm"— means that the highest match on the list is a leveraged TM match (a 100% match from a TM)
state="translated" state-qualifier="exact-match"— means that the highest match on the list is an ICE exact match
We hope this will help you. Should you have any other questions, please contact XTM support directly at [email removed] .
Best regards,
XTM Support