| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | fortin(dot)christian(at)videotron(dot)ca, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-translators(at)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re : Re: [HACKERS] UTF-32 support in PostgreSQL ? |
| Date: | 2015-10-27 01:27:52 |
| Message-ID: | CAM3SWZR-xmOGEJOE9XrjWmgXQt4afBR2uihW8BdSoWozLERtdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-translators |
On Mon, Oct 26, 2015 at 6:20 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> UTF-16 is like UCS-2, but adds UTF-8-like escape sequences to handle
> the high 16 bits of the 32-bit Unicode space. It combines the worst
> features of UTF-8 and UCS-2. UTF-16 is the character set used by
> Windows APIs and the ICU library.
ICU can be built to support UTF-8 natively. UTF-8 support has been at
the same level as UTF-16 support for some time now.
"English language privilege" on your part (as you put it) could be
argued if the OP was arguing for UTF-16, but since he argued for
UTF-32, I don't see how that could possibly apply. UTF-16 is slightly
preferable for storing East Asian text, but UTF-32 is a niche encoding
worldwide.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2015-10-27 01:54:39 | Re: Multi-tenancy with RLS |
| Previous Message | Craig Ringer | 2015-10-27 01:20:15 | Re: Re : Re: [HACKERS] UTF-32 support in PostgreSQL ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | fortin.christian | 2015-10-29 01:44:09 | Re : Re: Re : Re: UTF-32 support in PostgreSQL ? |
| Previous Message | Craig Ringer | 2015-10-27 01:20:15 | Re: Re : Re: [HACKERS] UTF-32 support in PostgreSQL ? |