Sent by Sebastien_LE_CALLONNEC on 29 September 2003 15:03
Thank you all for your answers.
Lars skrev:
"This is not strictly on topic, but not strictly off either. The xml prolog
affects how style sheets are treated in IE and possibly other browsers."
Sorry, _does_ sound off-topic: I forgot to say that it's because I
faced problems while designing pages for IE that I happened to wonder about
this xml prologue. It was working fine without the header, but reading the
spec led me to think that I had to use this xml tag.
I was using a meta tag stating:
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
and therefore wasn't using an UTF-8 encoding. My doubts were raised by the
"higher-level protocol" bit: the HTTP request has been given a latin-1
encoding via the meta tag and it should mean I MAY use the xml prologue
indeed. But is HTTP the "higher-level protocol" referred to? As Markus
stated it, it sounds more like a "deeper-level" protocol to me...
Lars skrev ocksa:
"However, IF you are sending your xhtml documents as application/xhtml+xml
to understanding browsers (many people will argue that you should) AND if
you are using character encodings other than UTF-8, then you MAY wish to
also send the xml prolog to those browsers."
Well, that's actually what happens because adding the prologue tends to
break things when it comes to CSS - when working with IE. I much prefer to
leave it out rather than finding tricks to find out who accepts it and who
doesn't; but I'm still wondering it that's standard or not...
What I didn't know was that it changed the style-sheet behaviour and
this really puzzles me: as far as I know, such a header is useful to state
the encoding. What's the link with CSS interpreting? I was aware of the
!DOCTYPE switch, but not the xml prologue one.
Sebastien.
ps.- I modified the Subject since it was not relevant anymore.
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/