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 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.
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.
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 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.
Parameter | Description | Mandatory/ Optional | Type | Valid values |
|---|---|---|---|---|
Use DeepL Translator | Use the DeepL Translator MT engine NoteThe Use DeepL Translator entry in the table serves as an example of MT applied during a project creation. | Optional | Checkbox | Valid values:
The default is specified in system settings or customer settings. NoteThe customer settings take priority over system settings. |
Glossaries and formality | NoteThe Glossaries and formality settinng 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:
| Optional | Button | Advanced options values that are available for every target language:
|
Use Google MT | Use this setting to specify whether Google MT is used for this project. | Optional | Checkbox | Valid values:
The default is specified in system settings or customer settings. NoteThe customer settings take priority over system settings. |
Use AutoML | You can specify whether to use Google AutoML in the project. | Optional | Checkbox | Valid values:
|
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 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:
The default is specified in system settings or customer settings. NoteThe customer settings take priority over system settings. |
Matching for language pair | This parameter 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:
|
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 translated using MT. | Optional | Checkbox | Valid values:
The default is specified in system settings or customer settings. NoteThe 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:
The default is specified in system settings or customer settings. NoteThe 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:
The default is specified in system settings or customer settings. NoteThe customer settings take priority over system settings. |