From: fortin.christian@videotron.ca
To: Andrew Dunstan <andrew@dunslane.net>
To: pgsql-translators@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re : Re: [HACKERS] UTF-32 support in PostgreSQL ?
Date: Mon, 26 Oct 2015 17:39:44 -0400
Message-ID: <74309713d4d45.562e6560@videotron.ca> (raw)
In-Reply-To: <7460e6e6d633b.562e9d77@videotron.ca>
References: <7310b292c0558.562afaab@videotron.ca>
<7310dc30c2b71.562afae8@videotron.ca>
<7390a359c6c9c.562afb25@videotron.ca>
<7310a455c4445.562ac2f1@videotron.ca>
<562E9241.1080507@dunslane.net>
<73f0e719d0e30.562e9c08@videotron.ca>
<7440ac47d28b0.562e9c45@videotron.ca>
<7430acc9d1847.562e9c82@videotron.ca>
<7270ae0fd7bf8.562e9cbf@videotron.ca>
<73a0e3fdd5f4c.562e9cfc@videotron.ca>
<7310adbfd20ec.562e9d3a@videotron.ca>
<7460e6e6d633b.562e9d77@videotron.ca>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-translators>
----Do you mean data stored as UTF-32, or source code in UTF-32, or translation files as UTF-32?
I mean for ALL, data stored, source code, and translation files.
For source code, I think then GCC must support UTF-32 before.
I sent an e-mail to Oracle to see what they tink about this huge idea.
Well, I know it's not efficient space wise, but this in the only way that we can deploye worldwide.
I think it must be add to the next version of the SQL languages.
Le 26/10/15, Andrew Dunstan <andrew@dunslane.net> a écrit :
>
>
> 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
>
>
>
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: fortin.christian@videotron.ca, andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: Re : Re: [HACKERS] UTF-32 support in PostgreSQL ?
In-Reply-To: <74309713d4d45.562e6560@videotron.ca>
* 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