Hello, > Philippe's work works around this, but is XSLT supposed to work with > possibly broken HTML?
XSLT will not process a document that is not *valid* XML. My understanding, since we are using an XSLT transform to generate the HTML (using the default output method, which is XML...), is that the Provider output is *well-formed* XML, but invalid because it lacks the XML header and a single root node. Which means that the workaround I did should fix all ecma-provider output (as long as the output encoding remains UTF-8, which is quite likely). I don't know about other providers. Generally speaking, requiring providers to output HTML as well-formed XML (even if it's invalid) is probably a Good Thing, but I don't know if it is the case currently. phil _______________________________________________ Mono-docs-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-docs-list
