MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_plERuvvK2DHtNMU34Tx/tQ)"
From: fortin.christian@videotron.ca
To: Andrew Dunstan <andrew@dunslane.net>, pgsql-translators@postgresql.org
Cc: pgsql-hackers@postgresql.org
Message-id: <74309713d4d45.562e6560@videotron.ca>
Date: Mon, 26 Oct 2015 17:39:44 -0400
Content-language: fr
Subject: Re : Re: [HACKERS] UTF-32 support in PostgreSQL ?
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>
Precedence: bulk
Sender: pgsql-translators-owner@postgresql.org

This is a multi-part message in MIME format.

--Boundary_(ID_plERuvvK2DHtNMU34Tx/tQ)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Content-disposition: inline

=A0----Do you mean data stored as UTF-32=2C or source code in UTF-32=2C =
or translation files as UTF-32=3F

I mean for ALL=2C data stored=2C source code=2C and translation files=2E=

For source code=2C I think then GCC must support UTF-32 before=2E

I sent an e-mail to Oracle to see what they tink about this huge idea=2E=

Well=2C I know it=27s not efficient space wise=2C but this in the only w=
ay that we can deploye worldwide=2E
I think it must be add to the next version of the SQL languages=2E


Le 26/10/15=2C Andrew Dunstan  =3Candrew=40dunslane=2Enet=3E a =E9crit =3A=

=3E =

=3E =

=3E On 10/23/2015 11=3A29 PM=2C fortin=2Echristian=40videotron=2Eca wrot=
e=3A
=3E =3EIs PostgreSQL support UNICODE UTF-32 characters =3F
=3E =3E
=3E =3EIf not=2C I think it=27s a must to be internationnal=2E
=3E =3E
=3E =3ETo help you in this task=2C you could use this UTF-32 editor=3A
=3E =3E
=3E =3Ehttps=3A//wxmedit=2Egithub=2Eio/downloads=2Ehtml
=3E =3E
=3E =3Ethanks=2E
=3E =

=3E =

=3E =

=3E Do you mean data stored as UTF-32=2C or source code in UTF-32=2C or =
translation files as UTF-32=3F
=3E =

=3E For data=2C UTF-32 does not meet our requirements for server side en=
coding (as well as being horribly inefficient space-wise)=2E
=3E =

=3E cheers
=3E =

=3E andrew
=3E =

=3E =

=3E 

--Boundary_(ID_plERuvvK2DHtNMU34Tx/tQ)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Content-disposition: inline

=A0----Do you mean data stored as UTF-32=2C or source code in UTF-32=2C =
or translation files as UTF-32=3F=3Cbr /=3E=3Cbr /=3EI mean for ALL=2C d=
ata stored=2C source code=2C and translation files=2E=3Cbr /=3EFor sourc=
e code=2C I think then GCC must support UTF-32 before=2E=3Cbr /=3E=3Cbr =
/=3EI sent an e-mail to Oracle to see what they tink about this huge ide=
a=2E=3Cbr /=3EWell=2C I know it=27s not efficient space wise=2C but this=
 in the only way that we can deploye worldwide=2E=3Cbr /=3EI think it mu=
st be add to the next version of the SQL languages=2E=3Cbr /=3E=3Cbr /=3E=
=3Cbr /=3E=3Cspan=3ELe 26/10/15=2C =3Cb class=3D=22name=22=3EAndrew Duns=
tan =3C/b=3E =26lt=3Bandrew=40dunslane=2Enet=26gt=3B a =E9crit =3A=3C/sp=
an=3E=3Cblockquote cite=3D=22mid=3A562E9241=2E1080507=40dunslane=2Enet=22=
 class=3D=22iwcQuote=22 style=3D=22border-left=3A 1px solid =2300F=3B pa=
dding-left=3A 13px=3B margin-left=3A 0=3B=22 type=3D=22cite=22=3E=3Cdiv =
class=3D=22mimepart text plain=22=3E=3Cbr /=3E=3Cbr /=3EOn 10/23/2015 11=
=3A29 PM=2C fortin=2Echristian=40videotron=2Eca wrote=3A=3Cbr /=3E=26gt=3B=
Is PostgreSQL support UNICODE=A0 UTF-32 characters =3F=3Cbr /=3E=26gt=3B=
=3Cbr /=3E=26gt=3BIf not=2C I think it=27s a must to be internationnal=2E=
=3Cbr /=3E=26gt=3B=3Cbr /=3E=26gt=3BTo help you in this task=2C you coul=
d use this UTF-32 editor=3A=3Cbr /=3E=26gt=3B=3Cbr /=3E=26gt=3B=3Ca href=
=3D=22https=3A//wxmedit=2Egithub=2Eio/downloads=2Ehtml=22 target=3D=22l=22=
=3Ehttps=3A//wxmedit=2Egithub=2Eio/downloads=2Ehtml=3C/a=3E=3Cbr /=3E=26=
gt=3B=3Cbr /=3E=26gt=3Bthanks=2E=3Cbr /=3E=3Cbr /=3E=3Cbr /=3E=3Cbr /=3E=
Do you mean data stored as UTF-32=2C or source code in UTF-32=2C or tran=
slation files as UTF-32=3F=3Cbr /=3E=3Cbr /=3EFor data=2C UTF-32 does no=
t meet our requirements for server side encoding (as well as being horri=
bly inefficient space-wise)=2E=3Cbr /=3E=3Cbr /=3Echeers=3Cbr /=3E=3Cbr =
/=3Eandrew=3Cbr /=3E=3Cbr /=3E=3C/div=3E=3C/blockquote=3E

--Boundary_(ID_plERuvvK2DHtNMU34Tx/tQ)--