DeepL Nodes
The World’s Most Accurate and Nuanced Machine Translation for KNIME
DeepL Translator is a neural machine translation service owned and operated by DeepL SE, based in Cologne. DeepL names itself “the world’s most accurate and nuanced machine translation” and performs remarkably well on any kind of translation task. Using its sophisticated neural networks, DeepL is able to translate texts and documents blazingly fast with an incredible high accuracy into various languages.
DeepL Nodes are free and make all of DeepL Translator’s features easily accessible for KNIME users from within the KNIME Analytics Platform. Developed and maintained by NodePit, DeepL Nodes allow you to translate free texts, upload and download documents for translation, manage your glossaries and get basic information about your DeepL account within your KNIME workflows with a handy set of simple and robust nodes.
DeepL Nodes currently support translating texts and documents to and from the following languages: Bulgarian, Chinese (Simplified), Czech, Danish, Dutch, English (American and British), Estonian, Finnish, French, German, Greek, Hungarian, Indonesian, Italian, Japanese, Latvian, Lithuanian, Polish, Portuguese (Brazilian and European), Romanian, Russian, Slovak, Slovenian, Spanish, Swedish, Turkish, Ukrainian.
DeepL Nodes are regularly updated to support the latest features and languages.
While DeepL Nodes are free to use for the KNIME Analytics Platform, DeepL Translator requires a free or paid account. Sign up for free on the DeepL Website and get your API key.
If you have any questions, comments, or problems, we are happy to hear from you: mail@nodepit.com
We’re not affiliated with DeepL SE.
Contact
VendorNodePit GbR
AddressBienertstraße 33,01187 Dresden,Germany
Emailmail@nodepit.com
Websitehttps://nodepit.com
Content
DeepL
The DeepL API provides programmatic access to DeepL’s machine translation technology.
Server
Node to configure the server endpoints
Authorize
Nodes for different authorization methods
Translate Text
The text-translation API currently consists of a single endpoint, translate, which is described below.
To learn more about context in DeepL API translations, we recommend this article.
Translate Documents
The document translation API allows you to translate whole documents and supports the following file types and extensions:
docx- Microsoft Word Documentpptx- Microsoft PowerPoint Documentxlsx- Microsoft Excel Documentpdf- Portable Document Formathtm / html- HTML Documenttxt- Plain Text Documentxlf / xliff- XLIFF Document, version 2.1srt- SRT Document
Please note that with every submitted document of type .pptx, .docx, .xlsx, or .pdf, you are billed a minimum of 50,000 characters with the DeepL API plan, no matter how many characters are included in the document.
Translating a document usually involves three types of HTTP requests:
- upload the document to be translated,
- periodically check the status of the document translation,
- once the status call reports
done, download the translated document.
To learn more about context in DeepL API translations, we recommend this article.
Manage Glossaries
The glossary functions allow you to create, inspect, and delete glossaries.
Glossaries created with the glossary function can be used in translate requests by specifying the
glossary_id parameter.
If you encounter issues, please let us know at support@DeepL.com.
The DeepL API supports glossaries in any combination of two languages from the following list, enabling a total of 120 possible glossary language pairs:
- DA (Danish)
- DE (German)
- EN (English)
- ES (Spanish)
- FR (French)
- IT (Italian)
- JA (Japanese)
- KO (Korean)
- NB (Norwegian (bokmål))
- NL (Dutch)
- PL (Polish)
- PT (Portuguese)
- RO (Romanian)
- RU (Russian)
- SV (Swedish)
- ZH (Chinese)
The maximum size limit for a glossary is 10 MiB = 10485760 bytes and each source/target text, as well as the name of the glossary, is limited to 1024 UTF-8 bytes. A total of 1000 glossaries are allowed per account.
When creating a glossary with target language EN, PT, or ZH, it's not necessary to specify a variant
(e.g. EN-US, EN-GB, PT-PT, PT-BR, or ZH-HANS).
Glossaries with target language EN can be used in translations with either English variant.
Similarly PT, and ZH glossaries can be used in translations with their corresponding variants.
Glossaries created via the DeepL API are distinct from glossaries created via the DeepL website and DeepL apps. This means API glossaries cannot be used on the website and vice versa.
Note that glossaries are immutable: once created, the glossary entries for a given glossary ID cannot be modified.
As a workaround for effectively editable glossaries, we suggest to identify glossaries by name instead of ID in your application and then use the following procedure for modifications:
- download and store the current glossary's entries,
- locally modify the glossary entries,
- delete the existing glossary,
- create a new glossary with the same name.
Meta Information
Information about API usage and value ranges
Advanced
Nodes for advanced configuration
Nodes
Workflows
01_DeepL_Translate_TextNodePit- 02_DeepL_Translate_Text_with_ContextNodePit
- 03_DeepL_Meta_DataNodePit
- 04_DeepL_GlossaryNodePit
Further Links
Installation
To use this product in KNIME, install the extension DeepL Nodes from the below update site:
A zipped version of the software site can be downloaded here.