The BS DeepL TMS Connector translates Contentserv Translation Jobs via DeepL API. Visit deepl.com for more information. DeepL is known for its excellent machine translations and is used increasingly to automate or partly automate translation tasks.
Supported Languages include
- "BG" - Bulgarian
- "CS" - Czech
- "DA" - Danish
- "DE" - German
- "EL" - Greek
- "EN" - English
- "EN-GB" - English (British)
- "EN-US" - English (American)
- "ES" - Spanish
- "ET" - Estonian
- "FI" - Finnish
- "FR" - French
- "HU" - Hungarian
- "IT" - Italian
- "JA" - Japanese
- "LT" - Lithuanian
- "LV" - Latvian
- "NL" - Dutch
- "PL" - Polish
- "PT" - Portuguese (all Portuguese varieties mixed)
- "PT-PT" - Portuguese (all Portuguese varieties excluding Brazilian Portuguese)
- "PT-BR" - Portuguese (Brazilian)
- "RO" - Romanian
- "RU" - Russian
- "SK" - Slovak
- "SL" - Slovenian
- "SV" - Swedish
- "ZH" - Chinese
A complete and updated overview is listed at https://www.deepl.com/docs-api/translating-text/request/
Source and target languages in a Contentserv Translation Job are automatically mapped to the corresponding locale supported by the DeepL API.
Where possible, the most specific locale is used as the target language (e.g., "EN-GB" or "EN-US" instead of "EN").
To use the BS DeepL TMS Connector, first, you need a (charged) API developer subscription plan. For details, please visit https://www.deepl.com/pro.html#developer.
From the DeepL account settings, you can retrieve your authentication key for the DeepL API. Copy this to the BS DeepL configuration within Contentserv:
Additionally, as with any TMS connector, you have to activate it in the BPM Translation Manager settings:
Once this is completed, you are ready to use the DeepL connector.
Using the DeepL Connector
When the connector is properly licensed, the API Key is set in the global options, and the connector is activated in the BPM Translation Manager settings; you will find multiple integration cases in the Translation Manager of Contentserv.
Use DeepL Translation Tips in the Term Editor
A straightforward way to import a translation is in the term editor. Here you will find a toolbar button with the tooltip "Translate via Deepl Translator," which will send the text in the source language to the DeepL API and fill the returned translation to the target language editor:
Use DeepL Translations in the Term List
Another way of using the connector is the context menu in the TMS terms list:
This will send all selected terms to DeepL and write the translations back.
Use DeepL Translations as Export Plugin
Last but not least, the BS DeepL Connectors show up in the Export tab of the TMS jobs in the list of "Automatic Export" plugins:
When this plugin is selected, the terms will be sent to the DeepL API as soon as you click on the download or upload buttons in the editor's toolbar.
Use DeepL Translations to translate documents
The following file types are supported for translation:
- .pdf (Please note that to translate PDF documents, you must give one-time consent to using the Adobe API via the account interface.)
The maximum upload limit for any document is 10MB and 1.000.000 characters.
Documents are translated with the BS DeepL Translate Documents Active Script. The script is Context Sensitive.
|One or multiple documents for translation|
|Context Sensitive||If the script can be executed from other contexts (e.g., the PIM tree)|
|The source language of that document|
|The languages into which the document is translated|
|Target Folder||(Optional) Translated documents can be moved to a folder. If no folder is selected, the translated documents are created in the same folder as the translated document.|
|Add Timestamp||(Optional) Timestamp, which can be added to the file name of the translated document.|
The glossary functions allow you to create and manage glossaries in Contentserv that are considered for all DeepL translations.
Activate the Use Glossary option in the configuration to use existing glossaries for translations.
In the DeepL settings, you can create new glossaries. Each glossary must have a specific source and target language.
New entries can be added to the glossary via the list view. The dictionary can be uploaded to DeepL with the Transfer to DeepL button.
In the case of failed translations, the plugin throws an error. Detailed information on this is listed in an error log:
If the debug mode in the configuration of the connector is activated, API requests and responses to the DeepL API are also logged.