Re: mod_plsql / dad / character set problem

From: Laurenz Albe <invite_at_spam.to.invalid>
Date: 18 Jul 2006 12:16:17 GMT
Message-ID: <1153224973.959151@proxy.dienste.wien.at>

Jeremy <jeremy0505_at_gmail.com> wrote:

>> You have a problem then. You cannot store a Euro character in such a
>> database.

>
> You can and we have.

Sorry, but you have not.
You have stored 0x80 in the database, and that is not a Euro if the character set is WE8ISO8859P1, which you told me it is.

If I seem to be nitpicking here, it is because NLS problems are so tricky. Bear with me.

0x80 only becomes a Euro character in the correct environment, which in this case is WE8MSWIN1252. In WE8ISO8859P1 and WE8ISO8859P15 it is either undefined or means a control character.

>> You probably have a Windows client and your NLS_LANG is (incorrectly) set
>> to TERRITORY_LANGUAGE.WE8ISO8859P1 (correct would be WE8MSWIN1252).

>
> No. The "client" is mod_plsql running on Solaris. And the DAD is defined
> (as stated previously) as PlsqlNLSLanguage AMERICAN_AMERICA.UTF8 or
> AMERICAN_AMERICA.WE8ISO8859P1.
Sorry, I missed out on that one.

I guessed that because 0x80 means Euro in Windows 1252 and in no other codepage I know, certainly not in UTF-8 or ISO 8859-x.

>> The easiest solution would be to convert the database character set
>> to WE8MSWIN1252 without changing the data in the database.

>
> Why would I want to set the DB char set to something windows-oriented?

Well, I don't know, I hade been under the impression that the data in your database are encoded in Windows 1252. If that is not the case, I'm wrong.

But if it is true, wouldn't it be the correct solution to tell the database that it contains Windows 1252 strings and not ISO 8859-1 strings, as it currently believes?

Yours,
Laurenz Albe Received on Tue Jul 18 2006 - 07:16:17 CDT