Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / General / January 2005

Tip: Looking for answers? Try searching our database.

Problem - Extended characters print as question marks

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Walt - 28 Jan 2005 21:04 GMT
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.

Signature

//-Walt
//
//

Jon Skeet [C# MVP] - 29 Jan 2005 14:39 GMT
> 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
[quoted text clipped - 4 lines]
> 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
[quoted text clipped - 3 lines]
>
> 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/debuggingunicode.html for a bit
of advice on this kind of thing.

Signature

Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.