OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: DOCBOOK-APPS: Customization causing a spurious"Error: no ID for constraint linkend" message

Yes, that's exactly what I'm doing (version 1.1 with Saxon 6.5.2; See p. 490 of Mike Kay's book). Sorry I didn't mention it. 

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";

I was just being lazy and not writing portable code--or for that matter pasting in and calling the template that Mike provides on p. 490 that would make it portable :) I should give it a try using version="1.0" and node-set(), perhaps version="1.1" has some side effect wrt xsl:key?


> -----Original Message-----
> From: Dave Pawson [mailto:dpawson@nildram.co.uk]
> Sent: Sunday, November 10, 2002 3:12 AM
> To: Bob Stayton; David Cramer; docbook-apps@lists.oasis-open.org
> Subject: Re: DOCBOOK-APPS: Customization causing a spurious "Error: no
> ID for constraint linkend" message
> At 01:12 10/11/2002, Bob Stayton wrote:
> >The line in question is:
> >
> >  <xsl:for-each select="$current.nodeset/node()">
> >
> >Since $current.nodeset is created with a xsl:copy-of, it
> >is a result tree fragment.  How come your processor doesn't
> >stumble on this?
> I use it regularly, with SAXON 6.5.2, setting version to 1.1
> Mike added this in preparation for xslt 1.1 which since died.
>   It handy though, and will be valid again in xslt 2.0
> regards DaveP.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC