| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Arulappan, Arul Shaji" <arul(at)fast(dot)au(dot)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal - Support for National Characters functionality |
| Date: | 2013-07-15 06:36:58 |
| Message-ID: | CAM3SWZQN2N3V-DhOBEKzHV4vDzLmAatfhh=FtKMq5HqSASTc-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 15, 2013 at 4:37 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Jul 5, 2013 at 2:35 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> Yes, what I know almost all use utf8 without problems. Long time I didn't
>> see any request for multi encoding support.
>
> Well, not *everything* can be represented as UTF-8; I think this is
> particularly an issue with Asian languages.
What cannot be represented as UTF-8? UTF-8 can represent every
character in the Unicode character set, whereas UTF-16 can encode
characters 0 to 0x10FFFF.
Does support for alternative multi-byte encodings have something to do
with the Han unification controversy? I don't know terribly much about
this, so apologies if that's just wrong.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Chalke | 2013-07-15 06:59:28 | Re: Regex pattern with shorter back reference does NOT work as expected |
| Previous Message | Michael Paquier | 2013-07-15 05:42:23 | Re: Changing recovery.conf parameters into GUCs |