From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, <phppgadmin-devel(at)lists(dot)sourceforge(dot)net> |
Subject: | Re: UTF-8 encoding question regarding PhpPgAdmin development |
Date: | 2003-01-07 22:13:59 |
Message-ID: | 200301072313.59980.jm.poure@freesurf.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Peter,
Thank you very much for your answers. It rings a bell.
> Finally, when you display East Asian characters you will
> have a font problem because the Chinese, Japanese, and Korean characters
> are mapped to the same range in Unicode but you are supposed to use
> country-specific glyphs.
Do you mean that glyph hexaX will display differently in UTF-8 and EUC_JP? If
it is really the case, we cannot use UTF-8.
> Round-trip conversion is not safely possible, so if your tool provides a
> read/edit/write tool then you will have problems.
Maybe we could use "getdatabaseencoding()" to determine the dabase encoding
and generate HTML pages with the corresponding headers. Example: Latin1
database <-> ISOS-8859-1 headers.
The problem is that PhpPgAdmin interface needs to be localized in several
languages, not related to database encoding. Example: EUC_JP interface and
Latin1 databases.
Maybe a solution would be to use the ISO 10646 notation for PhpPgAdmin
interface localization: "&#XH;", where H is a hexadecimal number.
Cheers,
Jean-MIchel POURE
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-01-07 22:14:03 | Re: Next platform query: Alphaservers under VMS? |
Previous Message | mlw | 2003-01-07 22:10:17 | PostgreSQL site, put up or shut up? |