Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Multilingual support in generated XML (RSS)

From: "BarakF" <frohlinger@-----.--->
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.



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent