bd@a... (Bill Davis) wrote in message news:<b2b77655.0408051040.78aba5f5@p...>...
> 
> I get the following from msxsl.exe
> 
> prompt>msxsl vvsimp.xml -pi
>  < h t m l >
>  < b o d y >
> 
>                          p o s i t i o n :   2
>  < / b o d y >
>  < / h t m l >
> 
> but if I open vvsimp.xml with IE the page contains 
> 
> position: 1
> 
> (which is correct)
> 
> Given that I have up to date versions of the msxml parser (AFAIK) and
> that msxsl.exe is advertised to be a shell around the same XML engine
> that IE uses I see these results as a real head-scratcher.
> 
> (Boiled down from the more complex transformation where I originally
> experience this.)
> 
> I hope its me. Any ideas or comments are welcome.
> 
> Thanks

It is me. Looks like using the -xw switch with msxsl gets rid of the
"newline" text node in the XML file (which is seen as the first node
causing the first element to be seen as position=2). Perusal of other
entries in this group led me to this explanation. Also recognize that
use of normalize-text or a less general "apply-templates" would have
eliminated this discrepancy (this info also from this group)

I assume IE does equivalent of "msxsl -xw" by default.

Thanks to all for making this a great resource.