Microsoft Translator
Description
The Microsoft Translator is a machine translation service. The OMN integration works together with Microsoft via an API.
The Microsoft Translator is a proven, customizable and scalable technology for machine translation which is using industry standard REST technology.
More information about text translation and API can be found here.
To use the Microsoft Translator in the OMN context, a paid subscription must be purchased.
Supported languages
The list of supported languages is the following:
Afrikaans,
Albanian,
Amharic,
Arabic,
Armenian,
Assamese,
Azerbaijani (Latin),
Bangla,
Bashkir,
Basque,
Bosnian (Latin),
Bulgarian,
Cantonese (Traditional),
Catalan,
Chinese (Literary),
Chinese Simplified,
Chinese Traditional,
Croatian,
Czech,
Danish,
Dari,
Divehi,
Dutch,
English,
Estonian,
Faroese,
Fijian,
Filipino,
Finnish,
French,
French (Canada),
Galician,
Georgian,
German,
Greek,
Gujarati,
Haitian Creole,
Hebrew,
Hindi,
Hmong Daw (Latin),
Hungarian,
Icelandic,
Indonesian,
Inuinnaqtun,
Inuktitut,
Inuktitut (Latin),
Irish,
Italian,
Japanese,
Kannada,
Kazakh,
Khmer,
Klingon,
Klingon,
Korean,
Kurdish (Central),
Kurdish (Northern),
Kyrgyz (Cyrillic),
Lao,
Latvian,
Lithuanian,
Macedonian,
Malagasy,
Malay (Latin),
Malayalam,
Maltese,
Maori,
Marathi,
Mongolian (Cyrillic),
Mongolian (Traditional),
Myanmar,
Nepali,
Norwegian,
Odia,
Pashto,
Persian,
Polish,
Portuguese (Brazil),
Portuguese (Portugal),
Punjabi,
Queretaro Otomi,
Romanian,
Russian,
Samoan (Latin),
Serbian (Cyrillic),
Serbian (Latin),
Slovak,
Slovenian,
Somali (Arabic),
Spanish,
Swahili (Latin),
Swedish,
Tahitian,
Tamil,
Tatar (Latin),
Telugu,
Thai,
Tibetan,
Tigrinya,
Tongan,
Turkish,
Turkmen (Latin),
Ukrainian,
Upper Sorbian,
Urdu,
Uyghur (Arabic),
Uzbek (Latin),
Vietnamese,
Welsh,
Yucatec Maya,
Zulu
All languages can be seen on this page.
| The languages can be adapted by the providers, which may result in discrepancies between the page and the languages actually supported. |
| As this Workflow uses write operations to PIM attributes via REST API, the OMN user executing this Workflow needs to be in an admin role. API admin roles are configured in property 'omn.eai.api.admin.roles' in EAI Properties |
Configuration Parameters
Workflow-Name: ai-translation
General parameters
| Key (* = required) | Type | Default | Description | Example |
|---|---|---|---|---|
ext.ai-translation.translationService* |
string |
Name of the AI translation service which should be used ('deepl', 'ms', 'google' or 'systran') |
deepl |
|
ext.ai-translation.attributes |
string (multi) |
List of attribute identifiers which should be translated (per default all language dependent attributes are translated) |
"Artikelnummer, Farbe" |
|
ext.ai-translation.allowOverwrite |
boolean |
true |
Controls if existing values should be overwritten. If this is set to false then attributes which already contain values for the target language will not be translated (no additional cost occur) |
false |
ext.ai-translation.sourceLanguages |
language (multi) |
required |
List of content source languages which should be translated |
English, German |
ext.ai-translation.targetLanguages |
language (multi) |
required |
List of content target languages which should be translated to |
French, Japanese |
Microsoft specific parameters
| Key (* = required) | Type | Default | Description | Example |
|---|---|---|---|---|
ext.ai-translation.ms.apiUrl* |
string |
Base URL of the ms translation service |
||
ext.ai-translation.ms.apiKey* |
string |
API Key for the ms translation service |
||
ext.ai-translation.ms.sourceLanguageTagMappings |
string |
The mappings from language tags to the Microsoft Source Languages. The language tag is constructed from the *_omnSourceLanguage and its configured ISO language and country code. For example 'French' with a configured ISO language code of 'fr' and a country code of 'FR' will be translated to the language tag 'fr-FR', which then could be mapped to Microsoft Source Language "fr-ca" (canadian french) by using "fr-FR:fr-ca". Multiple mappings need to be comma separated. There should usually be no need to set this parameter with another mapping. See also General Language Mapping. Note that the ".putAll", ".removeAllKeys" feature is not yet available here. By default no mappings are provided and the ISO language code will be used as Microsoft Source Language. |
us-EN:en,ch-CH:de,fr-FR:fr-ca |
|
ext.ai-translation.ms.targetLanguageTagMappings |
string |
The mappings from language tags to the Microsoft Target Languages. The language tag is constructed from the *_omnTargetLanguage and its configured ISO language and country code. For example 'French' with a configured ISO language code of 'fr' and a country code of 'FR' will be translated to the language tag 'fr-FR', which then could be mapped to Microsoft Target Language "fr-ca" (canadian french) by using "fr-FR:fr-ca". Multiple mappings need to be comma separated. There should usually be no need to set this parameter with another mapping. See also General Language Mapping. Note that the ".putAll", ".removeAllKeys" feature is not yet available here. By default no mappings are provided and the ISO language code will be used as Microsoft Target Language. |
us-EN:en,ch-CH:de,fr-FR:fr-ca |
Example configuration
The following image shows what a sample configuration for Microsoft Translator might look like.
A detailed step-by-step guide to the configuration of the Workflow Config Function plug-in can be found on this page.