> -----Original Message-----
> From: pgsql-bugs-owner(at)postgresql(dot)org
> [mailto:pgsql-bugs-owner(at)postgresql(dot)org] On Behalf Of Tatsuo Ishii
> Sent: Wednesday, July 31, 2002 1:18 PM
> To: richso(at)i-cable(dot)com
> Cc: pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] Multi-byte character bug
> > 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 done a
> > wrong procedure). However, the problem still there: why
> JDBC and ODBC
> > still report the error ?
> psql works but JDBC and ODBC does not? The fact that psql is
> working tell us that at least BIG5<-->EUC_TW works fine. It
> seems something wrong with JDBC and ODBC settings.
> Unfortunately I'm not a Java or ODBC expert at all. Sorry...
Ok ! I will post to the jdbc and odbc thread for help !
> > The character code is 0xc05c, in which the second byte is
> actually a
> > "\"
> > (back-slash)
> > (pls see the attached file: offence2.zip)
> 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 ?
Why don't Postgres directly support BIG5 in server side as BIG5 is the
main encoding using for Traditional Chinese communities, i.e. HK &
Taiwan ? As EUC_TW do not have complete correspondings char in BIG5,
this will seriously prevent the Traditional Chinese communities for
using Postgresql !
> Tatsuo Ishii
> ---------------------------(end of
> TIP 5: Have you checked our extensive FAQ?
In response to
pgsql-bugs by date
|Next:||From: Neil Conway||Date: 2002-07-31 20:14:31|
|Subject: Re: share lib libpq++|
|Previous:||From: Gibellini Paolo||Date: 2002-07-31 17:20:19|
|Subject: ERROR: scanNameSpaceForRefname: unexpected node type 0|