| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
Introduction
This article provides you with detailed information about translation memory (TM) matching and its expected behavior in XTM Cloud.
...
Keep in mind that this order can always be changed if required, by means of, for example, TM settings (global/customer-level/project-level), or TM penalty profiles.
| Note |
|---|
IMPORTANT! If there are multiple matches of the exact same score available for a particular segment, for instance 3 Leveraged matches, the TM match that is prioritized in this case is the one with a most recent Date modified. This can be found in the metadata of a particular TM record in your TM base in the XTM Cloud UI.  |
...
Internal repetitions
Segments containing internal repetitions are populated automatically when no match has been inserted and one of the repetitions is translated for the first time. Depending on the settings in XTM Workbench, these segments can be populated with updated versions of the relevant TM matches if the internal repetition translation is changed.
...
If there are inline tags in the original TM record, the TM match has been downgraded from 100% match (or ICE match) to 99% Fuzzy match, due to the difference.
...
Unmatched or MT
...
-matched segments turn up as Leveraged (100%) or ICE matches
The parent of a repetition (the first occurrence of the segment in the file) is not flagged as a repetition. Because of this, it cannot be included in repetition ("R") matching. Keep in mind that the matching for the segment is refreshed every time the segment is activated in XTM Workbench. For instance, when it is activated in the next workflow step, the matching is performed again. Then, the TM will already contain the entries from the previous workflow step in which the file was actually translated. This can cause new TM matches to be found and displayed in XTM Workbench.
...
In the case of some segments, this behavior is not caused by the 100% repetitions but by the setting which caused the Fuzzy repetitions Matches to change to 100% or ICE matches, if the segment contained a number and this was the only difference between the segment and its TM match. The setting in question is If segment has one number, which is different, substitute number & try to promote fuzzy to leveraged match. To access the relevant checkbox, select Configuration → Settings → Translation → TM → Fuzzy matches.
...
| Note |
|---|
IMPORTANT! Keep in mind that the If segment has one number, which is different, substitute number & try to promote fuzzy to leveraged match setting only works when:
The setting does NOT work when:
|
...
TM import with statuses
When nothing is selected from the Import or set approved/not approved status dropdown (TM → TM import → Import TM), XTM Cloud will apply the Set as not approved option by default. To fix this issue, the TM would have to be imported again, with the Import statuses and set as not approved where missing option selected. If you then import the TM again, the statuses will be overwritten.
...