From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | UTF-8 encoding question regarding PhpPgAdmin development |
Date: | 2003-01-07 13:38:39 |
Message-ID: | 200301071438.39170.jm.poure@freesurf.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear all,
We are working on PhpPgAdmin UTF-8 support. I would like to be able to view
UTF-8, ASCII and Latin1 databases in PhpPgAdmin without changing HTML header
encodings.
I guess this can be done using:
SET CLIENT_ENCODING='Unicode'
for all PhpPgAdmin connections.
My question are:
- Are some database encodings not translatable into UTF-8 using SET
CLIENT_ENCODING = 'Unicode'. It used to be the case for Latin1, but it has
been fixed now.
- Some letters, like the euro sign, do not belong to Latin1. Example: let's
say we have a Latin1 database and use SET CLIENT_ENCODING = 'Unicode'. If I
input a euro sign, does it get rejected by PostgreSQL?
- More generaly, is it safe to convert an Encoding (ex: Latin1 or Chinese
multi-byte) into UTF-8 using SET CLIENT_ENCODING? Can all multi-byte
encodings be converted into/from UTF-8 safely?
Best regards,
Jean-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Jeroen T. Vermeulen | 2003-01-07 14:21:39 | Re: Error using cursors/fetch and execute |
Previous Message | Magnus Naeslund(f) | 2003-01-07 13:29:30 | Error using cursors/fetch and execute |