Andrew Welch wrote:
(*) Both Saxon and MSXSL do it in ~30 seconds, so it's really problem with
the XSLT performance in FF.
Perhaps it doesn't like things like:
<xsl:template match="text()[not(ancestor::artwork)]">
Not sure what you think is a problem here.
and
select="count(//ed:del|//ed:ins)!=0"
I just moved this into a global variable, and the performance difference
for MSXML and Saxon isn't measurable, while for xsltproc it's huge. So
xsltproc apparently computes this multiple times, although it doesn't
need to.
So is this a problem with the XSLT code, or the implementation?
and
<xsl:if test="not(ancestor::ed:del) and not(//xref[(_at_)target=$anchor])">
...very much :0)
The only way to avoid the "//" above would be to use xsl:key, which
didn't seem necessary so far because Saxon and MSXML seem to perform
well without. I'll give that a try when I have time.
(and putting /> on a new line is imho just horrible)
BR, Julian
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--