Repository navigation
'quality_optimized' Produces erroneous translation #152
Description
Activity
I can not reproduce this, sorry:
$ curl -X POST https://api.deepl.com/v2/translate \ --header "Content-Type: application/json" \ --header "Authorization: DeepL-Auth-Key KEY" \ --data "{ \"text\": [\"Mio padre è alto.\"], \"target_lang\":\"ES\", \"model_type\":\"quality_optimized\", \"show_billed_characters\":true }" {"translations":[{"text":"Mi padre es alto.","detected_source_language":"IT","billed_characters":17,"model_type_used":"quality_optimized"}]}Nor on deepl.com, with/without source language, I always get "Mi padre es alto". Do you have more examples of this?
import deepl
auth_key = "blablabla"
deepl_client = deepl.DeepLClient(auth_key)def translate(text, source_lang, target_lang, model_type='quality_optimized', formality='prefer_less'):
response = deepl_client.translate_text(
text,
source_lang=source_lang,
target_lang=target_lang,
model_type='quality_optimized',
formality='prefer_less'
)
return response.textprint("DeepL Spanish ⇄ English translator")
italian = 'Mio padre è alto.'
spanish = translate(italian, 'IT', 'ES')
print(spanish)Thanks, with
formality = prefer_lessI can reproduce. This looks like a bug in our translation models to me, I'll investigateJust wanted to give an update here: This is apparently a wider issue and our research team is working on it :) Unfortunately model updates usually take a bit, as the process is more involved.
I have seen numerous examples where adding 'quality_optimized' to the search string produces an erroneous translation, usually involving a possessive adjective.
Example (Italian):
Original phrase: 'Mio padre è alto.'
Translated to Spanish
With 'quality_optimized': 'Tu padre es alto.'
Without 'quality_optimized': 'Mi padre es alto'
I am mystified how this can occur.