![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - Re: Multilingual support in generated XML (RSS) >Thread Next - Re: Multilingual support in generated XML (RSS) Re: Multilingual support in generated XML (RSS)To: NULL Date: 11/2/2006 12:45:00 PM It does bend your mind INDEED! So let me see if I figured it out: The HTML (client) pages are set as UTF-8 (charset = UTF-8). But the server's codepage was set as 1255 (I printed the Response.CodePage, without setting it previously to 65001, and received 1255 - the Hebrew ANSI codepage). So the data arrived from the client as UTF-8, treated with the wrong codepage, and inserted corrupted into the DB, which expected valid UTF-8. On the other way around - since the same corrupted conversions were made, the ASP page displayed the data correctly, but the XML, which expected valid UTF-8, showed the corruption. So to sum it up - if I set all the pages with codepage 65001 - it should fix everything (as it did, when I tested it), and all will have a valid UTF-8 - the client, server, DB and XML. One more question left - I have lots of corrupted UTF-8 strings in the DB now. Is there a way to perform some kind of conversion to fix it? Thanks, Gabi. | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||||
|
