Google Cloud Translation
Description
Google Cloud Translation is a machine translation service. The OMN integration works together with Google via an API.
Cloud Translation enables OMN to dynamically translate text programmatically via an API. It uses a Google pre-trained or custom machine learning model to translate text.
To use the Google Could Translation in the OMN context, a paid subscription must be purchased.
More information about Translation API and Translation AI in general can be found here.
Supported languages
The list of supported languages is the following:
Afrikaans, Albanian, Amharic, Arabic, Armenian, Azerbaijani, Basque, Belarusian, Bengali, Bosnian, Bulgarian, Catalan, Cebuano, Chinese (Simplified), Chinese (Traditional), Corsican, Croatian, Czech, Danish, Dutch, English, Esperanto, Estonian, Filipino (Tagalog), Finnish, French, Frisian, Galician, Georgian, German, Greek, Gujarati,
Haitian Creole, Hausa, Hawaiian, Hebrew, Hindi, Hmong, Hungarian, Icelandic, Igbo, Indonesian, Irish, Italian, Japanese, Javanese, Kannada, Kazakh, Khmer, Kinyarwanda, Korean, Kurdish, Kyrgyz, Lao, Latin, Latvian, Lithuanian, Luxembourgish, Macedonian, Malagasy, Malay, Malayalam, Maltese, Maori, Marathi, Mongolian, Myanmar (Burmese),
Nepali, Norwegian, Nyanja (Chichewa), Odia (Oriya), Pashto, Persian, Polish, Portuguese (Portugal, Brazil), Punjabi, Romanian, Russian, Samoan, Scots Gaelic, Serbian, Sesotho, Shona, Sindhi, Sinhala (Sinhalese), Slovak, Slovenian, Somali, Spanish, Sundanese, Swahili, Swedish, Tagalog (Filipino), Tajik, Tamil, Tatar, Telugu, Thai, Turkish,
Turkmen, Ukrainian, Urdu, Uyghur, Uzbek, Vietnamese, Welsh, Xhosa, Yiddish, Yoruba, 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 dependant attributes are translated) |
"Artikelnummer, Farbe" |
|
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 |
Google specific parameters
| Key (* = required) | Type | Default | Description | Example |
|---|---|---|---|---|
ext.ai-translation.google.apiUrl* |
string |
Base URL of the google translation service |
||
ext.ai-translation.google.apiKey* |
string |
API Key for the google translation service |
||
ext.ai-translation.google.sourceLanguageTagMappings |
string |
The mappings from language tags to the Google Source Languages. The language tag is constructed from the *_omnSourceLanguage and its configured ISO language and country code. For example 'German (Switzerland)' with a configured ISO language code of 'ch' and a country code of 'CH' will be translated to the language tag 'ch-CH', which then could be mapped to Google Source Language "de" by using "ch-CH:de". 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 Google Source Language. |
us-EN:en,ch-CH:de |
|
ext.ai-translation.google.targetLanguageTagMappings |
string |
The mappings from language tags to the Google Target Languages. The language tag is constructed from the *_omnTargetLanguage and its configured ISO language and country code. For example 'English' with a configured ISO language code of 'us' and a country code of 'EN' will be translated to the language tag 'us-EN', which can be mapped to the Google Target Language "en" by specify the mapping "us-EN:en" here. 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 Google Target Language. |
us-EN:en,ch-CH:de |
Example configuration
The following image shows what a sample configuration for Google Cloud Translation 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.