Re: Saxon & xsltproc giving different output (SOLVED)

On Thu, Dec 29, 2011 at 02:33:13PM -0600, Russell Urquhart scripsit:
[snip]
> In looking at this i started looking at the key dfined and used in the loop:
> 
>   <xsl:key name="module-index" match="errata_section" use="module_impacted"/>
> and the containing loop:
> 
>      <xsl:for-each select="//errata_section[generate-id(.)=generate-id(key('module-index', module_impacted)[1])]">
>         <xsl:sort select="module_impacted"/>
[snip]
> So i started looking in the data file for anomalies. Turns out that there was a <modules_impacted> element with a value of HDQ/1-wire. All the others had the value of HDQ. i.e.
[snip[
> I'm glad its fixed, but can anyone share some light as to why such an anomaly would play out like that?

generate-id() should return a string which is "syntactically an XML
name", so my first impulse is to wonder if that slash is causing
something, somewhere, to type-choke.

-- Graydon