Creating a project: AI Translations
This section provides information about optional AI Translations settings that you can make while creating a project in XTM Cloud.
To display the AI Translations settings for a new project, select the Projects tab. Next, in the top right-hand corner of the screen, select the Add project button. Finally, in the Add project, form, select the required customer and scroll down to the AI Translations section. As a result, the AI Translations settings are displayed. They are grouped into these sub-sections:
General options.
Machine translation.
AI Automation.
Style Guide.
TQI options.
XTM Cloud is integrated with a wide selection of Machine Translation (MT) engines. Only MT engines that have been set up by your XTM Cloud Administrator for the entire system, or by the Project Manager at customer level, are visible and available for selection during project creation.
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 a project > AI Translations 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 that you have enabled for a project, for all language pairs in the project. Your XTM Cloud Administrator can specify whether an MT request will be send out during project analysis, or on a 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 a segment has already been returned. This also applies when source files have been updated (continuous projects), for segments whose content and context (their previous and the following segment) have not changed.
Warning
Project reanalysis means that all source files are analyzed again. For this reason, machine translation requests will be sent again in accordance with 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 particular 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 specific 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 result 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.
Important
If a project is subcontracted, your machine translation (MT) settings are inherited by your subcontractor (LSP) and their Linguists.
Neither LSP Project Managers nor LSP Linguists can change these settings.
Setting | Description | Mandatory/ Optional | Type | Valid values |
|---|---|---|---|---|
General options section | ||||
Do not search for an MT/LLM match when one of the selected matches exists | This setting applies to all MT engines/LLM features that have been enabled in the project. When any of the options are selected, the segments concerned are not translated using MT/LLM. | 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 | This setting applies to all MT engines/LLM features that have been enabled in the project. Specify whether matches should be inserted in the target automatically, 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. ImportantIf the Populate target with match setting is set either to Always, fixing inline differences or Only if inlines are the same, a translation memory match will be populated automatically into the target segment instead of the MT- or LLM-generated translation. |
Set MT/LLM matches to Finished | This setting applies to all MT engines/LLM features that have been enabled in the project. Specify if MT/LLM matches are to be set to 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. |
Machine translation section This section describes examples of MT engine settings | ||||
Custom MT settings | ||||
Use [your custom MT's name] | Use this setting to specify whether this custom MT is to be used for the project. The custom MT name has been specified by your XTM Cloud Administrator. For details, see Connecting a Custom Machine Translation engine. | Optional | Checkbox | Valid values:
The default is specified in system settings or customer settings. NoteThe customer settings take priority over system settings. |
Model for language pair | This setting is displayed if you have selected the Use [your custom MT's name] checkbox. When you select the Choose model button, the Model for language pair popup is displayed. Use it to enable your custom MT for the required project language pairs. | Optional | Button | When you select the Choose model button, the Model for language pair popup is displayed. In the Model for language pair popup, select the appropriate option for each target language. Then, at the bottom of the Model for language pair popup, select OK. The options are:
The default option is Do not match for this language, but it can be changed to Use custom MT by XTM Support. To request supportVisit our Support Portal. |
DeepL MT settings | ||||
Use DeepL Translator | Use this setting to specify whether the DeepL Translator MT engine is to be used for the project. NoteThe Use DeepL Translator entry in the table serves as an example for 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 setting is only available for DeepL Translator If you select this button, you can make these settings for each target language in the project:
| Optional | Button | Advanced options values that are available for every target language:
|
Google MT settings | ||||
Use Google MT | Use this setting to specify whether Google MT is to be used for the 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 | Use this setting to specify whether Google AutoML is to be used in the project. | Optional | Checkbox | Valid values:
|
Models and glossaries | You can select a model and glossary for a particular 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:
|
OpenAI GPT settings | ||||
Use OpenAI GPT | If your XTM Cloud Administrator has connected OpenAI GPT to your XTM Cloud instance, you can decide whether to enable or disable it for the 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 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:
|
AI Automation section | ||||
AI Translate & TQI settings Business use caseThe AI Translate & TQI feature helps you reduce translation costs and improve workflow efficiency by leveraging context-aware LLM-generated translations in line with your terminology, translation memory, context, and Style guides. Additionally, the feature is combined with the TQI feature to provide you with quality scores based on configurable thresholds. With AI Translate & TQI, you can base the optimization of your review process on actual data, in line with industry standards, enabling Linguists to focus exclusively on translations that really require post-editing or human intervention. If required, you can also use the feature without the TQI component to only generate high-quality LLM-generated translations based on your resources. AI Translate & TQI can be combined with Intelligent Workflow for greater impact and significant time savings. For details, see Global Intelligent Workflow settings. | ||||
Use AI Translate & TQI | NoteTo use this feature, you must purchase an AI Words allowance for your entire 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. For details about AI Words calculation and deduction for projects, see AI Words in XTM Cloud. For more information, contact your account manager. Clients running the new Enterprise or Business subscription (for details, see Licensing) receive a free monthly allowance of 100,000 or 50,000 AI Words per XTM Cloud instance, accordingly. These words can be used for one or more of these AI-driven features: AI Translate & TQI (used either with or without the TQI component), AI Post-Edit, and TQI. For details, see AI-driven Features tab. XTM uses ChatGPT and Gemini to run the AI Translate & TQI feature. To check which models are currently used, see the Supported models section in https://xtm.ai.transifex.com/docs#section/LLM-Configuration. NoteIf you are using your own LLM keys, the size of the source text, terminology, TM records, context segments, and the Style guide instructions can influence the LLM usage costs. For details, refer to your LLM subscription rules. This setting is only displayed if the AI Translate & TQI feature has been activated for your instance by your XTM Cloud Administrator. For details, see Global AI Translate & TQI settings. The AI Translate & TQI feature uses an LLM (Large Language Model) to automatically generate a high-quality and context-aware translation that matches your tone and voice. For every eligible segment, the feature 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, the project's subject matter, and Style Guide instructions. You can also combine the LLM-generated translations with the TQI feature to automatically evaluate the quality of the LLM-generated translation. The quality ranges (percentage) can be configured directly in the TQI feature at global, customer, and project levels (in a project template, when creating a project, and in Project Editor). Source text words processed by the AI Translate & TQI feature are referred to as AI Words. Words from the translation memory (TM), terminology, and context segments are NOT counted as AI Words. ImportantIf the AI Translate & TQI feature is set to run in analysis and you use XTM Terminology, ensure that your XTM Cloud Administrator has enabled the Match terms in analysis setting (for details, see Terminology engines). If they haven't, as a user with the Project Manager role, select it yourself at customer level (for details, see Customer Editor – Settings). Otherwise, the AI Translate & TQI feature will not have access to terminology. To improve the accuracy of LLM-generated translations, especially if the necessary terminology and translation memory (TM) records either do not exist or are very limited, we strongly recommend using a Style Guide. For details, see Style Guide in the table below. If there are contradictions between the information taken from terminology, the Style Guide, TM entries or context strings, AI Translate & TQI uses the information from those sources in this order of importance:
So, in the case of contradictions, terminology typically takes precedence over Style Guide rules or TM suggestions and surrounding strings. ImportantThe AI Translate & TQI feature will not process a segment for which a match type, selected in the Do not search for an MT/LLM match when one of the selected matches exists setting, has been found. For details, see the "General settings for machine and LLM-generated translations" section of this table. If the Populate target with match setting for any translation memory match category is set either to Always, fixing inline differences or Only if inlines are the same, this TM match, if available, will automatically be inserted in the target segment, instead of the AI Translate & TQI translation. To ensure that an LLM-generated translation will take priority over TM matches and always be inserted in the appropriate target segment, automatically, ensure that the Populate target with match setting is set to Never. For details, see the "General settings for machine and LLM-generated translations" section of this table. | 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 setting is only displayed if you have selected the Use AI Translate & TQI checkbox. You can specify the project target languages for which the AI Translate & TQI feature is enabled. | Optional | Button and popup | When you select the Choose button, the Use AI Translate & TQI popup is displayed. In the Use AI Translate & TQI popup, select the appropriate setting for each target language checkbox. Then, at the bottom of the Use AI Translate & TQI popup, select Save. The checkbox setting options are:
|
AI Translate & TQI settings | You can specify which AI Translate & TQI thresholds are to be used for the project: the system default thresholds or project-specific settings. This setting is only displayed if you have selected the Use AI Translate & TQI checkbox. | Mandatory if you have selected the Use AI Translate & TQI checkbox. | Dropdown | Select the appropriate option from the AI Translate & TQI settings dropdown:
|
Select AI translation mode | This setting is only displayed if you have selected the Project-specific option for the AI Translate & TQI setting. Specify if the AI-generated translation is also to be evaluated, or not. | Mandatory if you have selected the Project-specific option for the AI Translate & TQI setting. | Radio buttons | Valid values:
|
Intelligent Workflow settings Business use caseThe Intelligent Workflow feature accelerates time to market by reducing the overall workflow turnaround times and automating workflow decisions based on actual quality data. It also helps reduce translation costs and ensures efficiency in the translation workflow. Intelligent Workflow uses the AI Translate & TQI confidence score to route content automatically. High-confidence jobs skip manual checks, while Linguists only review the low-quality segments. | ||||
Enable Intelligent Workflow | NoteCurrently, it is only possible to make the Intelligent Workflow settings during project creation. You cannot change them in the Project Editor. This setting is only displayed if the Intelligent Workflow feature has been activated for your instance by your XTM Cloud Administrator. For details, see Global Intelligent Workflow settings. These conditions must be met so that you can use Intelligent Workflow in the project:
The Intelligent Workflow feature leverages AI Translate & TQI to power your workflow automation. It helps you save time and resources by closing unnecessary workflow steps automatically in jobs whose average TQI exceeds the custom Acceptable threshold. A job's average TQI is calculated by adding the scores from all segments and dividing them by the number of segments that have received a score. ICE matches, leveraged (100%) matches, and manual translations made by a Linguist are not evaluated by the AI Translate & TQI feature. For this reason, they are not taken into account when calculating a job's average TQI. However, these two additional requirements must also be met for a workflow step to be closed automatically:
Example 27. Calculating a job's average TQI A project's TQI Acceptable threshold is set to 70%. This means segments whose TQI is between 70% and 100% are considered to be in the Good quality range. The source file for a job contains six segments. The first three segments are translated by LLM, with TQI results of 90%, 65% and 70%. Segment 4 has been translated manually by a Linguist. Segment 5 has been filled automatically with an ICE match. Segment 6 was initially LLM-translated, but a Linguist then modified it, so it no longer has a TQI. In this case, the job's average TQI is calculated solely on the basis of the first three segments, as follows:
The job's average TQI exceeds the project's Acceptable threshold. However, one of the segments has a TQI result of 65% which is below the Acceptable threshold. This means that workflow steps selected for the Intelligent Workflow feature will not be closed automatically. In situations like this, we would recommend that a Linguist should review the TQI suggestions about this lower-quality segment, in XTM Workbench, and correct the segment accordingly. ImportantFor the best user experience, we recommend using the Intelligent Workflow feature with the new Workflow Editor (Beta). For details, see Project Editor – Beta Workflow Editor. | Optional | Checkbox | Valid values:
|
Automatically close steps | NoteCurrently, it is only possible to make the Intelligent Workflow settings during project creation. You cannot change them in the Project Editor. This setting is only displayed if you have selected the Enable Intelligent Workflow checkbox. Select which workflow steps are to be closed automatically if a job's average TQI exceeds the custom Acceptable threshold. This means that, on average, segments in the job are of Good quality. | Optional | Multiple selection | A predefined list of all steps from the workflow definitions selected in the Workflow section of the project creation form for these settings (if applicable): Main workflow, New source workflow, every Language specific workflow, and Workflow for non-analysable files. For details, see Creating a project: Workflow. Some steps can be selected by default, as specified in system settings, but you can now deselect them and select other workflow steps, if required. |
Style Guide section | ||||
Style Guide | The Style Guide feature can be used with these LLM-based features:
We strongly recommend that you use a Style Guide to improve the accuracy of LLM-generated translations or evaluations, especially if the necessary terminology and translation memory (TM) records either do not exist or are very limited. You can select one Style Guide for your project. General rules of that Style Guide will be applied to all target languages. Language-specific rules will only be applied for the relevant target language. Language-specific Style Guide rules that have been set for target languages that are not used in a project will be ignored. If there is a conflict between a general rule and a language-specific rule, the language-specific rule takes priority. This setting will be displayed and can be changed in Project Editor. For details, see Project Editor – General information: AI Translations. | Optional | Dropdown list | Select one of the active Style Guides created by your XTM Cloud Administrators for your instance. For details, see Style Guide tab. |
TQI options section Business use caseThe TQI feature provides you with quality scores based on configurable thresholds and context-aware translation analysis in line with your terminology, translation memory, and Style guides. This helps you reduce translation costs and improve workflow efficiency by enabling Linguists to focus exclusively on translations that really require post-editing or human intervention. | ||||
Request TQI during analysis | This setting is displayed if it has been enabled by your XTM Cloud Administrator. For details, see Global TQI settings. Specify if you want to use TQI during project analysis to score all types of content (e.g., human translations, TM matches, and MT- or LLM-generated content). For details, see Global TQI settings. This setting will be displayed and can be changed in Project Editor. For details, see Project Editor – General information: AI Translations. | Optional | Checkbox | Select the required setting for the Request TQI during analysis checkbox:
The default is specified in customer settings or in project template settings. |
Request TQI for language pair | This setting is displayed if it has been enabled by your XTM Cloud Administrator. For details, see Global TQI settings. Specify target languages for which TQI should be used during project analysis. This setting will be displayed and can be changed in Project Editor. For details, see Project Editor – General information: AI Translations. | Optional | Button and popup containing checkboxes | Select the Choose button to the right of the Request TQI during analysis label. As a result, the Request TQI for language pair popup is displayed. In the Request TQI for language pair popup, for each project language pair, select the checkbox option and select the Save button. The options for language are:
|
TQI settings | This setting is displayed if it has been enabled by your XTM Cloud Administrator. For details, see Global TQI settings. Specify if the global-level or project-specific settings are to be used. The settings and thresholds that you select will apply to all use cases of the TQI feature in a project:
| Optional | Dropdown list | Valid values:
|