Because MSXSL is not implementing the XSLT recommendation correctly.
Xalan's behavior is correct. There are other gotchas with text nodes in
MSXSL. Another is that text nodes on entity and CDATA section boundaries
are not merged, which is also contrary to the XSLT data model. There's
probably some FAQ somewhere that explains them all.
Dave
"Scott Moore"
<puffandtoot@cox To: <[EMAIL PROTECTED]>
.net> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: Bug in Xalan 2.4.0 with
position()
09/20/2002 01:33
PM
Please respond
to xalan-dev
Okay, nevermind. I just saw the answer to my bugzilla post.
Now my question is - why does MSXML 4.0 eliminate element whitespace by
default but Xalan does not? Which is the correct behavior (if there is
one).
Thanks,
Scott
P.S. Sorry about the bogus bug report.
Re: Bug in Xalan 2.4.0 with position()
David N Bertoni/Cambridge/IBM Fri, 20 Sep 2002 13:55:05 -0700
- Bug in Xalan 2.4.0 with position() Scott Moore
- Re: Bug in Xalan 2.4.0 with position() Scott Moore
- Re: Bug in Xalan 2.4.0 with positio... Joseph Kesselman
- Re: Bug in Xalan 2.4.0 with positio... Scott Moore
- Re: Bug in Xalan 2.4.0 with pos... Scott Moore
- Re: Bug in Xalan 2.4.0 with... Joseph Kesselman
- Re: Bug in Xalan 2.4.0 with pos... Joseph Kesselman
- Re: Bug in Xalan 2.4.0 with... Scott Moore
- RE: Bug in Xalan 2.4.0 with position() Voytenko, Dimitry
- RE: Bug in Xalan 2.4.0 with positio... Gary L Peskin
- Re: Bug in Xalan 2.4.0 with position() David N Bertoni/Cambridge/IBM
- Re: Bug in Xalan 2.4.0 with position() David N Bertoni/Cambridge/IBM
- RE: Bug in Xalan 2.4.0 with position() Voytenko, Dimitry
- Re: Bug in Xalan 2.4.0 with positio... John Gentilin
