From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
---|---|
To: | "Dennis Bjorklund" <db(at)zigo(dot)dhs(dot)org> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Patches" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: UNICODE characters above 0x10000 |
Date: | 2004-08-07 07:59:39 |
Message-ID: | 5066E5A966339E42AA04BA10BA706AE56089@rodrick.geeknet.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
This should do it.
Regards,
John Hansen
-----Original Message-----
From: Dennis Bjorklund [mailto:db(at)zigo(dot)dhs(dot)org]
Sent: Saturday, August 07, 2004 5:02 PM
To: Tom Lane
Cc: John Hansen; Hackers; Patches
Subject: Re: [HACKERS] UNICODE characters above 0x10000
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
Attachment | Content-Type | Size |
---|---|---|
wchar.c.patch | application/octet-stream | 2.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-08-07 10:02:33 | Re: pg_dump: could not parse ACL list |
Previous Message | Dennis Bjorklund | 2004-08-07 07:01:37 | Re: UNICODE characters above 0x10000 |
From | Date | Subject | |
---|---|---|---|
Next Message | markir | 2004-08-07 09:46:08 | PITR on Win32 - Archive and Restore Command Strings |
Previous Message | Stefan Kaltenbrunner | 2004-08-07 07:56:55 | psql - missing tab-completion support for tablespaces |