On 8 February 2010 08:58, Tab Atkins Jr. jackalmage@gmail.com wrote:
On Mon, Feb 8, 2010 at 5:01 AM, Nicolas Neuss neuss@math.uni-karlsruhe.de wrote:
Faré fahree@gmail.com writes:
I'm experiencing the same error with Chromium, which is probably not any client to tell to go to hell.
This page contains the following errors:
error on line 2 at column 3: Char 0x0 out of allowed range Below is a rendering of the page up to the first error.
Presumably, a lot of WebKit-based browsers will fail with the same error. Safari anyone?
http://www.weitz.de/hunchentoot? Works with Safari (4.0.4).
It's dependent on the encoding. If you interpret the page as utf-8, there's an encoding error (except I get it at line 2 column 54). If you interpret it as Windows-1252, it displays fine. Chrome 4.0.279.78 on Windows here.
So is the solution that said hunchentoot page should declare its encoding in HTTP headers?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] If it's not worth doing right, it's not worth doing. — Scott McKay