Re: [xslt] libxslt

["William M. Brack" <wbrack mmm com hk>]

http://www.w3.org/TR/1999/REC-xslt-19991116#include :
The xsl:include element is only allowed as a top-level element.

http://www.w3.org/TR/1999/REC-xslt-19991116#dt-top-level :
An element occurring as a child of an xsl:stylesheet element is called
a top-level element.

So, the answer to your original question 'I don't understand what the
"include was not compiled" msg means.' should perhaps be "The xslt
processor was unable to recognize the <xsl:include> within the context
in which it appeared".

On a more serious note, the overriding concern of libxslt is to provide
a very fast and efficient transformation of well-formed stylesheets.
There are many instances where error conditions within the stylesheet
produce messages which take substantial effort to decode (I
personally often resort to running the problem sheet through one of
the "competing" processors [saxon is my favourite, but in this particular
instance:

[wbrack@infobase1 wbrack]$ java com.icl.saxon.StyleSheet aus.xsl aus.xsl
Failed to compile style sheet
At xsl:copy-of on line 9 of file:/home/wbrack/aus.xsl: Variable StyleInfo
has
not been declared

it is also somewhat cryptic]).

Regards,
W. Brack
>
> <received from="Daniel Veillard" date="22 Jul 2001" time="20:49">
>
> <response>
>
> G'day Daniel,
>
> Fair enough, I hadn't confirmed whether it was allowed (but OTOH,
> where is it proscribed?).
>
> But it does not solve the real problem, that of the include not working
...

>   On Mon, Jul 23, 2001 at 10:27:50AM +1000, John Hurst wrote:
>   >   <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version=
> "1.0">
>   >     <xsl:variable name="StyleInfo">
>   >       <xsl:element name="META">
>   >         <xsl:attribute
name="HTTP-EQUIV">Content-Style-Type</xsl:attribute>
>   >       </xsl:element>
>   >     </xsl:variable>
>   >   </xsl:stylesheet>
>
>     Hum ... xsl:element outside of a template ... I don't handle those,
>   I'm uncertain if this is really allowed ... This would require a bit
>   of work to support.
>     In the meantime
>       <xsl:variable name="StyleInfo">
>         <META HTTP-EQUIV="Content-Style-Type"/>
>       </xsl:variable>
>    should allow to bypass this limitation,
>
>   Daniel