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

From Dennis Bjorklund
Subject Re: UNICODE characters above 0x10000
Date
Msg-id Pine.LNX.4.44.0408070851550.9559-100000@zigo.dhs.org
Whole thread Raw
In response to Re: UNICODE characters above 0x10000  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 7 Aug 2004, Tom Lane wrote:

> question at hand is whether we can support 32-bit characters or not ---
> and if not, what's the next bug to fix?

True, and that's hard to just give an answer to. One could do some simple
testing, make sure regexps work and then treat anything else that might
not work, as bugs to be fixed later on when found.

The alternative is to inspect all code paths that involve strings, not fun
at all :-)

My previous mail talked about utf-8 translation. Not all characters
possible to form using utf-8 are assigned by the unicode org. However,
the part that interprets the unicode strings are in the os so different
os'es can give different results. So I think pg should just accept even 6
byte utf-8 sequences even if some characters are not currently assigned.

--
/Dennis Björklund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: UNICODE characters above 0x10000
Next
From: "John Hansen"
Date:
Subject: Re: UNICODE characters above 0x10000