Skip to main content

XTM Cloud 25.3

Creating a project: Machine translation

This section provides information about optional Machine translation settings that you can set while creating a project in XTM Cloud.

XTM Cloud is integrated with a wide selection of Machine Translation (MT) engines. The MT engines that are visible and available for selection during project creation depend on what has been set up by your XTM Cloud Administrator for the entire system, or by the Project Manager at customer level.

The supported MT engines are:

  • Acolad.

  • Amazon Translate.

  • CrossLang.

  • Custom MT.

  • DeepL.

  • Google Translate.

  • Intento.

  • KantanAI.

  • Language Weaver.

  • Lingo24.

  • Lionbridge GeoFluent.

  • Microsoft Translator.

  • Omniscien Technologies Language Studio.

  • Oneliner.

  • OpenAI GPT.

  • SAP Translation Hub.

  • SmartMATE.

  • SYSTRAN.

In the Creating project > Machine translation section, you can activate/deactivate all MT engines that have been integrated with your instance by your XTM Cloud Administrator. XTM Cloud will send a request to all MT engines which you have enabled for the relevant project, for all language pairs in the project. Your XTM Cloud Administrator can specify whether the MT request will be send out during the project analysis, or on segment-by-segment basis, in XTM Workbench, or both. XTM Cloud will never send a new request to the MT engine if a machine translation match for the relevant segment has already been returned. This also applies when source files have been updated (continuous projects), for the segments, whose content and context (their previous and the following segment) did not change.

Warning

Project reanalysis means that all source files are analyzed again. Therefore, machine translation requests will be sent again, according to the current project settings.

Language pair support can be limited by your MT engine provider or by the additional MT settings, such as models or profiles. For the following MT engines, it is also possible to map MT engine usage for the relevant language pair(s):

  • CrossLang.

  • DeepL.

  • Google Translate – AutoML, including NMT.

  • Intento.

  • Language Weaver.

  • OpenAI GPT.

  • Omniscien Technologies.

  • SAP Translation Hub.

  • SYSTRAN.

  • Any MT integration which uses Custom MT.

In the case of the AWS Amazon Translate MT engine, you can only map its use for terminology for the relevant language pair(s).

If the same language is sent to more than one MT engine, XTM Cloud will send a translation request to each of them. In XTM Workbench, the MT engine results for the relevant segment(s) are displayed in the Matches docked panel. Each of the results is labeled with the relevant MT engine name. The order in which the results are displayed depends on the order in which the MT engines respond. The Populate target with match setting will be applied to the first MT match on the Matches list.

Important

Ensure that you always use an MT engine which is compliant with your security and data processing requirements.

Table 60. Creating a project: Machine translation settings

Setting

Description

Mandatory/

Optional

Type

Valid values

DeepL MT settings

Use DeepL Translator

Use the DeepL Translator MT engine

Note

The Use DeepL Translator entry in the table serves as an example of MT applied during a project creation.

Optional

Checkbox

Valid values:

  • Selected.

    When you select this option, the Advanced options setting is displayed.

  • Cleared

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.

Glossaries and formality

Note

The Glossaries and formality setting is only available for DeepL Translator

If you select this button, you can make these settings for each target language in the project:

  • Use MT for this language.

  • glossary.

  • formality.

Optional

Button

Advanced options values that are available for every target language:

  • Use MT for this language toggle switch:

    • Disabled.

    • Enabled.

      The Glossary and Formality dropdown lists is activated.

  • Glossary dropdown:

    • Not available — when DeepL Translator does not support glossaries for this target language.

    • Choose... — to select a glossary available for this target language.

  • Formality dropdown:

    • Not supported — when DeepL Translator does not support a formality setting for this target language.

    • Default (default).

    • More.

    • Less.

Google MT settings

Use Google MT

Use this setting to specify whether Google MT is used for this project.

Optional

Checkbox

Valid values:

  • Selected.

    When you select the Use Google MT checkbox, the Use AutoML checkbox is displayed.

  • Cleared.

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.

Use AutoML

You can specify whether to use Google AutoML in the project.

Optional

Checkbox

Valid values:

  • Selected.

    When you select the Use AutoML checkbox, the Models and glossaries setting and the Advanced options button are displayed.

  • Cleared.

Models and glossaries

You can select a model and glossary for the relevant language pair in the project.

Optional

Button and popup

When you select the Advanced options button, the Advanced options popup is displayed.

In the Advanced options popup, for each Target language, select one of the following options:

  • Use MT for this language toggle switch:

    • Disabled.

    • Enabled.

      The Model and Glossary dropdown lists are activated.

  • Model dropdown:

    • Not supported — when Google AutoML does not support a model for this target language.

    • Google NMT (default).

      When you select this option, you are not able to select a glossary for this target language.

    • A list of models available in your Google AutoML account.

  • Glossary dropdown:

    • Not available — when Google AutoML does not support glossaries for this target language.

    • Choose... — to select a glossary that is available for this target language.

OpenAI GPT settings

Use OpenAI GPT

If your XTM Cloud Administrator has connected OpenAI GPT to your XTM Cloud instance, you can decide to enable or disable it for the relevant project.

Optional

Checkbox

Valid values:

  • Cleared – to disable OpenAI GPT for the relevant project.

  • Selected – to enable OpenAI GPT for the relevant project.

    When you select this option, the Matching for language pair setting is displayed.

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.

Matching for language pair

This setting is displayed if you have selected the Use OpenAI GPT checkbox.

In Matching for language pair, you can enable OpenAI GPT for each project language pair.

Optional

Button

Select the Choose button to the right of the Matching for language pair label. As a result, the Matching for language pair popup is displayed.

In the Matching for language pair popup, for each project language pair, you can set the toggle switch to:

  • Disabled (default).

    OpenAI GPT MT is NOT activated for the relevant target language.

  • Enabled.

    OpenAI GPT MT is activated for the relevant target language.

Intelligent Score settings

Note

This is a Beta feature.

Use Intelligent Score

Note

This is a Beta feature.

This feature can only be run using LLM licenses owned by XTM International.

During the Beta tests, the feature is limited to 100,000 AI words per XTM Cloud instance. AI Words are source words sent to the LLMs. Words from the translation memory (TM), terminology, and context segments are NOT counted as AI Words.

This setting is only displayed if the Intelligent Score feature has been activated for your instance by your XTM Cloud Administrator. For details, see Global Intelligent Score settings.

The Intelligent Score feature automatically evaluates the quality and accuracy of translations generated by an LLM (Large Language Model). For every eligible segment, the feature compares translations generated by three different LLMs and evaluates their similarity. In the process, it analyzes the source segment, context (the previous and next segment), the three highest translation memory (TM) matches that were added or updated most recently, terminology, and the project's subject matter. The lower the similarity between these three translations, the lower the quality evaluation score (percentage). The quality ranges (poor, medium, and high) are configurable at global, customer, and project levels. Source text words processed by the Intelligent Score feature are referred to as AI Words. Words from the translation memory (TM), terminology, and context segments are NOT counted as AI Words.

Optional

Checkbox

Valid values:

  • cleared – the Intelligent Score feature is deactivated for the project. If required, you and other Project Managers can then activate the feature in the Project Editor.

  • selected – the Intelligent Score feature is activated for the project. If required, you and other Project Managers can then deactivate the feature in the Project Editor. When you select the checkbox, these settings are displayed:

    • Matching for language pair.

    • Confidence threshold.

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.

Matching for language pair

Note

This is a Beta feature.

This setting is only displayed if you have selected the Use Intelligent Score checkbox.

You can specify the project target languages for which the Intelligent Score feature is enabled.

Optional

Button and popup

When you select the Choose button, the Use Intelligent Score popup is displayed.

In the Use Intelligent Score popup, select the appropriate setting for each target language checkbox. Then, at the bottom of the Use Intelligent Score popup, select Save. The checkbox setting options are:

  • cleared (default) – the Intelligent Score setting is deactivated for the relevant project target language. If required, you and other Project Managers can then activate the feature in Project Editor.

  • selected – the Intelligent Score setting is activated for the project target language. If required, you and other Project Managers can then deactivate the feature in Project Editor.

Intelligent Score settings

You can specify which Intelligent Score thresholds are to be used for the project: the system default or project-specific settings. (made by your XTM Cloud Administrator for the

This setting is only displayed if you have selected the Use Intelligent Score checkbox.

Mandatory if you have selected the Use Intelligent Score checkbox.

Dropdown

Select the appropriate option from the Intelligent Score settings dropdown:

  • System default (default) – the Confidence threshold section displays the system default values in read-only mode. These are the values set for the Intelligent Score feature at customer level. For details, see Customer Editor – Settings.

  • Project specific – the Confidence threshold section displays the system default values, but they can be edited, if required.

Confidence threshold

Note

This is a Beta feature.

This setting is only displayed if you have selected the Use Intelligent Score checkbox.

Specify the ranges within which target segments are considered poor, medium, and high quality.

Optional

Text fields and a slider

Use the Confidence threshold section settings to specify the minimum quality score for acceptable or good translations:

  • Not acceptable – set a threshold below which segments are considered poor quality and need correction or post-editing by a Linguist. To do so, enter a numeric value in the text field. Alternatively, use the slider displayed above the Not acceptable label: the corresponding numeric value is displayed automatically in the text field. The Not acceptable quality range is marked red on the slider. Also, target segments within this range are marked red in XTM Workbench. The default value is 0%.

  • Acceptable – set a threshold to create a range for medium-quality segments. These LLM-translated segments meet basic standards, but a Linguist might need to make minor improvements to them. To set the threshold, enter a numeric value in the text field. Alternatively, use the slider displayed above the Acceptable label: the corresponding numeric value is displayed automatically in the text field. The Acceptable quality range lies between the Not acceptable threshold, or 0% (if the Not acceptable threshold has not been set), and the Acceptable threshold value. It is marked yellow on the slider. Also, target segments within this range are marked yellow in XTM Workbench. The default value is 0%.

  • Good – the setting value is fixed at 100%. Segments in the range between the Acceptable threshold, Not acceptable threshold (if Acceptable has not been set), or 0% (if neither the Acceptable nor Not acceptable threshold has been set), and 100% are considered high quality. They do not need corrections or post-editing by a Linguist. The Good quality range is marked green on the slider. Also, target segments within this range are marked green in XTM Workbench.

General machine translation settings

Do not search for an MT match when one of the selected matches exists

This setting is displayed at the bottom of the Machine translation section and refers to all MT engines enabled for the relevant project.

When any of the options are selected, the segments concerned are not translated using MT.

Optional

Checkbox

Valid values:

  • ICE.

  • Leveraged.

  • Repetition.

  • 95-99% fuzzy.

  • 85-94% fuzzy.

  • 75-84% fuzzy.

  • 95-99% fuzzy repetition.

  • 85-94% fuzzy repetition.

  • 75-84% fuzzy repetition.

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.

Populate target with match

This setting is displayed at the bottom of the Machine translation section and refers to all MT engines enabled for the relevant project.

Specify if matches should automatically be inserted in the target according to inline tag differences and, if so, when.

Optional

Dropdown list

Valid values:

  • Never.

  • Only if inlines are the same.

  • Always, fixing inline differences.

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.

Set MT matches to done

This setting is displayed at the bottom of the Machine translation section and refers to all MT engines enabled for the relevant project.

Specify if MT matches are completed and, if so, in which workflow steps.

Optional

Dropdown list

Valid values:

  • Never (default).

  • All steps.

  • First step only.

  • All except last step.

The default is specified in system settings or customer settings.

Note

The customer settings take priority over system settings.


In this section: