Re: Usind database with encoding UNICODE and vovel

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Alejandro D(dot) Burne" <alejandro(dot)dburne(at)gmail(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Usind database with encoding UNICODE and vovel
Date: 2005-08-05 07:38:21
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9812@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: Alejandro D. Burne [mailto:alejandro(dot)dburne(at)gmail(dot)com]
> Sent: 04 August 2005 16:11
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: Usind database with encoding UNICODE and vovel
>
> 2005/8/4, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>:
>
> ...
> > >
> > > Dave, thanks 4 your time;
> > > * I've installed MDAC 2.8 with same results.
> > >
> > > * If I don't set locale on the client it doesn't work,
> pgadmin either
> > > (show wrong encoding data)
> > >
> > > After connect trough odbc:
> > > SHOW CLIENT_ENCODING;
> > > return -> UTF8
> >
> > So to make it work, you do " SET client_encoding TO 'LATIN10' " ?
>
> Yes, I choose LATIN10 after odbc connect and things go ok, I'm using
> visualfoxpro.

OK, great thanks. Seems the sensible thig to try when you think about it
:-)

Regards, Dave.

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2005-08-05 07:48:33 Re: Use Declare/Fetch in new version
Previous Message Lothar Behrens 2005-08-05 04:42:21 Re: SQLColAttribute and SQL_DESC_BASE_TABLE_NAME