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

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

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: gordon(at)gforce(dot)ods(dot)org
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in
Date: 2002-06-26 15:00:15
Message-ID: 20020627.000015.85413275.t-ishii@sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-bugs
> I am runing redhat 7.3, and install the postgresql 7.2.1 from Redhat CD.
> I try to create a new database encode with EUC_TW... it should be
> support chinese (Big5). And then i use Pgadmin II to input chinese
> character "r" , it reject me... like following :
> 
> ERROR : Invalid EUC_TW character sequence found (0xa672)....
> 
> when i input "" , it fine... i know the problem in the chinese
> character "r"... but the character just normal ... just like in english
> "A", "B", "C", not a special character in chinese.... i have try more
> more chinese word with different encode.. like unicode, euc_cn..and
> more... also reject me... "invalid.... character sequece...".
> 
> 
> Anyone experience about case.... how to solve the problem ? Please help,
> thanks.

Honestly I'm tired of this kind of complains. Please verify your
"correct" EUC_TW character sequences first.  r"
cannot be correct EUC_TW at all. I have already shown 
Gene Leung "rules to verify your EUC_TW character sequences".
See followings. 

BTW, I have no idea what Pgadmin II is. Are you sure that it supports
EUC_TW? I suspect it only supports Big5. (EUC_TW and Big5 are
completely different beasts).

---------------------------------------------------------------
Ok, here are some rules to verify EUC_TW characters:

(1) if the first byte is 0x8e, then the 8th bit of following three
    bytes must be set

(2) else if the first byte is 0x8f, then the 8th bit of following two
    bytes must be set

(3) else if the 8th bit of the first byte is set, then the 8th bit of
    following one bytes must be set

(4) else (that means the 8th bit of the first byte is not set) then
    that must be an ASCII character.

Apparently 0xa672 does not satisfy all of above.

--
Tatsuo Ishii



In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-06-26 15:02:51
Subject: Re: view OIDs
Previous:From: AlfredoDate: 2002-06-26 14:31:50
Subject: Please I want to unsusribe me from this list

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