Skip to main content

XTM Cloud 13.4

Matches – general

To access the Matches – general parameters, select Configuration > Settings > Translation > TM > Matches – general.

To make changes to the Matches – general settings, select the relevant option for the required parameters and then select the Save button at the bottom of the screen.

Table 14. Matches - general parameters

Parameter

Description

Reverse memory matching

If you select this parameter, XTM Cloud uses a TM that is stored in the reverse direction to the project. For example, if the project is English => French then XTM Cloud first matches against this TM and then against the French => English TM.

Note

Reverse matching is enabled or disabled for the entire system and so either used or not used for all customers and in all projects.

Save TM segment history

If you select this parameter, XTM Cloud saves up to 10 versions of the TM segment (up to a maximum of 5000 characters). The history is displayed in the TM > Manage tab screen, when a TM Expert selects the info icon i-icon.png next to the segment and then the clock icon clock-eleven-light-blue.svg in the popup. This parameter also enables an additional dropdown list in the TM > Manage tab screen, with which TM Experts can search by TM history.

Set matches with inline differences as fuzzy

If the only differences in the match are inline tags, XTM Cloud can classify the match as an ICE, 100% leveraged match or Fuzzy match 99%.

To set this parameter, use the checkbox in the Permit column:

  • Selected – Result:

    • XTM Cloud downgrades the ICE or 100% leveraged matches score to Fuzzy match 99% if:

      • there ARE inline tags in the segment, but there are NO inline tags in the relevant TM entry,

        Example 1. Inline tags in the source segment, but not in the relevant TM entry.
        • Segment:

          source: text {1} word example

        • TM entry:

          source: text word example


      • or there ARE inline tags in the segment and there ARE inline tags in the relevant TM entry, BUT they are DIFFERENT.

        Example 2. Different inline tags in the segment and in the relevant TM entry.
        Case 1. Fewer inline tags in the segment than in the TM entry.
        • Segment:

          source: text {1} word example

        • TM entry:

          source: text {1} word {2} example

        Case 2. More inline tags in the segment than in the TM entry.
        • Segment:

          source: text {1} word {2} example

        • TM entry:

          source: text {1} word example


    • XTM Cloud keeps the ICE or 100% leveraged match score, if there are NO inline tags in the segment, but there ARE inline tags in the relevant TM entry.

      Example 3. No inline tags in the segment, but there are inline tags in the relevant TM entry.
      • Segment:

        source: text word example

      • TM entry:

        source: text {1} word example

      • Match:

        source: text word example

      Note

      XTM Cloud removes inline tags and only displays plain text.


  • Cleared – Result: XTM Cloud shows the match as an ICE or a 100% leveraged match, and:

    • if there are NO inline tags in the segment, but there ARE inline tags in the relevant TM entry, XTM Cloud removes the inline tags from the match source segment in the Matches docked panel, in XTM Workbench.

      Example 4. No inline tags in the segment, but there are inline tags in the relevant TM entry.
      • Segment:

        source: text word example

      • TM entry:

        source: text {1} word example

      • Match:

        source: text word example

      Note

      XTM Cloud removes inline tags and only displays plain text.


    • OR if there ARE inline tags in the segment, but there are NO inline tags in the relevant TM entry, XTM Cloud:

      • modifies the match source segment to look exactly like the current source segment (inline tags from the current segment are added in the relevant places) AND

      • automatically adds the relevant missing inline tags at the end of the match target segment in the Matches docked panel, in XTM Workbench.

      Example 5. Inline tags in the segment, but no inline tags in the relevant TM entry.
      • Segment:

        source: text {1} word example

      • TM entry:

        source: text word example

        target: translation word example

      • Match:

        source: text {1} word example

        target: translation word example {1}


    • OR if there ARE inline tags in the segment and there ARE inline tags in the relevant TM entry, BUT they are DIFFERENT, XTM Cloud:

      • modifies the match source segment to look exactly like the current source segment (deletes redundant inline tags, or adds required ones in the right places) AND

      • automatically adds the inline tags from the current segment at the end of the match target in the Matches docked panel, in XTM Workbench.

      Example 6. Inline tags in the segment, and inline tags in the relevant TM entry, but different ones.
      Case 1. Fewer inline tags in the segment than in the TM entry.
      • Segment:

        source: text {1} word example

      • TM entry:

        source: text {1} word {2} example

        target: translation {1} word {2} example

      • Match (identical to the TM entry):

        source: text {1} word {2} example

        target: translation {1} word {2} example

      • Once the match is populated with the target text:

        target: translation {1} word example

        Note

        XTM Cloud deletes the redundant {2} inline tag. The existing {1} inline tag stays in its correct place.

      Case 2. More inline tags in the segment than in the TM entry.
      • Segment:

        source: text {1} word {2} example

      • TM entry:

        source: text {1} word example

        target: translation {1} word example

      • Match (identical to the TM entry):

        source: text {1} word example

        target: translation {1} word example

      • Once the match is populated with the target:

        target: translation {1} word example{2}

        Note

        XTM Cloud fixes the missing {2} inline tag by adding it at the end of the target phrase. The existing {1} inline tag stays in its correct place.

      Case 3. Inline tags in the segment differ from the ones in the TM entry.
      • Segment:

        source: text {1} something {2} word great example

      • TM entry:

        source: text something word {1} great {2} example

        target: translation something word {1} great {2} example

      • Match (identical to the TM entry):

        source: text something word {1} great {2} example

        target: translation something word {1} great {2} example

      • Once the match is populated with the target:

        Target segment: translation something word {1} great {2} example

        Note

        XTM Cloud uses the exact target match.


Use not approved memory

Use this parameter to specify if only an approved TM should be used in your XTM Cloud instance, or also a not approved TM.

You can specify whether this parameter is displayed at customer and project level and if it is enabled or disabled by default. To do so, use the checkbox in the Permit column:

  • Selected (default) – This parameter is displayed at customer and project level.

    If you also select the checkbox in the Default setting column, the parameter is enabled at customer and project level by default. Project Managers can disable it, if required.

  • Cleared – This parameter is NOT displayed at customer and project level.

    When you disable this parameter, this does NOT affect:

    • suggesting not approved TM entries from the current project. These entries are returned even after project reanalysis.

    • internal matching.

Match against all language variants

Select this parameter to enable XTM Cloud to search for a TM match using all language variants. For example, when this option is selected, if you are translating English (UK) => Spanish (Spain) (en_GB => es_ES), XTM Cloud first matches against the English en_GB to Spanish es_ES TM and then checks all the other variants of English, such as the en_US or en_AU, and Spanish, such as the es_MX or es_CL TM, to find a match.

When you select the checkbox in the Permit column, you enable matching against all language variants for the entire system. You can further specify which languages you want to include. The options are:

  • Arabic

  • English

  • French

  • German

  • Italian

  • Portuguese

  • Spanish

  • Dutch

Note

Matching against all language variants is enabled or disabled for the entire system and so either used or not used for all customers and in all projects.

When you enable this parameter, the additional TM language variant penalty profile and Highlight segments populated with a language variant match parameters are displayed.

TM language variant penalty profile

This parameter is displayed if you have enabled the Match against all language variants parameter. It enables you to specify which penalty profile to use for language variant matches.

Note

A language penalty profile supersedes any other TM penalty profile chosen at project level.

This option only works when the following conditions are met:

  • the Match against all language variants parameter is enabled,

  • either the source, or target, or both languages in the project job are variant languages,

  • the TM language variant penalty profile parameter has been enabled at project level.

You can decide if this parameter is displayed at project level and specify the default. To do so, use the checkbox in the Permit column:

  • Selected (default) – This parameter is displayed at project level.

    You can select one of the predefined TM penalty profiles or create your own TM penalty profiles as a system default (for details, see TM penalty profiles). To do so, select the relevant option from the dropdown in the Default setting column. Project Managers can change the setting at project level, if required.

  • Cleared – This parameter is NOT displayed at project level.

Highlight segments populated with a language variant match

This parameter is displayed if you have enabled the Match against all language variants parameter. When Project Managers select this parameter at project level, in XTM Workbench, target segments populated with TM entries for a different language variant are marked with the circle-v-orange.png icon.

You can decide if this parameter is displayed at project level and specify the default value. To do so, use the checkbox in the Permit column:

  • Selected (default) – This parameter is displayed at project level.

    If you also select the checkbox in the Default setting column, the parameter is enabled at project level by default. Project Managers can disable it, if required.

  • Cleared – This parameter is NOT displayed at project level.

Mark segments as locked when

Use this parameter to lock specific types of segment and exclude them from editing in XTM Workbench.

You can specify if this parameter is displayed at customer and project level and set the default value. To do so, use the checkbox in the Permit column:

  • Selected (default) – This parameter is displayed at customer and project level.

    You can select one of the values as a system default. Project Managers can change the value at customer and project level, if required. To set the system default, select the relevant option from the dropdown in the Default setting column:

    • Match type is approved or not approved ICE and Leveraged – Segments populated with either approved or not approved In-Context Exact matches and 100% leveraged matches are locked.

    • Match type is approved ICE and Leveraged – Only segments populated with approved In-Context Exact matches and 100% leveraged matches are locked.

    • XLIFF:doc status >= Translated – Segments with Translated, Proofed and Validated XLIFF:doc statuses are locked. This option is available if the TIPP parameter has been enabled (for details, see General system settings).

    • XLIFF:doc status >= Proofed – Segments with Proofed and Validated XLIFF:doc statuses are locked. This option is available if the TIPP parameter has been enabled (for details, see General system settings).

    • XLIFF:doc status = Validated – Only segments with the Validated segment status are locked. This option is available if the TIPP parameter has been enabled (for details, see General system settings).

    Note

    A locked segment can be unlocked by a user who has been granted the relevant rights for segment locking and unlocking. To do so, as an Administrator or a Project Manager: select the relevant user in the Users tab. Then, in the Edit user > Access rights > XTM Workbench, for the Segment locking rights, select one of the two options:

    • Lock and unlock.

    • Unlock only.

    If you have disabled the Allow editing of ICE matched segments parameter and enabled the Mark segments as locked when parameter, even users with relevant segment locking and unlocking rights cannot unlock ICE matched segments in XTM Workbench. This is because, when you disable the Allow editing of ICE matched segments parameter, XTM Cloud locks the relevant segments permanently.

  • Cleared – This parameter is NOT displayed at customer and project level.

Matching of non-translatables

Use this parameter to specify whether non-translatable text is to be left unchanged or is it to be matched against the TM.

Non-translatable segments:

  • are numeric.

  • are alphanumeric.

  • only contain punctuation.

  • are URLs – only if the Treat hyperlinks as translatable text parameter is deselected.

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

When a segment has a 100% leveraged or an ICE match and it has been edited, a new TM entry is created. You can change this default behavior and specify that an existing TM entry is to be modified, when:

  • Source – the source segments in the TM and your project segments are identical. When you select any other option from the list, the Source option is selected and becomes inactive.

  • Inlines – inline tags are identical.

  • Context – segments have the same context.

  • Tags – the TM tags in segments are identical.

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

You can use this parameter to set segment IDs as an additional parameter in your settings that control how the TM is overwritten. Valid values for this parameter are:

  • Source – enabled by default.

  • Inlines – disabled by default.

  • Segment ID – enabled by default.

  • Context – disabled by default.

  • Tags – disabled by default.

Treat hyperlinks as translatable text

This parameter can only be configured at global level.

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

Once you enable this parameter, it applies to all projects created afterwards. So, if the user decides to disable this option for projects for which it was enabled, such projects must be reanalyzed.

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

This parameter is only available at global and customer level when TIPP is enabled (for details, see Enabling TIPP in XTM).

If this parameter is enabled, and segments with XLIFF: doc Rejected status are saved in Workbench, they are not saved in TM. If identical segments already exist in TM, but their status is not Rejected, they are removed from TM.

If you select the checkbox in the Default setting column, the parameter is enabled by default for all existing and new customers. Project Managers can disable it for ta specific customer, if required.