Mort Yao

Could you please provide a minimal example file to reproduce the issue?

The problem is not on Japanese or the encoding, but on the format of the file. translate-shell expects the input file to be plain text. Unfortunately, HTML format is not...

Google banning frequent requests is a known issue here (#349).

I'm not sure if I understand the motivation here. Why are commas not preferable in this case? Separate lines will make the output overly long, and different colors should not...

Ah, I see where the problem is. Maybe a better format is ``` "не так просто, как часто кажется", "не совсем так просто, как это часто делается, чтобы быть" ```

Hi, Thanks for maintaining the Arch package. Just to clarify, the sha1sum string `e9959df02300279b46e1bf7bc4739b07891d86b4` is for the standalone file (which can be downloaded from either https://www.soimort.org/translate-shell/trans or http://git.io/trans, or by...

I agree that download *integrity* is important in all cases, especially when the hosting server / network relays are unreliable. But to "verify the source of the release" (which involves...

> but it's a good indicator that something's gone sideways if things suddenly don't match up and a new key, unsigned by the old one, is being used to sign...

I can't look into such an issue if I can't reproduce it on my machine -- instead of the terminal recording, please present 1) The exact commands you are using...

What is your output exactly? The result I got is consistent with Google Translate's web interface: ``` $ trans -brief -e google en:zh "FileMaker 17’s new master-detail layouts display the...