W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2004

[Bug 719] Doctype/encoding fallback issues

From: <bugzilla@wiggum.w3.org>
Date: Mon, 17 May 2004 07:05:02 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1BPcBK-0000hu-O7@wiggum.w3.org>


------- Additional Comments From link@pobox.com  2004-05-17 03:05 -------
cf. Comment #5;

HTTP specifies that the absence of a charset parameter in the Content-Type field
means a default of ISO-8859-1. The HTML 4.01 Recommendation says something along
the lines of "This has turned out to be sub-optimal. You should disregard this
and default to UTF-8 instead."

IOW, when no other charset information is present -- including any defaults
implied from an XML Content-Type -- we can pick either ISO-8859-1 or UTF-8
depending on whether we choose to listen to the IETF or the W3C. After many
(*many*) discussions on w-v we've ended up listening to the W3C.

As for why there is no warning in the case outlined in Comment #3, this is due
to the page generating a fatal error. The exception handler is conservative in
what it tries to spit out because fatal errors usually occur too early and the
datastructures are in a garbage state.

I'll look into whether we can fix it in this particular case.

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Monday, 17 May 2004 03:05:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:06 UTC