-
Improvement
-
Resolution: Fixed
-
None
-
Critical
-
-
Emptyshow more show less
A DeepL-specific switch in the configuration should determine, what "formality"
value is used for translation with DeepL.
By default "default" should be used.
This should be overwriteable on client and task-import-level, but not on task level.
See https://www.deepl.com/docs-api/translating-text/ the switch "formality".
[TRANSLATE-2357] introduce DeepL config switch "formality"
Workflow | Original: MittagQI Workflow [ 30407 ] | New: MittagQI Workflow with Peer [ 36097 ] |
Status | Original: Test Ready [ 10005 ] | New: Done [ 10000 ] |
Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |
Status | Original: Selected for Development [ 10100 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: Selected for Development [ 10100 ] |
Status | Original: Selected for Development [ 10100 ] | New: In Progress [ 3 ] |
Rank | New: Ranked higher |
Status | Original: Test Ready [ 10005 ] | New: Selected for Development [ 10100 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |
ChangeLog Description |
New:
The "formality" deepl api flag now is available as task import config. More about the formality flag: Sets whether the translated text should lean towards formal or informal language. This feature currently works for all target languages except "EN" (English), "EN-GB" (British English), "EN-US" (American English), "ES" (Spanish), "JA" (Japanese) and "ZH" (Chinese). Possible options are: "default" (default) "more" - for a more formal language "less" - for a more informal language |