But you have just stumbled into the nastiest hornet's nest of XHTML, which is that there's no agreed-upon MIME type for XHTML. And older browsers will, of course, choke on XHTML especially if you set one of the more "correct" mime types (that is, not text/html). I don't remember all the details, but it's all well put out in an article called XHTML considered harmful or seomthing like that. Personally, I do my final output from XSLT in HTML format.
simon
On Wednesday, November 19, 2003, at 08:40 AM, Andy Gale wrote:
Hi,
I've recently started using AxKit and XSP/XSLT to produce web pages. I'm
trying to output XHTML 1.0 with certain formatting quirks such as no
carriage returns after <li>blah</li> elements. Using the
AxTraceIntermediate directive I've managed to ascertain that something
seems to converting my XHTML into HTML and reformatting it. This is
causing a problem with the rendering in IE. I can find no description
in any of the documentation as to why this would happen. Is there
anyway to get around this?
Regards,
Andy -- Andy Gale Developer, intY Ltd, Bristol, UK [e: [EMAIL PROTECTED] w: www.inty.com t: +44 (0)1454 640512]
intY has scanned this email for all known viruses (www.inty.com)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- anti-spam: do not post this address publicly www.simonwoodside.com -- 99% Devil, 1% Angel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
