Subject: RE: template conflicts From: Linda van den Brink <lvdbrink@xxxxxxx> Date: Tue, 23 May 2000 16:54:53 +0200 |
> My first thought, after reading of Section 2.6.2 (Stylesheet > Import) in the > XSLT spec was that you might be importing 'general.xsl' after > including > 'domain.xsl'. > > Then I tried it out using SAXON, and it shouted at me (very > politely and > quite correctly) because xsl:import elements must come before > xsl:include > elements. Thanks for testing! > I assume that XT complains in the same way, and that your > stylesheet looks like: > > <xsl:import href="general.xsl"/> > ... > <xsl:include href="module.xsl"/> > <xsl:include href="domain.xsl"/> > ... *NO*. My stylesheet does have the includes before the import, but XT does not complain. That must be a bug, then? > If it's a problem in XT and you need to use XT, you could try adding a > priority attribute to the template to get the behaviour you want, but > that's definitely non-optimal. Yep, that works. > Sorry to not be of more help. > > Cheers, > > Jeni > > Dr Jeni Tennison > Epistemics Ltd, Strelley Hall, Nottingham, NG8 6PE > Telephone 0115 9061301 * Fax 0115 9061304 * Email > jeni.tennison@xxxxxxxxxxxxxxxx > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: template conflicts, Jeni Tennison | Thread | RE: template conflicts, Jeni Tennison |
Re: getting element name into html , Clementson, Bill | Date | RE: getting element name into html , Julian Reschke |
Month |