Skip site navigation (1) Skip section navigation (2)

Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese

From: Gordon Luk <gordon(at)gforce(dot)ods(dot)org>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese
Date: 2002-06-27 08:06:08
Message-ID: 3D1AC770.4010004@gforce.ods.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Tatsuo Ishii wrote:

>>Ok, but problem is, when i try encode with unicode, it also reject
>>me.... invalid UNICODE charater.... :-(
>>    
>>
>
>Show me the entire error message please.
>

Ok... error like this...
ERROR : Invalid UNICODE character sequence found (0xe5a672)...

the input charater also "中文字"....

>Actually PostgreSQL does support Big5. To use Big5, set the client
>encoding to Big5 and set the server(DB) encoding to EUC_TW. PostgreSQL
>will take care of the conversion between Big5 and EUC_TW.
>
>There are several ways to set the client encoding to Big5:
>
>SQL: set client_encoding to 'Big5';
>from psql: \encoding Big5
>using environment variable: export PGCLIENTENCODING=Big5 (example for bash)
>
>Hope this helps,
>--
>Tatsuo Ishii
>  
>
O... you are right, i use Pgadmin II , and type SQL by hand ... and add
the "set client_encoding to 'Big5';" before insert statement.... It
WORK!!!! Thanks...


Gordon

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-06-27 14:02:37
Subject: Re: weird strncmp bug while executing trigger?
Previous:From: Tatsuo IshiiDate: 2002-06-27 07:01:21
Subject: Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group