Thank you David, that was very helpful.
You're right, I must have run the 1.0 stylesheet through Saxon before I
added the translate() to the key definition. And I've just verified that
XMLSpy still chokes on the stylesheet without the variables in the key, so I
wasn't deluding myself in thinking there was some kind of problem there. But
I'll redo this in 2.0 because it's a lot easier to read, as you say.
Can I <xsl:import> existing version 1.0 stylesheets which do other useful
things into a 2.0 stylesheet which does the glossary-specific stuff? Or do I
have to change them all? Currently I use xsltproc for a large number of
small transforms because the performance edge over a 2.0 processor adds up
to a significant time saving in the full build, and it seems that the
optimal fix here would be to use Saxon for the glossary-specific stuff
without having to go away and create 2.0 copies of all the low-level
stylesheets.
Cheers
Trevor
-----Original Message-----
From: David Carlisle [mailto:davidc(_at_)nag(_dot_)co(_dot_)uk]
Sent: Wednesday, 21 May 2008 12:02 a.m.
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] glossary sorting/indexing question
--~------------------------------------------------------------------
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>
--~--