This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: my output just contains xsl code
- To: xsl-list at mulberrytech dot com
- Subject: RE: my output just contains xsl code
- From: sara dot mitchell at ps dot ge dot com
- Date: Wed, 7 Jun 2000 14:05:11 -0400
- Reply-To: xsl-list at mulberrytech dot com
Sorry to all for the misinformation! (red face >-:) Apparently it was
also true of a very early version of LotusXSL which is where
I 'mislearned' this.
Sara
> -----Original Message-----
> From: Kay Michael [mailto:Michael.Kay@icl.com]
> Sent: Wednesday, June 07, 2000 1:53 AM
> To: 'xsl-list@mulberrytech.com'
> Subject: RE: my output just contains xsl code
>
>
> > From: sara.mitchell@ps.ge.com [mailto:sara.mitchell@ps.ge.com]
> >
> > You fell foul of one requirement that may seem obvious (but others
> > have also missed it including myself): At least one of your
> templates
> > must 'select' a node to apply the template to.
>
> No this isn't true (not with a conformant XSLT 1.0 processor,
> anyway). If no
> template rule matches a node, the built-in template rule
> kicks in, and does
> an <xsl:apply-templates/> to its child nodes automatically.
>
> But the statement is true, IIRC, for Microsoft IE5 1998 XSL,
> as this is one
> of the many XSLT features it didn't implement.
>
> Mike Kay
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list