Is Characterset WE8MSWIN1252 better than WE8ISO8859P15???

Hello,

We are using WE8ISO8859P15 as a default character set on 10g(Windows 2000) and AL16UTF16 as a national Character set. Although this supports Euro Symbol (IF NLS_LANG is set at client), but doesn't store following...
This character ´ (hex:B4) ascii 180. When data is entered it shows ¿ (reverse question mark).

example....
create table tempmy (Name varchar2(30));
insert into tempmy values ('D'||chr(180)||'costa');
insert into tempmy values ('O'||chr(180)||'Brian');
insert into tempmy values ('My Currency '||CHR(128));

But if same example is used when Default character set WE8MSWIN1252 (This also supports Euro symbol) and NLS Character set AL16UTF16 Then it shows proper data...

D´costa
O´Brian


Could you please guide us in this. Also is it manadatory to set NLS_LANG for Euro Symbol?

Thanks & Regards,

Shailesh

well if you need to display those characters you need the necessary character set?

Same applies for any symbol

I think you are using the wrong character:
O'Brian is normally written with a single quote Hex:27
´ is an acute accent Hex:B4

Hello,

(ISO defined) does not encode all the characters that are encoded in Microsoft created and default character set at client Character set. The other way around encodes everything that is encoded in . That means for Windows clients setup, character set is recommanded as database Character set, else users on these clients could use characters that can not be stored in the database and those characters will be replaced by something else (See above reported problem ´is stored as ¿).

Can anyone help me for NLS_LANG. Is it mandatory to set this at client if Euro symbol needs to be stored in the database.

Thanks & Regards,

Shailesh

Quote:

---

Originally posted by DaPi
I think you are using the wrong character:
O'Brian is normally written with a single quote Hex:27
´ is an acute accent Hex:B4

---

Good Lord Dapi you need to get out more.