| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
Introduction
The following article aims at answering common questions you might have, or resolving issues you might experience, about the machine translation (MT) module in XTM Cloud.
Before reading the article below, make sure you also read the article that handles common TM-related issues: Machine translation (MT) – most common issues & troubleshooting! |
|---|
...
Questions and answers
How can matches from MT become ICE matches?
...
Removing or changing the Category ID might help with resolving the issue.
Can I select an MT that shall be used for segment population in XTM Workbench when using multiple MT engines in a single project?
In case you have enabled the Populate target with match option for your MT, the order of MT engines that appear in XTM Workbench is hard-coded and cannot be customized. Find below the order in which they appear in the editor:
Microsoft MT,
Omniscien MT,
Kantan MT,
Crosslang MT,
Acolad MT,
Lingo24,
Oneliner MT,
GeoFluent,
Google MT,
Amazon,
DeepL,
Language Weaver,
Smartmate,
SAP MT,
Intento MT,
Custom MT.