While Machine Translation (MT) is generally not a recommended standalone translation method, it's useful in many cases, for example, if you have a lot of non-customer-facing content or want to translate something in conjunction with human post-edit.

Transifex supports:

Google Translate
Microsoft Translator
DeepL Translate (We support both DeepL API Free and DeepL API Pro, and our integration is based on version 2 (v2) of the DeepL API.)
Amazon Translate
KantanMT
Alexa Translations A.I.
Intento
Custom.MT

You'll need to have an account with your chosen service(s) before you can use it for machine translation in Transifex. You might need a subscription, depending on which service(s) you choose and how many words you're translating.

📝Note: When setting up an IAM user to use Amazon Translate with Transifex, the minimum permissions required are TranslateReadOnly.

Machine Translation on an Organization Level

To set up machine translation for your whole organization:

Head to your Settings by clicking on your profile icon.
On the left menu, click on Machine Translation.
Click on the drop down list to choose the MT vendor, or if you already have a machine translation service added, click on Add another Machine Translation service.
In the form that is displayed, select one of the available services:
1. Microsoft Translator Text API
2. Google Translate
3. KantanMT
4. DeepL
5. Amazon Translate
6. Alexa Translations A.I.
7. Intento
8. Custom.MT
Configuration may vary depending on the service you select:
1. If you want to use Microsoft Translator, choose Microsoft Translator Text API and add your subscription key. Also, while setting this up in Azure, set your 'Location/Region' to "Global".
2. If you chose Google Translate, add your API key.
3. If you chose KantanMT, add your API key and engine alias (check here for more details).
4. If you chose DeepL, you must add your API key and set whether the translated text should lean towards formal or informal language. Optionally, you can enable the "Apply the default formality on translations for non-supported languages" option. By enabling this option, languages not supported in the selected DeepL Formality will be translated using the default formality; if this option is disabled, these languages will remain untranslated.
  
  This functionality is described in DeepL Documentation here.
  
  For DeepL and when the mode is set to ‘Plain Text’, strings that include placeholders display the following behavior: To ensure that placeholders are preserved in the translation, spaces are intentionally introduced before and after them. To avoid this from happening, we suggest setting DeepL mode to ‘HTML’.
5. If you chose Amazon Translate, provide your Amazon Translate Access Key ID, and Amazon Translate Secret Access Key as well as define the Amazon Translate Region.
6. If you chose Alexa Translations A.I., provide your Alexa API Key.
7. If you chose Intento, provide your Intento API Key. Optionally, you can set the routing parameter, if you prefer to use the routing you have configured in Intento.
8. If you chose Custom.MT, provide your Custom.MT API Key.
Choose Machine Translation Mode: HTML or plain text (no need to, if you chose Custom.MT for your Machine Translation provider):
1. HTML mode
  Transifex leverages most of the different MT services' capability to detect and keep HTML tags; Transifex protects only the variables and custom placeholders. Current known MT service hiccups include conversions of special characters to their HTML entity counterparts. (ex., a single quote character could become a ' in the translation).
2. Plain text mode
  Transifex is trying to protect all HTML tags, variables, and custom placeholders feeding strings as simple text to Machine Translation services. Current known MT service hiccups include:
  1. Extra symbols (ex. 0x5a4d6e521).
  2. Translations missing part of a sentence found in the source, thus altering its meaning.
  3. Missing HTML tags, variables, and custom placeholders as the MT service mishandles them.
You can use the selected Machine Translation service only for specific target languages by clicking on “Use this Machine Translation service only for specific languages” and selecting the set of languages you want to use the chosen service. If you don’t select specific languages, this service will be used as the Default for all target languages.
Optional: If you need to use a different Machine Translation setup for certain target languages, you can add an additional Machine Translation service configuration for those languages. To do this, simply click on the "Add another Machine Translation service" option below your existing configuration, add the credentials for this new service, and select a different set of languages than the ones selected in your default machine translation setup.

You can remove a Machine Translation configuration by clicking “Remove MT Service” displayed after hovering over the desired service.
When you are done setting the desired Machine Translation service(s), click on “Save changes”

📝Note:

Suppose you have set up an MT service with no specific languages selected (Default). In that case, this service will be applied to all the languages not explicitly configured in a different MT service.

Example: Let's say you have configured DeepL to be applied only to French and German.
- If you don’t configure any other MT service, all other languages (except French and German) will not be machine-translated.
- Suppose you configure a different MT service (e.g., Google Translate) with no specific languages selected. In that case, Google MT will be used as default, and all languages (except for French and German) will go through this MT service instead.
Machine Translation services usually provide only one translation variant for a given language. Therefore, any similar locales in Transifex are translated by the Machine Translation service's sole translation language.

For example, Portuguese has five locales (pt, pt_PT, pt_AO, pt_BR, pt_MZ); however, MT services will translate all of them as "pt".
Selecting a main language for a Machine Translation service doesn’t mean all its locales will also be sent to this service.

If, for example, you select “pt” for DeepL and your project contains “pt_BR”, strings in this locale will not be machine-translated unless you explicitly specify that you also want pt_BR to go through DeepL.
In case you need to use a different machine translation key for a specific project, please take a look at the section below.
HTML / Plain text modes do not differentiate in Amazon MT. The result from these two modes is the same due to Amazon API.

Language pairs in Custom.MT are set up directly within templates. Each template supports a single source-to-target language pair. To use Custom.MT in single- or multi-language projects, ensure that you’ve created a separate template for each source-target language pair used in your Transifex projects. Template names should follow this format: <source locale>-<target locale> (e.g., en_US-fr_CA). If no template is found with a given source-target language pair, the source strings will not be translated in that language.

Machine Translation on a Project Level

In Transifex, you can go into a project and override any machine translation settings you may have set for your organization. For example, you could set up Google Translate for your organization and then use Microsoft Translator for just one project. Or you can use one API key for your organization and a different one for a specific project.

To set up machine translation for a specific project:

Select the project from the project navigation in the Dashboard.
Click on Settings.
In the Project Actions section on the right, click on Override organization's Machine Translation settings. A modal window will open allowing you to edit your Machine Translation settings.
Select the machine translation service you want to use.
If you chose Google Translate, add your API key. If you chose Microsoft Translator Text API (latest), add your subscription key; also, while setting this up in Azure (Microsoft's cloud), make sure to select a 'Location/Region' of "Global". If you chose Microsoft Translator (deprecated), add your Client ID and Client secret. If you choose KantanMT, add your API key and engine alias.
Click the Save Changes button.

Enabling Automatic Machine Translation

📝Note: Automatic Machine Translation is available on the Growth plan.

If your translation workflow always starts with Machine Translation, Automatic Machine Translation can save you from manually starting MT. Automatic MT will run whenever you add new content or update existing content to a project.

To enable automatic Machine Translation:

From the Dashboard, select the project for which you want to enable Automatic Machine Translation.
Click on Settings.
In the submenu, click on Workflow.
In the Pre-translation step, enable the AI & Machine Translation Fill-up checkbox and the MT fillup option.
You have the option to exclude languages from MT Fill-up by enabling the option "Exclude languages from Machine Translation Fillup". Once you enable the setting, a list with all the project's target languages will be available for selection.
Click the Save Changes button.

📝 Note:

Please remember that Google Machine translation has limits regarding the recommended maximum length for each request, which is 5K characters. More information can be found here.

All four MT providers we are integrated with have their limitations in supporting variables/placeholders during the translation process. However, we have streamlined this process to the best of our ability, resulting in 99.82% of translations with variables being accurately returned.

Identifying Strings Translated by Machine Translation

There are two ways to know how many words were translated by MT.

Filter in Editor

You can identify the strings that MT translated in your resource files by applying the following filter:

More > Origin > MT: <Provider Name>

Then, you can mass-select all filtered strings and see the word count.

Reports

You can see the number of words translated by MT service on the Reports page.

Machine Translation & Translation Memory Fill-up

If TM Fill-up is enabled for a project, 100% Translation Memory matches will be used before Machine Translation runs.
Automatically machine-translated strings don't go into your Translation Memory until marked as reviewed. The same is true for strings that were machine-translated in bulk.
Suppose you add new project languages or enable Automatic Machine Translation and TM Fill-up after uploading/updating files. In that case, you'll need to trigger MT and fill up from TM manually. You can do this by clicking the Enable fill-up button in your project settings' Fill-up on-demand section in the Workflow tab.

Formality Options

📝Note: Formality options are only available to Transifex -DeepL integration

Through Transifex-DeepL integration, you can now set whether the translated text should lean towards formal or informal language.

This feature currently only works for target languages "DE" (German), "FR" (French), "IT" (Italian), "ES" (Spanish), "NL" (Dutch), "PL" (Polish), "PT-PT", "PT-BR" (Portuguese) and "RU" (Russian). Possible options are:

"more" - for a more formal language
"less" - for a more informal language

Formality settings can be found under Settings -> Machine Translation.

Glossary Terms Protection

Transifex ensures translation consistency across Google Translate, Microsoft Translator, DeepL Translate, KantanMT, Alexa Translations A.I. and Intento when running Machine Translation on your strings and preserves your terminology, ensuring that it remains intact during the translation process.

There's no need for manual configuration, as the system automatically preserves glossary terms whenever they are detected within the source string.

Exception to Glossary Terms Protection

In case a glossary term's translation is missing or contains only spaces, the machine translation will ignore them, and their occurrences on strings in projects linked to this glossary will be translated by machine translation as standard text.

Example

Let's say you have the term "Water Bottle" in your glossary, and this term is not translated to one of your glossary's target languages, in this case, Russian(ru).

And, in one of your projects using this glossary, you have the string "Don't forget to bring a water bottle to stay hydrated on your outdoor adventure."; when you run your translation machine service on this string, the string will be completely translated to Russian as if it were a string that does not contain a glossary term at all.

Glossary Terms Priority

When using machine translation with a glossary, you may come across a situation where a particular string matches multiple Glossary terms. Furthermore, there may be some overlap in the words used between these terms. In such scenarios, our platform needs to determine which Glossary term to use by considering some conditions on these terms; here are the conditions listed in priority order:

Term (or variant) is translated.
Term (or variant) word count.
Single terms (without variants).
Case sensitive terms.

Considering the above conditions priorities, when you have multiple glossary terms matches in a string that you're translating using Machine translation, it will happen as follows:

Term (or variant) is translated. Transifex checks if the glossary terms are translated in the target language you're translating with Machine translation. In case only one term is translated, this will be used for the translation of the string.
1. If more than one term is translated, Transifex will pass to the next condition.
2. If none of the terms are translated, the terms will be ignored, considering the Exception to glossary terms protection rule, and the matching words will be translated as normal text.
Term (or variant) word count. Our platform will check the terms' word counts, and the term with the most words will be taken to translate the string.
1. If multiple terms contain the maximum word count, Transifex will pass to the next condition.
Single terms (without variants). This condition refers to whether the term is part of a glossary variant or a single term. Transifex will prioritize the use of single terms over terms with variants.
1. In case more than one term matches the criteria, then Transifex will pass to the next condition.
Case sensitive terms. The last condition refers to case sensitivity. Specifically. Transifex platform checks if the case-sensitive setting is enabled and takes the one that fulfills the condition.

Example

Let's say you want to translate the string "Machine Learning Model Evaluation" into Spanish(es) using machine translation and having the following Glossary. Note: Only "Machine Learning Model" term is case-sensitive.

All the terms will be offered in the Glossary tab for this string; this means Transifex will need to use the conditions priorities to determine the translation that will be used in the translation.

This is what Transifex will do step by step:

The term "Model" will be discarded by the "Term (or variant) is translated" condition because it does not have a translation.
The term "Machine" will be discarded by the "Term (or variant) word count" condition because the other terms contain more words.
The term "Model Evaluation Rule" will be discarded by the "Single terms (without variants)" because it has other variants such as Model Evaluation, M. Evaluation, and Mdl Ev.
Transifex will choose between "Learning model evaluation" and "Machine Learning Model" terms; only the second term has case sensitivity enabled and matches with the string content, which is why the first term will be discarded.
Finally, Transifex will translate the String using Machine Translation, preserving only the term "Machine Learning Model"

📝Note: Amazon provides its own dedicated solution for glossary support. Please refer to our documentation here for additional information.