Simon Shutter wrote:
How could I do this in XSLT 1 if I had to? Could I use .Net to create a
compiled transform that would work with Andrew's stylesheet?
Thanks
Saxon8 is available for .NET, as open source, and is very stable. You
did not mention XSLT 1 in your original post and because parsing non-XML
files is the area for XSLT 2, not 1, we assumed XSLT 2. The latter has
very many new possibilities and can do so much that was (next to)
impossible in XSLT 1, so if you are able to switch, I highly recommend
you to do so. For many it makes learning XSLT much more fun and much
easier to do.
If you have to stick to XSLT 1, and your file is an external source
(i.e., it is not part of a variable) you are out of luck: create an
extension function. But since you are telling that you are new to XSLT,
I hope you are able to switch to 2.0, because that will make this task
bearable (and much easier for us to point you to the right solutions).
-- Abel Braaksma
--~------------------------------------------------------------------
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>
--~--