Should be there?

Post #22,942 by scoenye 1/3/02 7:07:38 AM Reply	Should be there? At least, that's what this [link\|http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk30/htm/xmconcharacterencodingxmlandmsxml.asp\|MSDN entry] implies.
Post #22,953 by bbronson 1/3/02 10:11:50 AM Reply	Wonderful contradictory MSDN Thanks for the link. I got my information from here: [link\|http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q275883\|Knowledge Base Article] "MSXML supports all encodings that are supported by Microsoft Internet Explorer. Internet Explorer's support depends on which language packs are installed on the computer" It then goes on to say MSXML has native support for UTF-16. The error we are receiving is this: "System does not support the specified encoding. Line 1, Position 40 <?xml version="1.0" encoding="UTF-16"?>" We traced the process and verified it's being generated on our web server, which is a W2K Server and is running MSXML 3. So, according to one MS article (your link) I shouldn't see this error. According to another article (my link) maybe I should see it; maybe I shouldn't. I'm confused. Brian Bronson
Post #22,965 by Silverlock 1/3/02 12:08:36 PM Reply	Try these I tried a query on "UTF-16" on my copy of the MS technet knowledgebase. These links look related to your problem. [link\|http://support.microsoft.com/default.aspx?scid=kb;EN-US;q303612\|q303612] [link\|http://support.microsoft.com/default.aspx?scid=kb;EN-US;q247708\|q247708] When I visit the aquarium, the same thought keeps running through my mind; Leemmmooonnn, Buuttteerrr, MMMmmmmmm good!
Post #22,974 by bbronson 1/3/02 12:37:00 PM Reply	I had seen both of those, don't think they apply Thanks for the help. re: Q247708. We're on MSXML 3.0, so this should not apply. Besides, the first solution they offer is to convert the xml to UTF-16!!! re: Q303612. The data is coming from a SQL Server 7 database through the IIS web server to the browser. The error is happening before it gets to the browser, so this shouldn't apply. And if the path was from the browser to the server, it wouldn't have been UTF-16 as IE would have submitted it as UTF-8. Although it does point out potential future issues (no matter what unicode characters you need to enter through IE, they better exist in UTF-8). I had also checked out the link from Q303612 to Q232580 (UTF-8 and SQL Server). I passed this on to the developers as another potential issue. They haven't responded yet. My head hurts (and it's not for any fun reasons!) Brian Bronson
Post #23,021 by scoenye 1/3/02 4:38:06 PM Reply	Might this be related? The fog is pretty dense out there regarding XML, XSL and character encoding. But maybe [link\|http://groups.google.com/groups?hl=en&threadm=OJ7Za1ioAHA.1320%40tkmsftngp04&rnum=20&prev=/groups%3Fq%3DSystem%2Bdoes%2Bnot%2Bsupport%2Bthe%2Bspecified%2Bencoding%2BUTF-16%26hl%3Den%26start%3D10%26sa%3DN\|this] is related to what is happening on your end. After all, the 40th character is past the closing ">" If I read the ng's right, the 'encoding="UTF-16"' bit implies the entire XML document is UTF-16 encoded. If that's not the case, the parser will not like it.
Post #23,385 by bbronson 1/7/02 2:31:25 PM Reply	Thought so, but alas, no Looked long and hard at it with the developer, and for the first few minutes thought that was the fix. But it wasn't. We did some more digging and testing. Now I don't even think the error message we are receiving is accurate. The error is happening when we load the xml document into the xml parser via the asp code. That's failing and ultimately we receive the utf-16 not supported message. But, when we manually load a known utf-16 document, that portion works. So something is preventing the problem xml document from being loaded. The entirely-MS system is telling is it's because utf-16 is not supported, but that's not the real reason. I have to put this down a few days because we have a release coming out. Thanks for the help, Brian Bronson

Welcome to IWETHEY!