| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | fortin(dot)christian(at)videotron(dot)ca, pgsql-translators(at)postgresql(dot)org |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] UTF-32 support in PostgreSQL ? |
| Date: | 2015-10-26 20:51:13 |
| Message-ID: | 562E9241.1080507@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-translators |
On 10/23/2015 11:29 PM, fortin(dot)christian(at)videotron(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2015-10-26 21:02:17 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Peter Eisentraut | 2015-10-26 20:28:28 | Re: Patch (2): Implement failover on libpq connect level. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | fortin.christian | 2015-10-26 21:39:44 | Re : Re: [HACKERS] UTF-32 support in PostgreSQL ? |
| Previous Message | Tom Lane | 2015-10-26 18:11:56 | Re: [HACKERS] UTF-32 support in PostgreSQL ? |