> > There's no character code in EUC_TW (CNS 11643-1992)
> > corresponding to Big5 0xc05c. That's why PostgreSQL complains.
>
>
> But I've created another db using MULE_INTERNAL encoding, the same error
> reported, why ?
Since Big5 representation of MULE_INTERNAL is actually "leading
character
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Tatsuo Ishii
> Sent: Wednesday, July 31, 2002 1:18 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [BUGS] Multi-byte character bug
>
>
> > By C
> By Chinese here, I mean BIG5 encoding character which is a widely used
> encoding in HK and Taiwan.
Ok. PostgreSQL does support BIG5 in the *frontend* side.
> I've done a new check on it, I found JDBC and ODBC driver still report
> the error message but psql do not (may be as you said, I've do
>> Two bugs has been found in the SQL parser and Multibyte char support:
>>
>What is the encoding for "chinese char"? You need to give us more info.
By Chinese here, I mean BIG5 encoding character which is a widely used
encoding in HK and Taiwan. My setup:
Db encoding: EUC_TW
C
>> Two bugs has been found in the SQL parser and Multibyte char support:
>>
>What is the encoding for "chinese char"? You need to give us more
>info.
By Chinese here, I mean BIG5 encoding character which is a widely used
encoding in HK and Taiwan.
My setup:
Db encoding: EUC_TW
> Two bugs has been found in the SQL parser and Multibyte char support:
>
> 1. ¡§Problem connecting to database: java.sql.SQLException: ERROR:
> Invalid EUC_TW character sequence found (0xb27a)¡¨ was reported in using
> JDBC driver to insert record, similar error reported when using OD
