<? Xml version = "1.0" encoding = "UTF-8"?>
<Weather ver = "2.0">
<Head> [...]
</Head>
<Loc id = "CHXX0101"> [...]
</Loc>
<Cc> [...]
</Cc>
<Dayf>
<Lsup> 10/28/06 AM Local Time </lsup>
<Day d = "0" t = "Saturday" dt = "Oct 28"> [...]
</Day>
<Day d = "1" t = "Sunday" dt = "Oct 29"> [...]
</Day>
</Dayf>
</Weather>
XSLT file format (content omitted ):
<? Xml version = "1.0" encoding = "UTF-8"?>
<Xsl: stylesheet version = "1.0" xmlns: xsl = "http://www.w3.org/1999/XSL/Transform">
<Xsl: output method = "xml" version = "1.0" encoding = "UTF-8" indent = "yes"/>
<Xsl: template match = "/"> [...]
</Xsl: stylesheet>
The conversion code I started using ASP + export cirpt:
// ========= Output type and stream encoding ==================================== =
Response. ContentType = "application/vnd. google-earth.kml + xml ";
Response. CharSet = "UTF-8 ";
// =======Obtain and load the remote XML file ================================
Var oXHy = Server. CreateObject ("MSXML2.XMLHTTP ");
Var url = http://www.dnxh.cn/ge/CHXX0101.xml;
OXHy. open ("GET", url, false );
OXHy. send ();
Var oXD = Server. CreateObject ("MSXML2.DOMDocument ");
OXD. loadXML (oXHy. responseText );
// ======= Load the XSL file ============================
Var xsl = Server. CreateObject ("Microsoft. XMLDOM ");
Xsl. async = false;
Xsl. load (Server. MapPath ("gew. xsl "));
// ======= File conversion ==========================
Response. Write (oXD. transformNode (xsl ));
It is reasonable to say that there should be no encoding problem, because the declaration of the encoding is declared. But something went wrong. The statement at the beginning of the output KML file is always
<? Xml version = "1.0" encoding = "UTF-16"?>
Test shows that there are no problems with the XML and XSLT source files, that is, the Problem lies in the conversion engine in ASP code, and then in RE: [xsl] Problem with Chinese (Solution) this article probably found the reason, here it is said that the engine transformNode is to generate a string, and on the win32 platform is always to process the string with a UTF-16, then we use this string to generate the KML file, then the result can only be UTF-16.
The solution is to use the transformNodeToObject engine. Replace the file conversion part with oXD. transformNodeToObject (xsl, Response ). The difference between the two methods is that the first one generates a string variable, and the other is to directly Save the converted XML data to the specified node.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
