Re: Multibyte ODBC

> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> Sent: 27 February 2002 23:45
> To: Dave Page
> Cc: 'jm(dot)poure(at)freesurf(dot)fr'; pgadmin-hackers(at)postgresql(dot)org;
> pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Multibyte ODBC
>
>
> Dave Page wrote:
> >
> > Hiroshi, please disregard my earlier email requesting a
> precompiled MB
> > copy of the driver - I found Eiji Tokuya's download.
> >
> > I have now tried the following tests using my own
> compilation of the
> > MB driver and Eiji's:
> >
> > 1) Created a unicode database in 7.2/cygwin and loaded
> Jean-Michel's
> > Japanese test table.
> >
> > 2) Created a datasource, and added SET
> CLIENT_ENCODING='SJIS' to the
> > connect settings.
> >
> > 3) Linked the test table from Microsoft Access XP.
> >
> > 4) Using the Arial Unicode MS font, the data in Access looks like
> > garbage.
>
> You need to set the *Japanese* locale if you'd like to
> display Japanese using SJIS.

Please excuse my ignorance on this one Hiroshi, but just about everything I
read is getting me more confused :-(

I assume by locale, in this context you mean Windows local - what it calls
it's regional settings? If so, I think this is still a problem because what
we are trying to achieve (at least in Access as it seems VB won't do it) is
display of multiple languages at once. For example, in a fictional case
someone may have a Unicode database that may contain data in Japanese
(UTF-8), French, English and maybe other languages (Jean-Michel may even be
in this situation now).

Access can do this quite happily with it's native tables (with no locale
changes), it's just the linked PostgreSQL tables that don't want to work
:-(.

Regards, Dave