On Wednesday 06 March 2002 10:10, Robin Berjon wrote: > On Wednesday 06 March 2002 15:11, Tod Harter wrote: > > 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! > > Note that XSLT has a "feature" that makes it not fail when external > documents can't be resolved (you might at best get a warning). Note also > that there are restrictions on where some elements can occur.
Yeah, I got a warning (and of course bad xslt output). In my case I had something like: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0"> <xsl:include href="perform_html.xsl"/> <xsl:template match="/"> (rest of stylesheet omitted...) which works fine with the included file in the same directory (which also contained the xml file being processed, its a simple example). 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. My error log shows the following line. [Wed Mar 6 11:58:54 2002] [error] [client 127.0.0.1] [AxKit] [Error] compilation error: file unknown-000143409632 element import 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/>. I admit though, there are more recent patches than I have for AxKit, so maybe its related to something thats been fixed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
