RE: microsoft latest, bug with extension elements?

["Julian Reschke" <julian.reschke@xxxxxx>]

> From: owner-xsl-list@xxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of Mike Brown
> Sent: Monday, July 31, 2000 8:45 PM
> To: xsl-list@xxxxxxxxxxxxxxxx
> Subject: Re: microsoft latest, bug with extension elements?
>
> If I am interpreting this correctly, then this is in violation of
> http://www.w3.org/TR/xslt#strip, which says
>
> "After the tree for a source document or stylesheet document has been
> constructed, but before it is otherwise processed by XSLT, some text nodes
> are stripped. A text node is never stripped unless it contains only
> whitespace characters. Stripping the text node removes the text node from
> the tree. The stripping process takes as input a set of element names for
> which whitespace must be preserved.
>
>  [...]
>
> A text node is preserved if any of the following apply:
>
> The element name of the parent of the text node is in the set of
> whitespace-preserving element names.
>
>  [...]
>
> For stylesheets, the set of whitespace-preserving element names
> consists of
> just xsl:text."
>
> So text node children of xsl:text elements must not be stripped
> even if they
> are nothing but whitespace characters.

Yes, but my understanding is that the user (== programmer) can force MSXML
not to strip anything by setting it up correctly before loading the document
(although I'd say this should be the default behaviour).

Julian



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list