ReversoTranslator BUG about translate HOT 7 OPEN

requests doesn't supports HTTP/2, probably that's why it's throws exception ChunkedEncodingError. Or there is some problem in server side. Anyway, if we send exactly same request with curl, we get useful information about error itself:

{"error":"direction_invalid","errorType":"validation"}⏎

from translate.

@reddere, as a workaround, please specify the source language of the text, as Reverso recognises text in Catalan. However, the translate endpoint doesn't support Catalan translation:

from translatepy.translators.reverso import ReversoTranslate

translator = ReversoTranslate()

text = 'Una manera única de conseguir la victoria\n\nJonesyTheGoat'
t = translator.translate(text, 'Italian', 'Spanish')
print(t)

from translate.

I made some investigation and came to conclusion that when we send request from Chromium, even from Icnognito mode, Reverso correctly detects language as Spanish, if we export same request as curl format from Network tab of Devtool and execute it in terminal, we get Catalon language as in requests result. Probably Reverso uses some fingerprinting algorithm to detect the source of incoming requests, I have no better explanations.

from translate.

I deeply appreciate the insightful replies @ZhymabekRoman . Unfortunately I cannot set the source language as I'm using the translator to translate from multiple languages (english, spanish and german mainly) to italian. If reverso detects the source of incoming requests, will passing a Chromium User-Agent in headers work?

from translate.

will passing a Chromium User-Agent in headers work?

Nope

from translate.

As a workaround, I think you can use Google to detect the language and pass it to Reverso for translation.

from translate.

Hmm requests.exceptions.ChunkedEncodingError is not really common, might need to investigate a bit

from translate.