Hi Andreas. UNICODE standard seems to be a correct answer.! I am examined with the standard so that it can operate it without problem. ScreenShot of the reference is a UNICODE version. http://cre-ent.skcapi.co.jp/~saito/pgadmin/lib/pgadmin3_unicode_debug1.jpg The place of the problem can't be limited. But, it seems to be WxWindows. Teach if you understood it though it tries it again tonight. Thank you in advance for your understanding. With kindest regards, Hiroshi-Saito ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding problem on D... Hiroshi Saito
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding problem... Andreas Pflug
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding pro... Hiroshi Saito
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding... Hiroshi Saito
- Re: [pgadmin-hackers] ctlSQLBox ClientEnco... Hiroshi Saito
- Re: [pgadmin-hackers] ctlSQLBox Clien... Andreas Pflug
- Re: [pgadmin-hackers] ctlSQLBox C... Andreas Pflug
- Re: [pgadmin-hackers] ctlSQLBox C... Saito
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding problem... Hiroshi Saito
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding pro... Hiroshi Saito
- Re: [pgadmin-hackers] ctlSQLBox ClientEncoding problem... Andreas Pflug