Re: TCL and encoding - Mailing list pgsql-general

From Tatsuo Ishii
Subject Re: TCL and encoding
Date
Msg-id 20010711115301W.t-ishii@sra.co.jp
Whole thread Raw
In response to Re: TCL and encoding  (Fernando Schapachnik <fschapachnik@vianetworks.com.ar>)
Responses Re: TCL and encoding  (Fernando Schapachnik <fschapachnik@vianetworks.com.ar>)
List pgsql-general
> En un mensaje anterior, Tatsuo Ishii escribió:
> > > Hello:
> > >     I'm not able to get a proper encoding with TCL 8.3
> > > and Postgres 7.1.2_2.
> > >
> > >     I've tried setting the DB enconding to UNICODE and still
> > > doesn't work.
> >
> > What do you mean by "doesn't work?"
>
> Sorry... I mean non-ASCII chars doesn't look good on PgAccess plus
> they are stored as 'garbage' (really two characters).

For Japanese, an UNICODE database and TCL 8.3 combo works well. What
kind of charset (encoding) are you using? Can I have your data
(produced by pg_dump) so that I could reproduce your problem?

> > >     If I use TCL 8.0 the chars get stored properly on the DB but
> > > are not shown correctly on PgAccess (they are shown in hexa).
> >
> > more detailed information?
>
> Sure, what would you need?

Please tell me the database encoding.
--
Tatsuo Ishii

pgsql-general by date:

Previous
From: Fernando Schapachnik
Date:
Subject: Re: TCL and encoding
Next
From: Justin Clift
Date:
Subject: Re: Re: [DOCS] QUERY - Including the new LDP PostgreSQL HOWTO in the main PostgreSQL distribution