[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Character 150 withs Windows-1252 output

Subject: RE: Character 150 withs Windows-1252 output
From: "XSLList" <XSLList@xxxxxxxxxx>
Date: Thu, 20 Apr 2006 19:00:02 +0100
utf 16 windows 1252

If you are using MSXML (I'm glad to hear we are not the only MSXML users)
the encoding will be controlled by the ASP/VB or whatever programming
language you are using.

MSXML seems to ignore <xsl:output encoding=" Windows-1252" method="xml"/>

We find we have to set the encoding in the processing code [Response.Charset
= "ISO-8859-1"] and then for good measure replace the UTF-16 declaration at
the top of any MSXL parsed result [Response.Write Replace(objXSLProc.output,
"UTF-16", " Windows-1252")]

Messy but until MSXML allows for setting the encoding it seems the only

P.S we actually use ISO-8859-15 as you can't assume everyone uses windows ;)

William Charlton
The yMonda team
yMonda Limited
w: www.ymonda.net

Andrew Welch said

Why is it that #150 gets escaped when using Windows-1252 output
encoding when it should contain that character?

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.