Re: Converting from WE8MSWIN1252 to WE8ISO8859P1

On Sun, 18 Apr 2004 13:12:18 +0200, Sybrand Bakker <gooiditweg_at_sybrandb.verwijderdit.demon.nl> wrote:

>On Sun, 18 Apr 2004 10:41:17 +0200, Marc Blum <blum_at_marcblum.de>
>wrote:
>
>>NLS_LANG is dictated by the setting of your client OS! You can't toggle
>>NLS_LANG. You have no choice! For example: my PC runs XP with german settings.
>>Therefore NLS_LANG must be GERMAN_GERMANY.WE8MSWIN1252. Nothing other!
>
>I don't think that is true. I've seen it many times set on Dutch
>systems to American_America.<etc> without problem.

Dear Sybrand,

as long as all client machines have the same NLS_LANG setting and the database has that characterset (the part after the dot) as DATABASE CHARACTERSET, you have a *conceptually* wrong configuration, which works without problems, because:

if and only if client charset and db charset are identical, the oracle client layer does not perform *any* characterset conversion. Not even a one-on-one mapping to ensure, that unknown codepoints are omitted. That way unknown codepoints are stored and retrieved without corruption. You may choose US7ASCII for both sides, as long as they are identical, it doesn't matter in any way.

Me too, I've seen many many oracle systems with WE8ISO8859P1 on both sides. When the client app is windows based, it's wrong wrong wrong. The only correct NLS_LANG-setting for german/dutch/british Windows is <bla>.WE8MSWIN1252.

Please check these metalink docs for clarification:

158577.1
179133.1
225938.1
 

--
Marc Blum
mailto:blumNOSPAM_at_marcblum.de
http://www.marcblum.de