Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Special Characters Created on a UNIX system with HP Terminal on US7ASCII
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin T. wrote:
> Frank van Bortel wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Martin T. wrote: >>> >From the "Globalization Support Guide": >>> US7ASCII / U.S. 7-bit ASCII / US / Bits: 7 / ASCII >>> >>> So you are telling us that you used US7ASCII to store German umlauts? >>> This is just wrong. US7ASCII is just 0x00 -> 0x7F but the characters >>> you are talking about are 0x80 -> 0xFF and so cannot be correctly >>> stored in an US7ASCII character set column. >>> >> >> Simply not true - Oracle *always* stores bytes. Very dangerous >> assumption, that has cost a lot of money already. >> >> Same with the ability to "store the Euro-character in >> WE8ISO8859P1" - it works with no problem at all. >> >> Basically, because you do not store the euro symbol, >> but a code. It is up to the client to display this code >> correctly as '€'. If the client is thinking the code >> belongs to '¢' - it will display that. >> If the client does not know how to display, the convention is >> to display an inverted question mark. >>
What would the right thing be then? DB char set = server NLS settings = client NLS settings? Just as dangerous and wrong.
Top-posting is one way to shut me up...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFGn34ALw8L4IAs830RAvkQAJ9uHdiEaLtRfD4YFc6hm6knNQ7D4ACfalwN
DtvdCdzN7C2TZBDPSYUzB2M=
=L/ks
-----END PGP SIGNATURE-----
Received on Thu Jul 19 2007 - 10:06:40 CDT