[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Namespace-aliasing and excluded namespaces
> The problem with Libxslt is that, wrt to namespace exclusion, > it somehow processes the literal result elements, which are > the children of an xsl:template, differently than literal > result elements deeper in the subtree of an xsl:template. The > latter do work fine - or at least better. That startled me on first reading but then I remembered that Saxon has similar differences - if a literal result element is textually included within another in the stylesheet then you don't need to bother outputting the in-scope namespaces that were also in-scope for the outer element because they will be inherited anyway (unless inherit-namespaces is off). There were a few Saxon bugs in this area in the past, for example where the namespace is excluded and is therefore omitted from the outer element, but where it's then used on an attribute of the inner element and therefore needs to be output there. Michael Kay http://www.saxonica.com/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|