Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: A question about NLS Language settings

Re: A question about NLS Language settings

From: Yechiel Adar <>
Date: Mon, 23 May 2005 09:44:44 +0200
Message-ID: <006201c55f6b$4990e860$e300a8c0@user12344>

We were using the same method to write and read Hebrew letters. The database and the client both had: we8iso8859p1 so no conversion was done. Now come along. It seems that is doing internal conversion, of character strings, to utf8. During this conversion all non standard chars will become upside down question mark. You can go around it by some decleration of the character strings as oracle strings but you will probably have troubles. So my advice to you all is to use a charset that matchs what you put in. We are starting a conversion project because of this problem.

Yechiel Adar
Mehish Computer Services
----- Original Message -----
From: <>
To: <>; <> Sent: Monday, April 11, 2005 2:47 PM
Subject: RE: A question about NLS Language settings

> We ran into a problem in one of our applications where the users would
> cut text from a varchar2(2000) field, edit it in Word, then paste it.
> The problem was that certain characters like double-quotes apparently
> were "unknown" in the default characterset and where stored as upside
> down question marks. To get around this my colleague changed the
> configuration in the application server files to:
> Some questions, if this is a superset for the default then why isn't it
> the default?
> Are there any pitfalls to setting this in our .profile on our database
> server as well as our application server so that when we export/import
> (for example) we don't have problems?
> What about backups and restores - will this be an issue and should we
> set this for backups and restores.
> I can test the 3rd issue fairly easily but I would like to know if
> anyone has had experience with this issue and how they dealt with it.
> Thanks,
> Paula

Received on Mon May 23 2005 - 02:52:27 CDT

Original text of this message