Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese - Mailing list pgsql-bugs

From Gordon Luk
Subject Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese
Date
Msg-id 3D1AB758.1070600@gforce.ods.org
Whole thread Raw
In response to [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese (Big5)!!! Version 7.2.1 (come with Redhat 7.3)]  (Gordon Luk <gordon@gforce.ods.org>)
List pgsql-bugs
Hi Tatsue Ishii,

Ok, but problem is, when i try encode with unicode, it also reject
me.... invalid UNICODE charater.... :-(
I already try few client, like borland's SQL explorer, zde... and
restore program come with postgresql...

Sorry, i would like to a special request. After i read preious message
from you to Gene Leung, let me fully understand under EUC_TW rule ,
postgresql should reject me (input such invalid charaters). So i request
a special patch that could to support Big5 or disable the validation.

If postgres do not support Big5, that is big problem in chinese...
Please help.

Thanks for your quick response ( i have not response in General Mailling
list :-( , may be no one using postgresql in chinese [Big5].)

Gordon

Tatsuo Ishii wrote:

>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
>
>




_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

pgsql-bugs by date:

Previous
From: Anand
Date:
Subject: weird strncmp bug while executing trigger?
Next
From: Gordon Luk
Date:
Subject: Re: [Fwd: [GENERAL] [Please Help!!!!!!!!] Problem in Chinese