This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Dynamic stylesheet selection
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] Dynamic stylesheet selection
- From: "J. J. Merelo" <jmerelo at geneura dot ugr dot es>
- Date: Wed, 04 Apr 2001 18:42:31 +0200
- Organization: GeNeura team
- References: <3ACB1406.A440DE82@geneura.ugr.es> <3ACB19D2.F239CD33@alu.ua.es>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> <xsl:otherwise>
> <xsl:processing-instruction name="xml-stylesheet">
> href="../xsl/articulo.capitulos.xsl" type="text/xsl"
> </xsl:processing-instruction>
> <xsl:processing-instruction name="cocoon-process">
> type="xslt"
> </xsl:processing-instruction>
> </xsl:otherwise>
> </xsl:choose>
>
I tried something like that, but the problem is that the processor will
have to be applied each time to the new files "from outside", unless you
are within a framework that allows XSLT chaining, like AxKit or Cocoon.
What I would like is something like this
Initial XML document -> Initial XSLT -> XML doc 1 -> XSLT(2)
->....->XSLT(2)->Final XML doc -> Final XSLT
That is, make an XSLT generate initial content from an XML spec, make it
throug several iterations using the same XSLT, until a "final" XML
document (that could be recognized using a counter, or whatever), which
would be applied a final XSLT. Right now, I can achieve just one step
using saxon this way:
<xsl:output method="xml" indent="yes" saxon:next-in-chain='an.xsl'/>
But what I would like to is to make that "output" variable, making
saxon:next-in-chain a different file, possibly each time, and method
"html" in the final stage.
In this case, what this proprietary extension does is to chain XSLT
transformations. I don't know if there's an equivalent non-proprietary
way of doing it.
Thanks in any case for all answers received!
J
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list