13 Mar
2008
13 Mar
'08
5:34 p.m.
Jorge wrote:
On Fri, Mar 07, 2008 at 06:17:17AM +0000, place wrote:
This is no sort of proper fix whatsoever, but I was tired of seeing the "would set charset" message. It's actually surprisingly useful for remote files, since they're generally still at the javascript-and-css point at the end of the first packet.
In CVS there is a new approach that restarts parsing the whole page. It works with local/remote files, and page title. Please test it.
In the past, I've encountered pages that go <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> </head> Here's code just sticking in a flag when meta charset's been seen.