From: | Lars Bensmann <lars(dot)bensmann(at)epost(dot)de> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: pgaccess - international characters |
Date: | 2001-07-14 03:20:50 |
Message-ID: | 20010714052050.B9290@epost.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hello,
On Fri, Jul 13, 2001 at 01:32:22AM +0200, Lars Bensmann wrote:
>
> Now we have several Windows workstations using pgaccess to enter data into
> several tables. Everything is fine when using forms. International
> characters (like the german umlaute) work fine. But when I open the table
> directly don't get human readable output for the characters. It varies
> from one or several blank characters to "garbage".
I tested this on another box with Debian unstable installed (this includes
PostgreSQL 7.1.2).
When I use psql to enter umlaut characters everything is fine. pg_dump and
gtksql show proper results. Even pgaccess displays the characters
correctly. But when I enter the characters in pgaccess or update a record
I entered with psql I get this "garbage" again.
I examined this a bit more closely and it seems that the characters are
translated like this:
"a: <C3><A4>
"o: <C3><B6>
"u: <C3><BC>
"A: <C3><84>
"O: <C3><96>
"U: <C3><9C>
"s: <C3><9F>
I get the same results when I enter the data using Tksql as suggested by
Sandro.
This seems to be related to tcl or tk. Am I the only one with this
problem? What can I do about this?
TIA,
Lars
--
Any time things appear to be going better, you have overlooked something.
From | Date | Subject | |
---|---|---|---|
Next Message | Manika Dey | 2001-07-16 14:54:01 | postgres access from windowsNT |
Previous Message | Darko Prenosil | 2001-07-13 23:40:14 | LIBPQ WIN32 NON-BLOCKING |