Re: XSL stylesheets for TEI XML documents

Patrice Bonhomme writes:

 > This is quite annoying if we have to handle each of the 
 > XSLT implementations. It should be nice to specify a common
 > architecture for managing some more
 > processing/implmentation things.

Actually, I think it is premature. We currently have just one XSLT
processor that claims to be 100% conformant to the spec, and I think
we should wait for the others to catch up. When 

 a) we have 3 or 4 conformant processors
 b) we have more experience with extensions like xt:node-set

then someone can start firming up the extensions. 

 >     <xslx:call name="writeTo"> 
 >       <xslx:param name="method" value="html"/>
 >       <xslx:param name="file" value="{concat($masterFile,'.html')}"/>
 >       <xsl:...>...
 >     </xslx:call>

you can do _something_ like this already with named templates

 <xsl:call template name="output">
 <xsl:param name="file">
 <xsl:param name="contents">
  IF XT then
   xt:document
  ELSIF SAXON then
   saxon:output
  ELSE
   panic
 </xsl:call-template>

its a mild pain stuffing everything in a variable to pass to the
template (which is why I didn't do it), but its not that bad. the
nested xsl:fallbacks I used are not that bad either.

by the way, if we compare extensions, I see that Xalan implements
separate opening and closing of files, and thus templates can append
to an output stream. i wonder whether this is important?

sebastian


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list