...
Name | Type | Info |
text | string | The string to translate. |
source | string | The source language to translate from. Must be valid rfc5646 code. |
| target | string | The target language to translate to. Must be valid rfc5646 code. |
| langresType | string | optional, one (or more, comma-seperated) language-resource types. e.g. "DeepL" or "DeepL,Google" The types can be ('TermCollection', 'NEC-TM', 'OpenTM2', 'DeepL', 'SDLLanguageCloud', 'GroupShare', 'Google', 'Moses', 'Lucy LT', 'TildeMT') |
| langresId | int | optional, one (or more, comma-seperated) language-resource id's, e.g "12345" or "12345,23456" |
| nosegmentation | int | optional, if set to "1" the string to translate will not be segmented (even if it contains punctuation). Please note, the result-layout with segmented & unsegmented texts is different |
| escape | int | optional, if set to "1" the returned texts and any markup will be escaped |
...
| URL | Methods | Parameters | Description | |||||
/editor/instanttranslateapi/filepretranslate | POST | file: multipart/form-data; the file to translate. "0" as field name is deprecated and will not be supported in one of the next transalte5 versions. source: string; the source language to translate from. Must be valid rfc5646 code. target: string; the target language to translate to. Must be valid rfc5646 code. | Step 1: Starts a task-import with the file and its pretranslation. As long as the import is running, the response in step 2 for this file will say "isImporting" instead of returning the download-link. You might need to repeat step 2 until you get the link. The translated files are available until their configured lifetime is over; then they will be removed automatically. Response (example): {"taskId":"539"} | |||||
| /editor/instanttranslateapi/filelist | GET | Step 2: Get a list of all pretranslations that are currently available for the InstantTranslate-user including their downloadUrl. Response: allPretranslatedFiles for tasks with taskId as key .
| ||||||
| editor/instanttranslateapi/writetm | POST | The request parameters must be encapsulated in data parameter as json. ex: data={"sourceLanguage": "en","targetLanguage": "de","source": "Simple text","target": "Einfacher Text"} An example call via CURL could look like this: curl --location --request POST 'http://t5docker.localdev/editor/instanttranslateapi/writetm' \ --header 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' \ --header 'Accept: application/json' \ --header 'Translate5AuthToken: {{token}}' \ --form 'data="{\"sourceLanguage\": \"en\",\"targetLanguage\": \"de\", \"source\": \"Simple text hello\",\"target\": \"Einfacher Text hallo\"}"' | Auto creation of memoryFor each customer and language and language combination provided in the request(see example on the left), one memory will be auto created. And the source and the target content will be saved in those memories. Which customers will be used? The assigned customers to all users, not the current user which is making the request, but all available users in translate5 with instantTranslate role. With the runtimeOptions.InstantTranslate.saveToServices (overwrite on client level) it can be defined which TM memory resources can be used. By default this is disabled on instance level. Currently only available options are t5memory When requesting this api endpoint, for the given language combination and for all clients of a user with InstantTranslate right, a separate OpenTM2 memory will be created (if it does not exist already) and the requested content will be saved there. To enable InstantTranslate memory to be created for the client, this config must be set to something else then the default value, which is "disabled": runtimeOptions.InstantTranslate.saveToServices This system config can be overridden client specific in the clients overview. By default this feature is disabled. |
Configuration of InstantTranslate
...