Machine Translation

Machine translation engines integrated with Crowdin Enterprise provide translation suggestions from services like Google Translate and AutoML Translation, Microsoft Translate, and others.

MT suggestions are displayed in the Editor’s TM and MT Suggestions section in the order of the engines’ configuration dates. To prioritize a specific engine’s suggestions, configure that engine first.

Also, you can perform Pre-Translation using MT engines.

Add More Machine Translation Engines Install more machine translation engines from the Crowdin Store.

By default, machine translations are enabled for each project, but it is required to configure the translation engines before the project members can use them. If you want to disable this option for specific projects, clear Show machine translation suggestions in Project Settings.

To configure the machine translation engines, follow these steps:

1. Open your organization’s Workspace and select Machine translation on the left sidebar.
2. At the bottom right, click Add MT Engine.
3. In the appeared dialog, select an engine from the drop-down list.
4. (Optional) Edit the name of the MT Engine if needed.
5. Enter the requested credentials.
6. (Optional) Select applicable languages. Alternatively, leave empty for access to all languages.
7. (Optional) Select projects in which you want to use the MT engine. Alternatively, leave empty to enable it for all organization projects.
8. Click Create.

Microsoft Translator

Go to Windows Azure to access your Microsoft Translator API subscription key. Translator Text API offers a free tier with 2,000,000 translated characters.

Note

If the Resource Location associated with your Microsoft Translator Text API key is other than global, please make sure to specify it along with other credentials while configuring the Microsoft Translator MT engine in your Crowdin account.

How to sign up for the Microsoft Translator Text API

DeepL Translator

DeepL API is accessible only with the DeepL API Free and Pro subscription plans (For developers tab). Navigate to the DeepL Pro Account page to get a unique Authentication Key. Please note that the DeepL API plan is the only plan that provides this feature.

If you’re subscribed to a different subscription plan, you can switch to the DeepL API plan in your personal account settings. DeepL also provides a simulator that allows you to check your Authentication Key in action.

ModernMT

ModernMT Real time translation API is accessible with the Real time or Human-in-the-loop subscription plans. Navigate to the ModernMT Dashboard to get your License key. If you’re subscribed to a different subscription plan, you can switch to the Real time or Human-in-the-loop plan via the Manage Plan page.

Amazon Translate

The free version of Amazon Translate is available for 12 months. Afterward, you will need to pay for the number of characters translated. Crowdin uses Standard Text Translation type provided by Amazon Translate. Read more about available Amazon Translate pricing options.

Read more about obtaining your access key needed for Amazon Translate integration.

To use your Custom Terminology, follow these steps:

1. Specify your AWS Region (e.g., us-east-2).
2. Select your Custom Terminology from the respective drop-down menu.

What are the minimal scopes for an IAM user required to set up Amazon Translate to be used in Crowdin?

The minimal IAM scopes required depend on whether you’re using terminologies or not:

Without terminologies:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "translate:TranslateText",
      "Resource": "*"
    }
  ]
}

With terminologies:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "translate:TranslateText",
        "translate:GetTerminology",
        "translate:ListTerminologies"
      ],
      "Resource": "*"
    }
  ]
}

Alternatively, you can use the AWS managed policy: TranslateReadOnly, which provides the necessary read-only access to Amazon Translate.

Note

The "Resource": "*" allows access to all resources. For stricter security, consider limiting this to specific AWS regions or resources if applicable.

Google Translate

To use Google Translate, you shall have a Google Cloud account with an active billing profile. Cloud Translation is priced monthly based on usage. Learn more.

To obtain the API key necessary for integration, follow these steps:

1. Go to Google Cloud Console. Log in to the existing Google Cloud account or set up a new one.
2. Select an existing project or add a project using the New Project.
3. Go to API & Services > Library and search for Cloud Translation API.
4. Click Enable.
5. Go to API & Services > Credentials and click Create credentials > API key.
6. Copy the API key and click Close.

Google Cloud AutoML Translation

To use AutoML Translation, you shall have a Google Cloud account with an active billing profile. Google AutoML Translation is priced monthly based on how many characters you send for translation. Learn more.

To create a service account key and obtain the necessary credentials for integration, follow these steps:

1. Go to Google Cloud Console. Log in to the existing Google Cloud account or set up a new one.
2. Select an existing project or add a project using the New Project.
3. Go to API & Services > Library and search for Cloud AutoML API.
4. Click Enable.
5. The next step is to create a service account private key pair. The service account is used by Crowdin. Applications use service accounts to make authorized API calls.

To set up authentication and create your private key, follow these steps:

1. Go to API & Services > Credentials.
2. Click Create credentials > Service account.
3. In the Service account name field, enter a name that describes what this service account will do.
4. Click Create and continue.
5. From the Role list, select Project > Cloud Translation API Editor and click Continue.
6. Click Done.
7. In the API & Services > Credentials, click on the created service account.
8. Switch to the Keys tab.
9. Click Add key > Create new key.
10. Select JSON and click Create. A JSON file that contains your key will be downloaded to your computer.

Google Cloud AutoML Custom Glossary Configuration

Google Cloud AutoML custom glossary allows you to translate your domain-specific terminology consistently. You can use only one Google Cloud AutoML custom model at once. If you have multiple custom models you’d like to use in your Crowdin Enterprise projects, create multiple instances of Google Cloud AutoML MT engine under your Crowdin Enterprise account, specifying the different models in the settings of each MT engine. During the pre-translation via MT, you can alternately use Google Cloud AutoML with the needed model.

To configure your Google Cloud AutoML custom glossary, follow these steps:

1. Open your organization’s Workspace and select Machine translation on the left sidebar.
2. At the bottom right, click Add MT Engine.
3. In the appeared dialog, select Google AutoML Translate from the Engine drop-down list.
4. Click Select file and upload your JSON credentials.
5. (Optional) Specify your Custom Model.

   Note

   If no Google Cloud AutoML custom model is specified in the MT engine settings, the Google NMT model will be used instead.
6. Specify your Resource location (e.g., us-central1).
7. Select your Glossary from the respective drop-down list.
8. (Optional) Configure language mapping between Custom Model and Crowdin languages.
9. (Optional) Select applicable languages. Alternatively, leave empty for access to all languages.
10. (Optional) Select projects in which you want to use the MT engine. Alternatively, leave empty to enable it for all organization projects.
11. Click Create.

MT Engine IDs

Once you specify your MT engine credentials, the system automatically assigns a unique MT engine ID. Later on, you can use these IDs in API requests for pre-translation via machine engines.

You can find the MT engine ID in the organization’s Workspace > Machine translation page. Alternatively, you can also get your MT engine IDs via API.

Clearing MT Engine Cache

When MT engines are updated with new features or models, cached translations in Crowdin Enterprise may no longer reflect the latest translation capabilities. To display updated translations in the Editor’s TM and MT Suggestions section, clear the MT engine cache. This can be especially useful if you’ve already viewed certain strings in the Editor, as Crowdin Enterprise stores cached MT suggestions for those strings.

To clear the cache for your configured MT engine, follow these steps:

1. Open your organization’s Workspace and select Machine translation on the left sidebar.
2. Click (or right-click) on the needed MT engine in the list.
3. Click Clear cache.

See Also

Pre-Translation Speed up the translation process and ease the work of translators.

Project Settings Configure machine translation settings for your project.