-
Notifications
You must be signed in to change notification settings - Fork 60
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
Result mismatch Google Translate #80
Comments
Related issue: #22 (comment) |
Thanks, that works well! |
Yup for now translate/translatepy/translators/google.py Lines 78 to 86 in 1033e1f
The reason is that |
@Animenosekai so v2 better than v1? |
Well without reverse engineering the token generation, yes (maybe?) |
Hi guys, hope you are doing well.
I know that you are pretty busy working on v3 and may are already aware of this already, but just in case I open this issue.
When using the GoogleTranslate service, the translation is different from what we get in the website/app:
[1] Google translate result:
Sincerely sorry for not having replied to your messages more quickly, when the file is transmitted to the developers, we temporarily no longer have visibility on it.
[2] translatepy result:
Honestly sorry not to have answered your messages faster, when the file is transmitted to the developers, we do not temporarily have more visibility on it.
Any ideas of what/why could be this caused? I actually tried changing the session header as per #79 but it did not have any effect on the translation result.
[1]
[2]
The text was updated successfully, but these errors were encountered: