Hi, On Sat, 2012-08-25 at 20:10 +0000, corvid wrote:
Andreas wrote:
I tried to use translate.google.com with dillo and it does not work with non-ascii characters. I do not know http by heart so that I know what character set should be send in the post request but it seems not to be what google expects. Words with non-ascii characters are not translated and non-ascii characters are turned into questionmarks.
With our default http_user_agent setting, I see this problem as well. With it set to a firefox string, translate.google.com seems to work fine.
setting it to a firefox string gives <meta content="text/html; charset=UTF-8" http-equiv="content-type"> instead of <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> but google seem to always want utf-8 from the html form. So it seems to be a clear google bug. Greetings Andreas Kemnade