> I read the post from Jbryant on the 21st of Sep that provided > a workaround - but we are not running XSLT 2.0 yet, so that > option is out for now.
Anything (well, almost) that can be done in 2.0 can be done in 1.0. It just takes more arcane weirdness and tends to be much more verbose. If you can create representative samples of the kind of input you have to process and the kind of output your users want, I can try to help you create a 1.0 solution to it. Those kinds of questions are also welcome at the Mulberry XSL list, to which you can subscribe from this page: http://www.mulberrytech.com/xsl/xsl-list/ Jay Bryant Bryant Communication Services (presently consulting at Synergistic Solution Technologies) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
