From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Johann Woeckinger" <johann(dot)woeckinger(at)epluse(dot)at> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Character encoding problem using Tcl |
Date: | 2000-12-18 15:13:21 |
Message-ID: | 18958.977152401@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Johann Woeckinger" <johann(dot)woeckinger(at)epluse(dot)at> writes:
> But when using a Tcl-based interface (e.g. pgaccess or home made tcl
> based programs) to insert such characters into a table, they are not correct
> displayed on queries by use of psql - they appear as two 'unreadable'
> characters (they appear correct in queries done by the tcl application).
Hm. Tcl 8 uses Unicode (UTF-8) representation internally. It sounds
like the Unicode representation is getting sent straight to the database
rather than being converted into the character set the backend is
expecting.
We could fix this in libpgtcl if we could figure out what Tcl encoding
corresponds to the character set the backend is using. I'm not sure
if that's easy or hard.
Alternatively, building Postgres with multibyte support and creating
your database with UNICODE encoding ought to work.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-12-18 15:18:44 | Re: More on character encoding in SELECTs |
Previous Message | John Burski | 2000-12-18 15:05:35 | Re: Sequence |