From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | fschapachnik(at)vianetworks(dot)com(dot)ar |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: TCL and encoding |
Date: | 2001-07-11 02:53:01 |
Message-ID: | 20010711115301W.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2001-07-11 03:26:54 | Re: [GENERAL] Re: QUERY - Including the new LDP PostgreSQL HOWTO in the main PostgreSQL distribution |
Previous Message | Fernando Schapachnik | 2001-07-11 02:49:10 | Re: TCL and encoding |