-
Notifications
You must be signed in to change notification settings - Fork 389
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
Add DeepL Translator (close #203) #204
Conversation
There seems to be an encoding problem with DeepL (at least on my Mac). It returns non-ASCII characters with their Unicode code point. Example:
The replaced characters here are This is only with the deepl engine. google, bing and yandex are fine. – Tom |
@tflo |
Thanks for the info. Will try to find a workaround… – Tom |
Well, here an – ugly – workaround, with a bit of Perl to convert the characters:
Tested only on a few samples. – Tom |
Should be fixed by 4536adc using bash. |
Preface: Sorry I am noob. I 'git pull' in my local 'translate-shell' directory for the newest files (to include DeepL) however in the command line "trans -S" deepl is not found. Could you steer me in a direction to solving this problem? |
@vmeade Please check your version. Updated one should be 0.9.6.6.
|
Isn’t this committed yet? With DeepL and 0.9.6.6 I still get the hex code points in the output when I remove my perl after-treatment. The same with 0.9.6.6-git:c8107fe (installed via Homebrew |
Seems broken again in 0.9.6.7 (via homebrew) |
Due to recurring requests (#203, #121, and some email buried in the snow).
Usage:
trans
with option-e deepl
.:engine "deepl"
to the configuration file.Example:
$ trans :en 'mi casa es su casa' -e deepl mi casa es su casa my home is your home [ Español → English ] My house is your house. My home is your home. my house is your house