Re: [xsl] (possible) strange behaviour of JD.xslt

Subject: Re: [xsl] (possible) strange behaviour of JD.xslt
From: "Christopher R. Maden" <crism@xxxxxxxxx>
Date: Thu, 08 Nov 2001 23:26:30 -0800
Hash: SHA1

At 09:17 7-11-2001, =?us-ascii?B?IlJ1YuluIE1hcnTtbmV6Ig==?= wrote:
>Does anyone know if the XSLT specification or something say that <xsl:when>
>must follow <xsl:choose> without whitespaces between them when
>xml:space="preserve" is used, or is this a bug of JD.xslt?

As many have noted, the spec is ambiguous on this.

I think this is a symptom of SGML-itis among some of the XSL WG (myself 
included).  In element content, whitespace is always stripped, and 
xsl:choose has element content.  Of course, not only does element content 
never exist if there's no DTD, but a DTD can't even exist for XSL in 
general, so this assumption was entirely unwarranted.  I would file a bug 
report against JD.xslt anyway - it's not out of conformance with the spec, 
but there are *lots* of stylesheets that do this, and it's certainly not 
*wrong* to ignore the whitespace.

This is a bit of a problem for SGML-heads - just last week, I was startled 
when the element nodes from an <xsl:for-each> were all getting even values 
for position().  I had to explicitly say <xsl:for-each select="*"> to get 
what I wanted. d-:

- -- 
Christopher R. Maden, Principal Consultant, HMM Consulting Int'l, Inc.
DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training
<URL: > <URL: >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4  5DFC AC52 F825 AFEC 58DA
Version: PGP Personal Privacy 6.5.8


 XSL-List info and archive:

Current Thread