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/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--