From: Andres Freund <andres@anarazel.de>
To: fortin.christian@videotron.ca
Cc: pgsql-translators@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] UTF-32 support in PostgreSQL ?
Date: Mon, 26 Oct 2015 19:09:14 +0100
Message-ID: <20151026180914.GG620@awork2.anarazel.de> (raw)
In-Reply-To: <7310a455c4445.562ac2f1@videotron.ca>
References: <7310b292c0558.562afaab@videotron.ca>
<7310dc30c2b71.562afae8@videotron.ca>
<7390a359c6c9c.562afb25@videotron.ca>
<7310a455c4445.562ac2f1@videotron.ca>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-translators>
On 2015-10-23 23:29:53 -0400, fortin.christian@videotron.ca wrote:
> Is PostgreSQL support UNICODE UTF-32 characters ?
No.
> If not, I think it's a must to be internationnal.
Why? I think Unicode support is a must, but I don't see why utf-32
support is. Postgres supports UTF-8, and I haven't heard any convincing
arguments why that's not sufficient.
Andres
--
Sent via pgsql-translators mailing list (pgsql-translators@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-translators
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-translators@postgresql.org
Cc: andres@anarazel.de, fortin.christian@videotron.ca, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] UTF-32 support in PostgreSQL ?
In-Reply-To: <20151026180914.GG620@awork2.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox