Skip to main content

XTM Cloud 13.4

Creating a project: Machine translation

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

XTM Cloud has been 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 MT.

  • Amazon Translate.

  • CrossLang.

  • Custom MT.

  • DeepL.

  • Google Translate.

  • Intento.

  • KantanAI.

  • Language Weaver.

  • Lingo24.

  • Lionbridge GeoFluent.

  • Microsoft Translator.

  • Omniscien Technologies Language Studio.

  • Oneliner.

  • SAP Translation Hub.

  • SmartMATE.

  • SYSTRAN.

XTM Cloud can either:

  • send the source text for matching, from within XTM Workbench, segment by segment. The settings made in Configuration tab > Settings > Translation > Machine translation specify which segments are sent for MT matching. Segments that are not matched by the TM will be listed as MT matches in the project metrics. When an MT system is selected for use, the translator will get MT matches in XTM Workbench.

    This applies to the following MT engines:

    • SmartMATE.

    • MS Translator.

  • send the entire XLIFF for matching, so project creation might take longer.

    This applies to the following MT engines:

    • Omniscien Technologies.

    • KantanMT.

    • CrossLang.

    • Lingo24.

    • Oneliner.

    • Lionbridge GeoFluent.

    • SYSTRAN.

If you add more than one MT engine to your project, XTM Cloud will send the text to all MT engines in all project languages, unless you make a mapping between languages and MT enginess in the project. This mapping is however only possible for the following MT engines:

  • Google Translate.

  • Omniscien Technologies.

  • SYSTRAN.

  • AWS Amazon Translate. – But only for the terminology.

  • DeepL.

  • Language Weaver.

  • SAP Translation Hub.

  • Intento.

  • Custom MT.

If the same language is sent to more than one MT engine, then the MT matches will be prioritized in a specific way, in XTM Workbench: in order they have been loaded. If an error occurs during the MT translation (e.g. Kantan MT could not find an engine and did not perform translation) then XTM Workbench changes the order of displaying MT engine matches even if in xliff file matches are in order in which they have been loaded.

Important

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

Table 56. Create a project: Machine translation parameters

Parameter

Description

Mandatory/

Optional

Type

Valid values

Use DeepL Translator

Use the DeepL Translator MT engine

Note

The entry Use DeepL Translator 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 parameter 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 parameter is only available for DeepL Translator

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

  • DeepL Translator.

  • glossary parameter.

  • formality parameter.

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 will be 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 parameter for this target language.

    • Default (default).

    • More.

    • Less.

Use Google MT

Use this parameter 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 on the project.

Optional

Checkbox

Valid values:

  • Selected.

    When you select the Use AutoML checkbox, the Models and glossaries parameter 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 parameter values:

  • Use MT for this language slider:

    • Disabled.

    • Enabled.

      The Model and Glossary dropdown lists is 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.

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

When any of the options are selected, the segments concerned are not going be 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

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 determined by system settings or customer settings.

Note

The customer settings take priority over system settings.

Set MT matches to done

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 determined by system settings or customer settings.

Note

The customer settings take priority over system settings.