[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: MSXML / NBSP problem and resolution
This makes sense so far... If you call msxml so that it produces a dom or similar in memory representation then it always uses utf16 and ignores the requested output encoding. If you ask it to output to a file or string then it will use the encoding you request if it is supported on your platform. The way do a transformation in MSXML with ASP: const XSL = "structure.xsl" const XML = "data.xml" Set xmldoc = Server.CreateObject("MSXML2.DOMDocument.3.0") Set xsldoc = Server.CreateObject("MSXML2.DOMDocument.3.0") xmldoc.Load Server.MapPath(XML) xsldoc.Load Server.MapPath(XSL) strOutput = xmldoc.transformNode(xsldoc) response.write strOutput So what you are saying makes sense except that the transformNode returns a string, not an XML document or node set, so the encoding should be what I requested and not encoding of the internal DOM. i.e., I still don't understand why it is adding that meta tag into the output. (though there is a lot more light on the subject now.) Mike XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|