If you send it with an html mime type, then what you _should_
get is the same as if the input had been >abc with a visible > sign,
which is why incidentally the so called "compatibility rules" in XHTML
are fundamentally broken. Relying on <br /> to produce a linebreak
not a linebreak followed by a > sign means that you are _relying_ on the
browsers using a non conformant parser for HTML. Browsers almost always
do use a non conformant parse so it sort of works, but a "standard"
should never have suggested that it is a good thing. HTML validating
systems often do use an SGML parser (nsgmls, typically) and there things
often break, <br /> validates as the extra text > is allowed in any
content model that allows <br/> but for example
<meta .../>
fails to validate as it is equivalent to
<meta ...>>
and you cant have extra > text in the head of the document.
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--