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.




Reply via email to