From: Andrew Dunstan <andrew@dunslane.net>
To: fortin.christian@videotron.ca
To: pgsql-translators@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] UTF-32 support in PostgreSQL ?
Date: Mon, 26 Oct 2015 16:51:13 -0400
Message-ID: <562E9241.1080507@dunslane.net> (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 10/23/2015 11:29 PM, fortin.christian@videotron.ca wrote:
> Is PostgreSQL support UNICODE UTF-32 characters ?
>
> If not, I think it's a must to be internationnal.
>
> To help you in this task, you could use this UTF-32 editor:
>
> https://wxmedit.github.io/downloads.html
>
> thanks.
Do you mean data stored as UTF-32, or source code in UTF-32, or
translation files as UTF-32?
For data, UTF-32 does not meet our requirements for server side encoding
(as well as being horribly inefficient space-wise).
cheers
andrew
--
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: andrew@dunslane.net, fortin.christian@videotron.ca, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] UTF-32 support in PostgreSQL ?
In-Reply-To: <562E9241.1080507@dunslane.net>
* 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