471,328 Members | 1,723 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,328 software developers and data experts.

Problem - Extended characters print as question marks


We are using ASP.net to develop a new website. The old website uses
legacy ASP connecting to an Oracle database (9.2, W2k3, charecter set
WE8ISO8859P1). The new site connects to the same database but using
ASP.NET.

Our problem is that extended characters are printing out as question
marks. In particular, the "smart quote" characters that MS Word likes
to use are showing up as question marks.

We ran into a similar problem with the legacy ASP about a year ago and
solved it by changing the registry entry
HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOME0/NLS_LANG to
AMERICAN_AMERICA.WE8ISO8859P1 so that it matchs the character set on the
database.

Any clues how to fix it in the dot.net world?

Thanks.

--
//-Walt
//
//
Jul 21 '05 #1
1 1876
Walt <wa*********@YerBootsyahoo.com> wrote:
We are using ASP.net to develop a new website. The old website uses
legacy ASP connecting to an Oracle database (9.2, W2k3, charecter set
WE8ISO8859P1). The new site connects to the same database but using
ASP.NET.

Our problem is that extended characters are printing out as question
marks. In particular, the "smart quote" characters that MS Word likes
to use are showing up as question marks.
What are the unicode values of those characters? I can't see any curly
quotes in ISO-8859-1. (See http://www.unicode.org/charts/PDF/U0080.pdf
for the upper half of ISO-8859-1.)
We ran into a similar problem with the legacy ASP about a year ago and
solved it by changing the registry entry
HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/HOME0/NLS_LANG to
AMERICAN_AMERICA.WE8ISO8859P1 so that it matchs the character set on the
database.

Any clues how to fix it in the dot.net world?


My guess is that the database actually contains duff data (i.e. it
doesn't *really* contain "smart quote" characters) but that the same
mistake that was made when inserting characters (eg treating CP-1252 as
if it were ISO-8859-1) is being made on the way out with the old ASP
app, which would make it work.

See http://www.pobox.com/~skeet/csharp/d...ngunicode.html for a bit
of advice on this kind of thing.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too
Jul 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by barthome1 | last post: by
10 posts views Thread by Richard R Plourde | last post: by
11 posts views Thread by LucaJonny | last post: by
13 posts views Thread by ramif | last post: by
7 posts views Thread by wannymahoots | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.