Re: UTF-8 encoding question regarding PhpPgAdmin development - Mailing list pgsql-hackers

From Jean-Michel POURE
Subject Re: UTF-8 encoding question regarding PhpPgAdmin development
Date
Msg-id 200301072313.59980.jm.poure@freesurf.fr
Whole thread Raw
In response to Re: UTF-8 encoding question regarding PhpPgAdmin development  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: UTF-8 encoding question regarding PhpPgAdmin development  (Peter Eisentraut <peter_e@gmx.net>)
List 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


pgsql-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Next platform query: Alphaservers under VMS?
Next
From: mlw
Date:
Subject: Re: PostgreSQL and memory usage