katharine wykes wrote:
That's really useful, thanks.
The ammended code seems to be causing Netscape 6 to crash. Can you see
a problem with the xslt:
The general strategy for tracking down bugs is to
use a command line XSLT processor (Saxon, Xalan, MSXML)
and run the transformation outside the browser. This
will give away problems in the XSLT and the source XML.
Using several processors can be an advantage.
Check the resulting HTML whether it looks right, then
load it into the browser. If everything is fine,
Netscape's XSLT engine has a problem (well, NS6.x for
x<2 has plenty of problems, don't even try).
It might be a good idea to try the last Mozilla release
(1.1 beta as of this writing), and report the crash if
it still happens.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list