Re: Client Encoding
От | Hiroshi Saito |
---|---|
Тема | Re: Client Encoding |
Дата | |
Msg-id | 015f01c32f6f$da14d6e0$1f324d80@w2k обсуждение исходный текст |
Ответ на | Client Encoding ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgadmin-hackers |
Hi Dave. They are still imperfect. This binary understands SJIS-code more securely than UNICODE now. http://cre-ent.skcapi.co.jp/~saito/pgadmin/lib/pgadmin3_2003-06-10_bin.zip Of course, other encodings are understood, too. Leave it because it is input and output of the local data and it doesn't become a difficulty. With kindest regards, Hiroshi-Saito ----- Original Message ----- From: "Dave Page" <dpage@vale-housing.co.uk> To: <pgadmin-hackers@postgresql.org> Sent: Tuesday, June 10, 2003 10:43 PM Subject: [pgadmin-hackers] Client Encoding It seems we all seem to think that client_encoding should be set to UNICODE in all cases for unicode builds and SQL_ASCII for others, therefore I've backed out the previous changes and implemented this behaviour instead. Any problems, please let me know. Regards, Dave
В списке pgadmin-hackers по дате отправления: