- From: Christopher R. Maden <crism@maden.org>
- Date: Fri, 25 Oct 2002 17:12:17 -0700
- To: www-validator@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When unable to detect an encoding, the new validator should use the prescribed defaults, which I believe still means ISO8859-1 for text/html over HTTP, and UTF-8 or UTF-16 for XHTML documents uploaded directly. With the simple interface, validating <URL: http://crism.maden.org/ > reports that it is unable to detect the encoding, including using Appendix F of XML 1.0. Using Appendix F is inappropriate for a document delivered over HTTP, since the HTTP headers take precedence (and thus it should be interpreted as ISO8859-1), but even so, using the Appendix F algorithm should result in a determination of UTF-8. Either way, since this page is 7-bit ASCII, the validation ought to work. The new service looks great, though. ~Chris, compulsive validator - -- Christopher R. Maden, Principal Consultant, crism consulting XML - SGML - HTML - DTDs/schemas - conversion - training - ebooks - B2B <URL: http://crism.maden.org/consulting/ > PGP Fingerprint: BBA6 4085 DED0 E176 D6D4 5DFC AC52 F825 AFEC 58DA -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.8 iQA/AwUBPbnd4axS+CWv7FjaEQJCygCg8+bf5xtKIgqWIamsytiZBV+mcn0AnihY 6Z2WW+mk+kB027d4CqM3WyP6 =rEdr -----END PGP SIGNATURE-----
Received on Friday, 25 October 2002 20:29:44 UTC