...
| Config name | Values | Default | Description |
|---|---|---|---|
Using the config in the database: runtimeOptions.plugins.DeepL.server | list | ["https://api.deepl.com"] | DeepL Api Server; format: ["SCHEME://HOST:PORT"] |
Using the config in the installation.ini runtimeOptions.plugins.DeepL.server[] | https://api.deepl.com | ||
| runtimeOptions.plugins.DeepL.authkey | string | (put your api key here) | The authentication key as found in your DeepL-account settings Please note: Since translate5 is NOT a CAT-tool with a license-per-user model, translate5 uses the volume-based DeepL API, as agreed by the DeepL company.. You will need the "DeepL API" license key "for developers". Please see https://www.deepl.com/de/pro.html#developer. You pay a basic fee per month and on top a volume based fee. |
| runtimeOptions.plugins.DeepL.matchrate | integer | 70 | DeepL penalty value, used as default matchrate since in MT no matchrate is available |
Term collection as glossary source for DeepL language resource
The checkbox "DeepL glossary source" at the termCollections configuration decides, if the terminology of this termCollecton is automatically uploaded to DeepL. If yes for each language pair of DeepL that has a matching language combination in the termCollection and that is assigned to the same client the terminology is uploaded. If the checkbox is unchecked in the TermCollection or the client is removed from the TermCollection or the DeepL language resource or one of both language resources is deleted, the terminology on the side of DeepL is deleted.