As a matter of fact I was about to ask what parser OO.org is using. There's no
chance to use Saxon in OO.org, is there? :)

Thanks for the hint on the saxon function though.


--------------------------------------------------------------------------
Zitat von David Carlisle <davidc@xxxxxxxxx>:

> 
> Manos
> 
> > All you have to do is make sure no templates in the two XSL files match 
> > both XML and XHTML nodes, If that is the case you can simply merge
> > them. 
> 
> No that won't work to chain transformations.
> 
> Since the requirement was to use XSLT2 I assume that the original poster
> is using Saxon8, in which case he can use the saxon:next-in-chain
> attribute on xsl:outout, see
>
http://www.saxonica.com/documentation/extensions/output-extras/next-in-chain.html
> 
> (I wasn't aware the you could use saxon8 to process filters in OO.org)
> 
> David
> 
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________