Versions Compared

Old Version 6

changes.mady.by.user Damian Rozmiarkowski

Saved on

compared with

New Version Current

changes.mady.by.user Damian Rozmiarkowski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
Page Properties
hiddentrue

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.

2024-10-24 12_04_27-Window.pngImage Added

...

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.

...

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:

  • there is only one number in a segment and this number differs the current source segment from the one from the translation memory.

  • the decimals in the current source segment are separated with full stop or comma, e.g. 10,5 or 10.5.

  • the currency or measurement units come after or before a number in the current source segment and are written without space, e.g. 10cm, $15, $10,50.

The setting does NOT work when:

  • there are two or more numbers in a segment.

  • a number in the current source segment is a combination of digits and letters, e.g. 43AB32.

  • a different character is used to separate digits within a number, e.g. 1'000'000, 1'000'000,50, 10 000.

...

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.

...