The translation and localization management platform POEditor supports a number of advanced options for machine translation.

If you're using tags in your localization project, the first advanced option you'll find in the Automatic Translation page is I want translations for the strings tagged with. You can use this option to machine translate just a specific group of strings.

For Google and Azure AI Translator, the Automatic Translation feature supports the option Format, which can be set either to Plain text or HTML (recommended for strings containing HTML tags, because it can better preserve the tags during translation). By default, the Format option is set to Plain Text.

For DeepL, the Automatic Translation feature supports the options Tag Handling, Split Sentences, Preserve Formatting and Formality.

Tag Handling tells the machine translation engine what kind of tags to take into consideration. The options are None, HTML and XML. By default, the Tag Handling is set to None.

Split Sentences tells the machine translation engine whether to split the strings into sentences or to treat each string as a single sentence. You can choose No Splitting, to have each string treated like a single sentence, Split on punctuation and on newlines or Split on punctuation only (without splitting on newlines).
By default, this option is set to Split on punctuation and on newlines.

Preserve Formatting tells the translation engine whether to respect the original formatting of the source texts or not. The formatting that's taken into consideration by this option is the punctuation and upper/lower cases at the beginning and the end of sentences. By default, this option is set to No.

Formality tells the translation engine whether to lean more toward formal language or less formal language. If you don't choose something else, the machine translation engine DeepL will use the option Default.
The Formality option is only available when selecting one of these target languages:

• German
• French
• Italian
• Spanish
• Dutch
• Polish
• Portuguese
• Portuguese (Brazil)
• Russian

If you have at least the Premium plan, you can also send a Glossary to Google, for the machine translation engine to take into account.

Good to know:

• In order for the option to appear, you need to have a Glossary set in the project's Settings
• In order for Google to use the Glossary, you need to have definitions in it for all the languages you want to translate
• The functionality works on a search and replace principle: Google uses the definitions in the Glossary to replace the corresponding Glossary terms in the translated languages
• The target language text is not adapted in any way
• The case used is the one from the Glossary definition from the target language
• The case of source language string is ignored. For example, Hello or hello will be replaced with the target language equivalent from the Glossary
• If there are multiple strings with the same text in the Glossary, only the last one added will be sent to Google
• If you want to use the credentials for Google Translate API V3 and the bucket where the Glossary will be stored, the respective credentials have to enable permissions for Google Translate and Google Storage.