Re: Special Characters Created on a UNIX system with HP Terminal on US7ASCII

From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Fri, 20 Jul 2007 15:15:41 +0200
Message-ID: <f7qchm$c1m$1@news1.zwoll1.ov.home.nl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin T. wrote:
> Frank van Bortel wrote:

>>
>> What would the right thing be then? DB char set = server NLS settings =
>> client NLS settings? Just as dangerous and wrong.
>>

>
> Sorry. You lost me there.
> "What would the right thing be?" Of course USING the char set you tell
> the DB you are using.
> If they (OP) tell the DB they use US7ASCII and then go and store
> WE8ISO8859P1 in it, it is certainly not the right thing.

As I stated: just as dangerous, just as wrong.

It works flawlessly - so what's the problem? Your clients should be US7ASCII?!? Nope - they should be what you use: Windows clients in this part of the world are WE8MSWIN1252.

There's a very nice Metalink document on national character sets, and the use (or abuse) of NLS settings. DB = Server NLS = Client NLS is listed as a no-no (though not a "hard" one)
- --
Regards,
Frank van Bortel

Top-posting is one way to shut me up...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFGoLV9Lw8L4IAs830RAnIYAJ4s/M1fW1U/uCKSSbplaZ5G+TDlvACcCOfW ILcZrSHfDhad2gZsGWHyJho=
=7FaN
-----END PGP SIGNATURE----- Received on Fri Jul 20 2007 - 08:15:41 CDT