[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: N : M transformation
David Carlisle wrote:
I don't need to decide between a processor-specific extension, I know, but that's why I wrote "[...] or do feature detection". I don't want to do that, since it requires me to write 50 instead of one line. see for example norm's version in the docbook sheets This is exactly the kind of endless detection and workaround code I'm happy to not have to write: <xsl:choose> <!-- put Saxon first to work around a bug in libxslt --> <xsl:when test="element-available('saxon:output')"> <!-- Saxon doesn't make the chunks relative --> <xsl:value-of select="concat($base.dir,$base.name)"/> </xsl:when> <xsl:when test="element-available('exsl:document')"> <!-- EXSL document does make the chunks relative, I think --> ... Norm needs to support a wide selection of XSLT processors, so that's his job, but I'm happy to not have to do that, and instead use a tiny temporary solution and wait for XSLT 2.0. As I wrote. Tobi -- http://www.pinkjuice.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|