Re: XSLT 1.0 support in browsers, as of June 2008
Julian Reschke schrieb:<xsl:template match="text()[not(ancestor::artwork)]">
Yes, that's what it's supposed to do :-).
I haven't examined your program, but there might be a way to code this more efficiently, maybe by using an artwork mode or an artwork parameter, so the information is available at each step and does not have to be looked up 3464 times, as in rfc2616.xml.
That's certainly possible, but it would mean that lots of code needs to be duplicated (mode), or rewritten to use named templates (which I'd like to avoid to keep the code readable).
There probably isn't any problem with this one expression. Your heavy use of the descendant axis is likely to involve much more scanning, especially when started at the root. The processor has to search the entire document, and if the document has a lot of nodes, this may take a long time, even growing exponentially.
I do understand that this is expensive, but it's sometimes a result of the XML vocabulary being transformed. xsl:key can help in same cases, but it's not always possible to use it, for instance because it doesn't work when parts of the content do not originate from same the source file.
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