Re: XHTML vs. <meta>-only encoding declarations

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bjoern Hoehrmann <derhoermi@gmx.net> 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.

- -- 
"I don't want to learn to manage my anger;
 I want to FRANCHISE it!" -- Kevin Martin

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.0.2

iQA/AwUBPwXZyaPyPrIkdfXsEQLpcwCg64H9wd+MLj9olMdtuP9ob0iP+/8An0GP
8241r6/sGeX0esOESOeycBGm
=DMjS
-----END PGP SIGNATURE-----

Received on Friday, 4 July 2003 15:47:24 UTC