Re: [xsl] MSXML / NBSP problem and resolution

[David Carlisle <davidc@xxxxxxxxx>]

> If the output is UTF-16, and the only way to change this is with 
> Response.Charset (lets consider this inelegant, more of a bandaid than a 
> solution), maybe the correct approach is a bit off the beaten path.

Given that most modern browsers are OK with utf16 anyway it's not clear
that you really need to change this, otherwise if you use
transformnodetoobject you can generate it in something other than utf16
in the first place.


> A certain character 
> (non-breaking space) was needed to get the page rendered correctly when 
> encoded in ISO-8859-1.  Is there a similar UTF-16 character anyone knows 

This sounds highly suspicous, by use of character references you can
access the full unicode character set in XML and HTML whatever the
encoding of the file. In utf16 you can access all unicode characters as
character data there are not really any "UTF-16 characters" as unlike
latin1 or aski utf16 does not encode a subset of unicode.

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