Altova Mailing List Archives

Re: [xsl] Thank you Daniel & Brian...

From: David Carlisle <davidc@--------->
Date: 3/30/2003 10:47:00 PM
> ...which I knew was right but had expected for
> the above three to catch any such oops. They
> did not, but the 3WC validator did.

xalan (and any other XSLT engine) doesn't know _anything_ about HTML at
all: it just generates the nodes that you specify so it won't catch any
html errors.

Neither mozilla nor IE use a validating HTML parser, they are designed
to render any hand-authored junk that is thrown at them....

If you are generating XHTML rather than XML then the XML parser in
mozilla is non validating, so also won't catch validation errors.. The
XML parser in IE can validate if you turn on validation from script, but
by default it is non validating, and by default the output of XSLT (even
if specified as being xml) goes to the html parser not the xml one.

This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:

 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.