Re: [xsl] Partial Implementation of XInclude include element

[David Carlisle <davidc at nag dot co dot uk>]

> So: which behavior is more correct? Or have I inadvertantly turned on a
> convenience feature of Saxon?

hard to say without seeing your stylesheet but if you have a literal
result element in a template then the resulting element in the result
tree will have namespace nodes for every namespace in scope on teh
literakl result element except the xslt namespace and namespaces listed
as extension namespaces or exclude-result-prefixes.
So most likely if fo namepsace is declared on xsl:stylesheet it will end
up in the output unless you take pains to stop it.

If you mean thatthe built in engine produces something that isn't
namespace well formed ie it has elements in a fo: namespace but without
any namespace declaration for fo: then that is certainly a bug in the
XSLT engine. The output should never have missing namespace decls.

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list