[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] MSXML / NBSP problem and resolution

---

---

This is getting off of the xsl topic, so I broke it from the list, but I had this question:
First of all, where did you find that transformNode returns a BSTR? I've been looking up and down msdn (though its a big site, and its easy to miss things). All I saw was that transformNode returns a string.

Second, I am guessing you meant transformNodeToObject in the second paragraph below.

transformNode produces a microsoft BSTR string thingy, which is _always_
UTF16 encoded as the BSTR type doesn't support any other

encoding.If you used transformNode you could specify a string or a stream
as the output destination and then the XSLT serialiser will be used and
the hints in xsl:output will be used.

Do you know of a way to make this work?
(i.e.) Take an xml document, an xsl document, output the transformation using the encoding hinted at in the output method, to the browser, and perhaps also to a local file?

The question is, given that the XSLT system inserted a declaration taht
it was utf16, and it was utf16, and you said IE6 detected it as utf16,
what was the original problem, I don't think I noticed the start of this
thread?

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>.)


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

---