Re: CSS validator stricter than XML validator

Bjoern Hoehrmann wrote:
> 
> * Philippe Le Hegaret wrote:
> >Bjoern Hoehrmann wrote:
> >> The HTML Validator treats the document as compatible HTML document, the
> >> CSS Validator as XML document. You define
> >>
> >>   <meta http-equiv="Content-Type" content="text/html;
> >>                                             charset=iso-8859-1" />
> >>
> >> in the document, the literal [ιδ...] are recognized as ISO-8859-1
> >> characters.
> >
> >> In XML document, the encoding must be declared in the XML
> >> declaration, your document doesn't have an (or 'a'?) XML declaration, so
> >> the document is treated as UTF-8-encoded and the octets for the
> >> mentioned 8-Bit-characters in ISO-8859-1 aren't valid UTF-8 sequences.
> >
> >Not only in the XML declaration but also in the protocol. See
> >ftp://ftp.isi.edu/in-notes/rfc3023.txt.
> 
> Yes, but the octet sequences the XML parser receives must match the
> (implicit or explicit) declared encoding.

Not exactly. only if the information doesn't come from an external
transport protocol:
[[[
In the absence of information provided by an external transport protocol
(e.g. HTTP or MIME), it is an error for an entity including an encoding
declaration to be presented to the XML processor in an encoding other than
that named in the declaration
]]]

-- Extensible Markup Language (XML) 1.0 (Second Edition)
http://www.w3.org/TR/2000/REC-xml-20001006#charencoding
Thu, 05 Oct 2000 12:19:51 GMT

The following sentence in the same section is misleading:
[[
 It is also a fatal error if an XML entity contains no encoding declaration
and its content is not legal UTF-8 or UTF-16.
]]

and should read:

"Unless an encoding is determined by a higher-level protocol, it is also a fatal
error if an XML entity contains no encoding declaration and its content is not
legal UTF-8 or UTF-16."

Philippe

Received on Tuesday, 15 May 2001 13:58:02 UTC