Upload and Translate a Document
This call uploads a document and queues it for translation. The call returns once the upload is complete, returning a document ID and key which can be used to query the translation status and to download the translated document once translation is complete.
Because the request includes a file upload, it must be an HTTP POST request with content type multipart/form-data
.
Please be aware that the uploaded document is automatically removed from the server once the translated document has been downloaded. You have to upload the document again in order to restart the translation.
The maximum upload limit for documents is available here and may vary based on API plan and document type.
You may specify the glossary to use for the document translation using the glossary_id
parameter.
Important: This requires the source_lang
parameter to be set and the language pair of the glossary has to match the language pair of the request.
Language of the text to be translated. Options currently available:
BG
- BulgarianCS
- CzechDA
- DanishDE
- GermanEL
- GreekEN
- EnglishES
- SpanishET
- EstonianFI
- FinnishFR
- FrenchHU
- HungarianID
- IndonesianIT
- ItalianJA
- JapaneseKO
- KoreanLT
- LithuanianLV
- LatvianNB
- Norwegian (Bokmål)NL
- DutchPL
- PolishPT
- Portuguese (all Portuguese varieties mixed)RO
- RomanianRU
- RussianSK
- SlovakSL
- SlovenianSV
- SwedishTR
- TurkishUK
- UkrainianZH
- ChineseIf this parameter is omitted, the API will attempt to detect the language of the text and translate it.
The language into which the text should be translated. Options currently available:
BG
- BulgarianCS
- CzechDA
- DanishDE
- GermanEL
- GreekEN
- English (unspecified variant for backward compatibility; please select EN-GB
or EN-US
instead)EN-GB
- English (British)EN-US
- English (American)ES
- SpanishET
- EstonianFI
- FinnishFR
- FrenchHU
- HungarianID
- IndonesianIT
- ItalianJA
- JapaneseKO
- KoreanLT
- LithuanianLV
- LatvianNB
- Norwegian (Bokmål)NL
- DutchPL
- PolishPT
- Portuguese (unspecified variant for backward compatibility; please select PT-BR
or PT-PT
instead)PT-BR
- Portuguese (Brazilian)PT-PT
- Portuguese (all Portuguese varieties excluding Brazilian Portuguese)RO
- RomanianRU
- RussianSK
- SlovakSL
- SlovenianSV
- SwedishTR
- TurkishUK
- UkrainianZH
- Chinese (unspecified variant for backward compatibility; please select ZH-HANS
instead)ZH-HANS
- Chinese (simplified)The document file to be translated. The file name should be included in this part's content disposition. As an alternative, the filename parameter can be used. The following file types and extensions are supported:
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 DocumentFile extension of desired format of translated file, for example: docx
. If unspecified, by default the translated file will be in the same format as the input file.
Note: Not all combinations of input file and translation file extensions are permitted. See Document Format Conversions for the permitted combinations.
Sets whether the translated text should lean towards formal or informal language.
This feature currently only works for target languages
DE
(German),
FR
(French),
IT
(Italian),
ES
(Spanish),
NL
(Dutch),
PL
(Polish),
PT-BR
and PT-PT
(Portuguese),
JA
(Japanese),
and RU
(Russian).
Learn more about the plain/polite feature for Japanese here.
Setting this parameter with a target language that does not support formality will fail,
unless one of the prefer_...
options are used.
Possible options are:
default
(default)more
- for a more formal languageless
- for a more informal languageprefer_more
- for a more formal language if available, otherwise fallback to default formalityprefer_less
- for a more informal language if available, otherwise fallback to default formalitySpecify how the response should be mapped to the table output. The following formats are available:
Structured Table: Returns a parsed table with data split into rows and columns.
Raw Response: Returns the raw response in a single row with the following columns:
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension DeepL Nodes from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.