Machine translation

Lingobit Localizer can translate with DeepL, Google Translate, and Microsoft Azure Translator. You use your own account with the provider. Text is sent to a provider only when you use machine translation; projects stay local files.

Machine translation is available in Professional and higher. In Translator Edition it is available when the translator project was prepared with Professional or higher.

Set up a provider

1. Choose Tools > Machine Translation Settings.

2. Select the provider and enter its credentials:

   • DeepL — the Auth Key. Leave Endpoint empty to select it automatically: keys ending with :fx use the free endpoint, all others the paid endpoint.

   • Google Translate — select the API Version. For version 2, enter a Cloud Translation API key. For version 3, click Open service account JSON and enter the Project ID and Location. Google Translate is a paid service.

   • Azure Translator — the Auth Key and the Region of your Translator resource. Change Endpoint only if you use a custom endpoint.

   The links in the dialog open the provider's instructions and portal.

3. Click Test to check the credentials before you start.

Credentials are stored on your computer for the current Windows user, under %LOCALAPPDATA%\Lingobit\Integration, protected for this user. They are not saved in the project, so a project you send to a translator does not contain your keys.

Translate

• To translate the whole project into the current target language, choose Project > Translate Using and the provider: DeepL Translator, Google Translate, or Azure Translator.

• To translate the selected items, use Translation > Translate Using.

• To see suggestions for one item, open the Translation Hints pane. It shows several variants from each provider with their similarity and length, and whether each variant passes validation.

If a provider is not set up yet, Localizer offers to open the settings.

Machine translations get the Auto status. After machine translation, Localizer applies safe automatic fixes, such as hotkeys, placeholders, and ending punctuation; you can turn this off with Safe fixes after machine translation. See Validation settings. Review machine translations before release; use the Needs Review filter to find them.

Machine translation is also useful for localizability testing: it shows how text of the target language fits your dialogs and forms.