Cart
[Home] [By Thread] [By Date] [Recent Entries]
> Oddly enough, Despite the fact that this behaviour deviates from what > XML/DOM recommends, I have had many users actually _thank_ us for > behaving this way. I can believe that it optimises many uses of XML where white space is merely indentation so I don't object too much to it in msxml (although the fact that white space stripping is on by default in msxml is just about the number one source of incompatibility between XSLT systems. When on xsl-list a user says position() returns 1,2,3 on one system and 2,4,6 on another, You can always reliably reply that the first system is MSXML, and it's thrown away white space, and every other XSLT system will count it. Looking from an xsl-list perspective I'd say it has caused far more confusion than any optimisation was worth. But for IE, which is primarily a document browser, white space stripping by default is just simply awful. White spaces in documents tend to be between words. So even though I would expect that msxml itself won't change, I strongly believe that IE should use msxml with preservewhitespace set true. You'll _have_ to do that anyway if you ever want to support XHTML (or let anyone else support XHTML via a stylesheet). David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
|
