- From: Terje Bless <link@pobox.com>
- Date: Fri, 4 Jul 2003 23:29:15 +0200
- To: W3C Validator <www-validator@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bjoern Hoehrmann <derhoermi@gmx.net> wrote: > >* Terje Bless wrote: >>>The MarkUp Validator gives no errors / warnings / whatever, it just >>>tells the document is valid. The CSS Validator will treat the document >>>as UTF-8 encoded XML document and throw an error for the bad UTF-8 >>>sequence. At least one of the validators should be changed to get >>>consistent results. Which and how? >> >>Given the Content-Type of text/html, I would say the CSS Validator is >>in error here and should be amended to either pay attention to the >><meta> value or use the HTTP defaulting rules (depending on what your >>position on the HTTP vs. HTML vs. MIME defaulting rules is). >> >>Granted XML rules suggest UTF-8 or -16 for this case, but as it's >>served as text/html -- e.g. Appendix C rules -- these do not, IMO, >>apply. > >But the MarkUp Validator honors the XML declaration in such documents... So it does, but I'm inclined to consider this a bug where text/html documents are concerned. And note that it only considers an explicitly given encoding from the XML Declaration and does not apply XML defaulting rules here. - -- We've gotten to a point where a human-readable, human-editable text format for structured data has become a complex nightmare where someone can safely say "As many threads on xml-dev have shown, text-based processing of XML is hazardous at best" and be perfectly valid in saying it. -- Tom Bradford -----BEGIN PGP SIGNATURE----- Version: PGP SDK 3.0.2 iQA/AwUBPwXxqaPyPrIkdfXsEQIaCwCg48dEzBzn1OELowipQ88qXZ+gi9gAoO7T n2tBAwM3/SueWh6z/xA44c/G =Kx5p -----END PGP SIGNATURE-----
Received on Friday, 4 July 2003 17:29:18 UTC