-
Notifications
You must be signed in to change notification settings - Fork 61
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
Possible to specify translate.google.cn? #14
Comments
Thanks for using translatepy ! This feature isn't available yet on this library as I never understood the reason why people would want to choose to change the domain but now that you are giving me this example I think it would be great to have it in the future versions! |
Thanks a lot. How to use it? |
Hmmm let me investigate this, I think I know where the problem is coming from |
Thanks for the bug report, @ffreemt. In general, it is not necessary to use the Translator class if you want to use only one translator service, you can directly use the class GoogleTranslate(service_url="translate.google.cn"). translate("hello", "fr") |
@Animenosekai , I have prepared a GIT patch that fixes this issue:
|
Nice, that's exactly what I was about to do! |
Thanks guys. Got another problem though.
Also tried |
Thanks, @ffreemt ! I seem to have found the culprit of the problem:
This is because the value zh is not in the Google column of Table ISO639. We are already discussing an alternative implementation #17 |
In fact, I also tried
|
Hi. Thanks for the nice work.
I did some tests with translatepy with google (
google_tr = Translator(use_google=True, use_yandex=False, use_bing=False, use_reverso=False, use_deepl=False).translate
). It worked great.However for users in some region that cannot access translate.google.com, they wont be able to use
google
intranslatepy
.In
googletrans
you can do something likefrom googletrans import Translator; translator = Translator(service_urls=['translate.google.com', 'translate.google.co.kr',])
. Is this possible withtranslatepy
?Thanks a lot.
The text was updated successfully, but these errors were encountered: