Re: [xsl] MSXML / NBSP problem and resolution

Subject: Re: [xsl] MSXML / NBSP problem and resolution
From: Mike Brown <mike@xxxxxxxx>
Date: Thu, 7 Nov 2002 15:49:22 -0700 (MST)
Michael H. Semcheski wrote:
> That was the original problem though, for one reason or another, it was 
> showing up as a ?

"?" usually indicates that you had a Unicode character that could not be
represented in whatever encoding was being used to encode the string as bytes.  

It also indicates that this substitution occurred at a point when it was no
longer known that the string contained markup (if it was known that it was XML
or HTML, then the unencodable character would've been replaced with &#160; or
&nbsp;).

Based on your other messages, I'd say this transcoding is happening when you
get a UTF-16 string from the XSLT processor and are converting it to
iso-8859-1 for output.

You need to stop getting that UTF-16 string in the first place, because the
no-break space character in there is apparently going to be directly encoded
as 0x00A0, byte order notwithstanding... not escaped as &nbsp; or &#160;.

   - Mike
____________________________________________________________________________
  mike j. brown                   |  xml/xslt: http://skew.org/xml/
  denver/boulder, colorado, usa   |  resume: http://skew.org/~mike/resume/

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


Current Thread