RE: [xsl] Character 150 withs Windows-1252 output

Subject: RE: [xsl] Character 150 withs Windows-1252 output
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Fri, 21 Apr 2006 11:41:44 +0100
> Why is it that #150 gets escaped when using Windows-1252 
> output encoding when it should contain that character?

Because there is no character in the Windows-1252 character set that
corresponds to the Unicode character with codepoint 150.

Michael Kay
http://www.saxonica.com/

Current Thread