Subject: Re: [HACKERS] UTF-32 support in PostgreSQL ?
To: fortin.christian@videotron.ca, pgsql-translators@postgresql.org
References: <7310b292c0558.562afaab@videotron.ca>
 <7310dc30c2b71.562afae8@videotron.ca> <7390a359c6c9c.562afb25@videotron.ca>
 <7310a455c4445.562ac2f1@videotron.ca>
Cc: pgsql-hackers@postgresql.org
From: Andrew Dunstan <andrew@dunslane.net>
Message-ID: <562E9241.1080507@dunslane.net>
Date: Mon, 26 Oct 2015 16:51:13 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <7310a455c4445.562ac2f1@videotron.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-translators-owner@postgresql.org


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