Unicode Text Issues with ASP/ADO

[Oleg]

So I've got a nasty little problem with ADO in the old ASP platform. We are extending an existing web site to include a Japanese Language version. We have built a tool in C# where users can write Japanese Strings into a SQL Server Table, The table columns are Unicode and we are using the N prefix on our insert and update statements.

All of the Japanese versions of the HTML the pages emit have been set to the UTF-8 charset, and from what I can tell this is the charset that tools like Excel use to deal with most other languages. Google seems to use this charset for all languages. A lot of the data has gotten into the system via cut-n-paste from Excel files sent to us from translators in Japan. We have pasted data into our ASP.Net forms and into Enterprise Manager, We have even used DTS to load some of the data

If we read the data back from SQL through ADO.Net and inject it into the page it displays in the proper charset just fine. But when we read the data with ADO and display it in the older pages we get garbage. I have tried many things to get around this to no avail

Any ideas and suggestions would be greatly appreciated

Thanks

- Ole

[Mark Schupp]

Try adding

session.codepage=65001

to each asp page.

--
Mark Schupp
Head of Development
Integrity eLearning
[url]www.ielearning.com[/url]


"Oleg" <anonymous@discussions.microsoft.com> wrote in message
news:4F55DAA5-AC52-49BB-9A27-2DBD3BB46071@microsoft.com...

> So I've got a nasty little problem with ADO in the old ASP platform. We

are extending an existing web site to include a Japanese Language version.
We have built a tool in C# where users can write Japanese Strings into a SQL
Server Table, The table columns are Unicode and we are using the N prefix on
our insert and update statements.

>
> All of the Japanese versions of the HTML the pages emit have been set to

the UTF-8 charset, and from what I can tell this is the charset that tools
like Excel use to deal with most other languages. Google seems to use this
charset for all languages. A lot of the data has gotten into the system via
cut-n-paste from Excel files sent to us from translators in Japan. We have
pasted data into our ASP.Net forms and into Enterprise Manager, We have even
used DTS to load some of the data.

>
> If we read the data back from SQL through ADO.Net and inject it into the

page it displays in the proper charset just fine. But when we read the data
with ADO and display it in the older pages we get garbage. I have tried
many things to get around this to no avail.

>
> Any ideas and suggestions would be greatly appreciated!
>
> Thanks,
>
> - Oleg
>
>

[Oleg]

I found a solution

The ASP page you have handles text in some non-Unicode form. Set the CODEPAGE property of the page to UTF-8 ("<%@CODEPAGE=65001...>"), or do it at the Session level. Make sure the charset in the HTTP header is set to UTF-8 too.