-
-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Google translation results returned by this lib are different from results returned by web translation. #283
Comments
It happened yesterday. The request rate is more limit and quality is reduce. |
same ? maybe "500 error" has gone...right? -> patched by xpz3 |
Test text "I was 37 then, strapped in my seat as the huge 747 plunged through dense cloud cover on approach to Hamburg airport. Cold November rains drenched the earth, lending everything the gloomy air of a Flemish landscape: the ground crew in waterproofs, a flag atop a squat airport building, a BMW billboard. So - Germany again." by Jay Rubin google official web translate result:
deep-translator:
result:
google unofficial API result:
result:
This seems to be more a case of the API endpoint different than a literary interpretation. |
see this #289 (comment) |
deep_translator_test.py
and it returns
web returns
It seems that Google is changing these undocumentary APIs, the happened to another API a few days ago. The API used by this lib also happened today. Moreover, this API seems to be unstable at the moment, with intermittent 500 errors. Has anyone else had this problem?
The text was updated successfully, but these errors were encountered: