Jean-Michel POURE writes:
> > 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
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.
Jean-Michel POURE writes:
> - 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.
It should be possible. If not, it's a bug.
> - Some letters, like the euro sign, do not belong to Latin1
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 so
