Keryx webb wrote:
xml-prologue
The XML Prologue is the section of the document that contains the XML
Declaration, DOCTYPE and any comments or PIs prior to the root element.
The XML Declaration on the other hand, or (more specifically) the
encoding declaration within the XML declaration, is the
Andrew Cunningham wrote:
Lachlan Hunt writes:
Andrew Cunningham wrote:
In theory the docuemnt should only be in one of the unicode
encodings, so without a BOM, the browser should try to render it as
UTF-8.
No, because when it's served as text/html, HTML rules apply, not XML
rules. So witho
Lachlan Hunt writes:
Andrew Cunningham wrote:
I was wondering if you should have another test in there: XHTML document
with no encoding declared in the http header or in a meta tag, and no xml
declaration. Sent as html/text.
That's text/html and an XHTML document served as text/html is HTML,
Andrew Cunningham wrote:
I was wondering if you should have another test in there: XHTML document
with no encoding declared in the http header or in a meta tag, and no
xml declaration. Sent as html/text.
That's text/html and an XHTML document served as text/html is HTML,
regardless of any lie
Keryx webb writes:
Andrew Cunningham wrote:
Keryx webb writes:
That's what we were discussing. If a page is sent as XHTML, one could
argue that it's supposed to be self-documenting, and that it might mean
that the xml-prologue should be more important than the http-header. As my
page pro
Hej!
Keryx webb skrev:
That's what we were discussing. If a page is sent as XHTML, one could
argue that it's supposed to be self-documenting, and that it might
mean that the xml-prologue should be more important than the
http-header. As my page proves, in FFox, MSIE and Opera (the three
I've
Andrew Cunningham wrote:
Keryx webb writes:
According to my tests Firefox *will* use the charset specified in the
http-header over the one in the XML-prologue if a page is sent as
application/xhtml+xml. (Or more exactly, regardless whether the page
is sent as text/html or application/xhtml+x
Keryx webb writes:
According to my tests Firefox *will* use the charset specified in the
http-header over the one in the XML-prologue if a page is sent as
application/xhtml+xml. (Or more exactly, regardless whether the page is
sent as text/html or application/xhtml+xml.) As will Opera.
i