On Mon, Oct 26, 2015 at 6:20 PM, Craig Ringer <cr...@2ndquadrant.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
