Re: [PATCHES] UNICODE characters above 0x10000 - Mailing list pgsql-hackers

From Dennis Bjorklund
Subject Re: [PATCHES] UNICODE characters above 0x10000
Date
Msg-id Pine.LNX.4.44.0408071306160.9559-100000@zigo.dhs.org
Whole thread Raw
In response to Re: [PATCHES] UNICODE characters above 0x10000  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: [PATCHES] UNICODE characters above 0x10000
List pgsql-hackers
On Sat, 7 Aug 2004, Tatsuo Ishii wrote:

> More seriously, Unicode is filled with tons of confusion and
> inconsistency IMO. Remember that once Unicode adovocates said that the
> merit of Unicode was it only requires 16-bit width. Now they say they
> need surrogate pairs and 32-bit width chars...
>
> Anyway my point is if current specification of Unicode only allows
> 24-bit range, why we need to allow usage against the specification?

Whatever problems they have had in the past, the ISO 10646 defines
formally a 31-bit character set. Are you saying that applications should
reject strings that contain characters that it does not recognize?

Is there a specific reason you want to restrict it to 24 bits? In practice
it does not matter much since it's not used today, I just don't know why
you want it.

--
/Dennis Björklund


pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Re: [PATCHES] UNICODE characters above 0x10000
Next
From: strk
Date:
Subject: pg_dump and sequences (bug ?)