On Wednesday 06 March 2002 07:54, cutlass wrote: > ----- Original Message -----
Well, I had the same problem. LibXSLT refused to process <xsl:import/>. I just assumed it was broken. I agree though, if you are using Sablotron, dump it, it doesn't work as well as libxml. They both have a few quirks though! > From: "cutlass" <[EMAIL PROTECTED]> > To: "Dave Brooks, BCS Systems" <[EMAIL PROTECTED]> > Sent: Wednesday, March 06, 2002 11:38 AM > Subject: Re: xsl:include v's import > > > thats because u are probably using sablotron which only supports include > > ( see http:://www.gingerall.com/charlie/ga/act/gadoc.act?pg=sablot ) > > > > > > u may use the libxslt XSLT processor with AxKit. > > > > cheers, jim fuller > > > > > > ----- Original Message ----- > > From: "Dave Brooks, BCS Systems" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, March 06, 2002 10:08 AM > > Subject: xsl:include v's import > > > > > Hi, > > > > > > AxKit seems to ignore <xsl:import/> whereas <xsl:include/> is fine > > (apart > > > > from problems finding the file). > > > > > > Any ideas?] > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Dave > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
