-
Notifications
You must be signed in to change notification settings - Fork 730
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
Translation by googletrans is different from result from google translate web #434
Comments
Same issue 🫡 |
@am1guard This project seems to be poorly maintained, you can find discussion in another project issue related to Google translate api. But unfortunately, the thing has not any progress yet. |
Well I don't know if it's right to write this here but I'm currently using a library called deep-translator. Deep-translator doesn't use Google translate web. It use translate.google.com api. So I recommend it. I tried it yesterday and it works fine |
Thanks for your recommend, I'll try it. :) |
I plan to investigate this issue, but I think I don't have enough time at the moment. I’m not sure how long it will take to resolve, but I'll do my best to fix it. |
Seems like there is a better end-point - also see this - #268 (comment) |
Before submitting, please confirm that:
Googletrans version
4.0.1+
Issue Type
Bug Report
Current Behavior
Translation by googletrans is different from result from google translate web.
I don't know if this is normal, I came here from another translation plugin that uses Google's API, and obviously both are different from the results of the Google Translate web version. A few days ago, the results should have been the same, at least some names were translated completely differently in the API and on the web.
Expected Behavior
Maybe the result should be the same? I don't know if there is a way to make it work by changing the API that might exist.
Steps to Reproduce
No response
Related Code
No response
Other Information
A piece of example:
source:
result from api:
result from web:
The text was updated successfully, but these errors were encountered: