Project Editor - General info: Machine translation
Select or change the settings for the created project by changing Machine translations parameters.
Populating target segments with machine translation matches
Parameter | Description | Mandatory/ Optional | Type | Valid values |
|---|---|---|---|---|
Use DeepL Translator NoteThe Use DeepL Translator in the table serves as an example of MT applied during a project creation. | Use the DeepL Translator MT engine | Optional | Checkbox | Valid values:
NoteYou need to reanalyze the project when you enable Machine translation after the project has been created, if your Administrator selected the After analysis option for the Send text for matching parameter under Configuration > Settings > Translation > Machine Translation. |
Glossaries and formality NoteThe Glossaries and formality parameter is available only for the DeepL Translator | Determines use of the following options for each target language in the project:
| Optional | Button | Advanced options values available for every target language:
|
Do not search for an MT match when one of the selected matches exists | When any of the options is selected, the respective segment will not be translated through MT. | Optional | Checkbox | Valid values:
The default is determined by system settings or customer settings. NoteThe customer settings take priority over system settings. |
Populate target with match | Determines if and when matches should be automatically entered into the target based on inline tag differences. | Optional | Dropdown list | Valid values:
|
Set MT matches to done | Determines if and in which workflow steps MT matches are completed | Optional | Dropdown list | Valid values:
|