Thanks.
UTF8 is good enough although it needs conversion between client GBK and server
side UTF8. I didn't notice that there are high risk to introduce GBK and
similar other kind of charsets into server side.
"=?ISO-8859-1?B?WGlvbmcgSGU=?=" writes:
> I just noticed that PG not support the f
"=?ISO-8859-1?B?WGlvbmcgSGU=?=" writes:
> I just noticed that PG not support the following encoding:
> /* followings are for client encoding only */
> PG_SJIS,/* Shift JIS
> (Winindows-932) */
> PG_BIG5,
I just noticed that PG not support the following encoding:
/* followings are for client encoding only */
PG_SJIS,/* Shift JIS
(Winindows-932) */
PG_BIG5,/* Big5 (Windows-950) */
PG_GBK,
