XTM Cloud v 13.0

Matches - general

To access the Matches - general parameters go to Configuration > Settings > Translation > TM > Leveraged matches.

Table 8. Matches - general parameters

Parameter

Description

Reverse memory matching

Selecting this option will enable XTM to use a TM that is stored in the reverse direction to the project. For example, if the project is English to French then XTM will firstly match against this TM and then against the French to English TM. Reverse translation memory matching only occurs where no match was found for the segment in the standard TM.

In XTM the translation memory is stored as a source and target language pair in a database. There is one table in the database for each target language, where all the segments for that target language are stored, whatever the source language.

  1. XTM looks in the regular table for the project target language and seeks a match for the source text.

  2. If any kind of match is found, XTM uses it and does not look for a reverse match

  3. If no match is found, XTM tries to find a reverse match by looking in the TM table of the project source language.

  4. If matches are found in this table, XTM only returns matches for the correct language pair

Reverse matching will give you ICE, leverage and fuzzy matches. However, note that the context of the match which is used for ICE matches is only saved in the TM at the end of the workflow. So, you will only get ICE matches from previous projects if they have finished.

Currently, reverse matching is enabled or disabled for the whole system and so either used or not used on all projects.

Save TM segment history

If selected, XTM will save all versions of the TM segment. The history is visible in the TM manager by clicking on the info icon i-icon.png next to the segment and then the clock icon clock_icon.png in the popup.

Set matches with inline differences as fuzzy

If the only difference in the match is inline elements, then this option allows you to set the match as a 100%/ICE match, or as a 99% fuzzy match.

Use not approved memory

Translation memory is created and stored immediately in XTM when the translator changes the target text and moves to the next segment. Initially it is stored as not approved” but this is changed to approved when the job is completed. This option allows you to choose whether you wish to use approved or not approved” TM.

Match against all language variants

This item gives you the option to match using all language variants. For example, when this option is selected, if you are translating English to Spanish (en-GB to sp-SP), XTM will firstly match against the English en-GB to Spanish sp-SP TM and then check all the other variants of English, such as en-US or en-AU, and Spanish, such as sp-MX or sp-CL TM to find a match. When you select the Permit box, you can specify which languages you want to include. The options are:

  • Arabic

  • English

  • French

  • German

  • Italian

  • Portuguese

  • Spanish

  • Dutch

TM language variant penalty profile

Specifies which penalty profile to use for language variant matches.

Note

Language penalty profile supersedes any other TM penalty profile chosen at project level!

The option will only work when the following conditions are met:

  • The Match against all language variants option is enabled

  • At least one TM penalty profile exists with the Match type is the variant option set in the Field column under Configuration > Data > Tags > Penalty profiles

  • A match is applied from a translation memory that is a different variant of the target language

Highlight segments populated with a language variant match

When matching against all language variants is enabled, the segment number field of language variant matches written to target is displayed in orange.

segment_highlight_lg_variant_match.png

Segment highlight when populated with a language variant match

Mark segments as locked when

To lock specific types of segments, select one of the values from a dropdown list:

  • Match type is approved or not approved ICE and Leveraged - segments populated with either approved or not approved In-Context Exact matches and Leveraged matches will be locked

  • Match type is approved ICE and Leveraged - only segments populated with approved In-Context Exact matches and Leveraged matches will be locked

  • XLIFF:doc status >= Translated - segments with Translated, Proofed and Validated XLIFF:doc statuses will be locked

  • XLIFF:doc status >= Proofed - segments with Proofed and Validated XLIFF:doc statuses will be locked

  • XLIFF:doc status = Validated - only segments with the Validated segment status will be locked

Matching of non-translatables

This parameter enables you to decide whether to leave the non-translatable text unchanged or to match it against the TM.

Non-translatables are segments that are:

  • numeric text

  • alpha numeric text

  • contain only punctuation

Treat hyperlinks as translatable text

This parameter can be configured on the global level only.

Enable this parameter if you want to make sure that all hyperlinks are treated as translatable segments. This means that they will be included in the word count and behave like translatable segments. Moreover, external matching (from Translation Memory) and internal matching (Repetitions) will work for them in a standard way.

This parameter, once enabled, will apply to all of the projects created afterwards. So, for projects with this option enabled, if the user decides to turn it off, such projects must be re-analyzed.

Modify the existing TM record if the project segment has the same

When a segment has a 100% leveraged or ICE match and it has been edited, the new TM entry will be created. You can change this default behavior and decide when an existing TM record is modified. If the source segments in the TM and your project segments are the same, existing TM records can be modified when:

  • inline tags are the same

  • context of segments is the same

  • TM tags of segments are the same

Modify the existing TM record if the project segment with Segment ID has the same

This parameter enables defining segment IDs as an additional parameter in your TM overwriting settings. Valid values for this parameter are:

  • Source: enabled by default

  • Inlines: taken from the Modify the existing TM record if the project segment has the same settings

  • Segment ID: enabled by default

  • Context: disabled by default

  • Tags: taken from the Modify the existing TM record if the project segment has the same settings

Note

This parameter requires enabling Segment ID matching.

Contact support@xtm.cloud to get this configured.

Do not store in TM segments with XLIFF: doc status set to Reject

This parameter is available only when TIPP is enabled at the system level under Configuration > Settings > System (see System settings).

With this function, when segments with Rejected status are uploaded to TM, they will not be saved in TM. If the same segments already exist in TM, but their status is different than Rejected, they will be removed from TM.

The parameter is by default switched on for all existing and new customer accounts, but is configurable on the global and customer level.