On Wednesday 06 March 2002 18:04, Tod Harter wrote: > Replacing the <xsl:include/> with <xsl:import/> of the same URL results in > a warning and failed inclusion of the referenced stylesheet's templates. I > don't know if the original poster had exactly the same problem or not. For > me include was perfectly acceptable, so I never investigated the problem > further. > > and I'm certainly using LibXSLT, so it would appear that the version of > AxKit and LibXSLT I have at least doesn't like to recognize <xsl:import/>.
Note that import has stricter restrictions than include. IOW, xsl:import *must* occur before any other element (other than other occurances of itself) in the xsl:stylesheet children. Given LibXSLT's affection for cryptic errors, I wouldn't be surprised if it said something completely unrelated. I've noticed people often using import and include interchangeably to achieve inclusion. Nothing wrong with that of course, so long as one is cautious of their behaviour differences. Imho it's better to stick to include for simple inclusion, and only use import for its extra features (ie stylesheet subclassing). -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- The first myth of management is that it exists. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
