Re: [xsl] MSXML / NBSP problem and resolution

[David Carlisle <davidc@xxxxxxxxx>]

> First of all, where did you find that transformNode returns a BSTR? 

the eindows help file that comes with the msxml sdk (a  separate downlad
for msxml3, but part of msxml4 download, as I recall)


> The original problem was how to get an nbsp / #160 or equivalent into 
> the output, in order to make a table render correctly.  (<td/> or <td> 
> </td> renders differently than <td>&#160;</td>.)

well that's easy: just put <td>&#160;</td> and it will work in any
encoding, so long as you don't confuse IE by telling it the file is in
an encoding that it isn't by forcing a latin 1 meta tag when the file is
in utf16. (or having your server specify that the file is in latin1
which is the default html encoding for text/html, I think)

But me I'm not really a microsoft person

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

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