Received: from mailout03.sul.t-online.de (mailout03.sul.t-online.com [194.25.134.81]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6E3RNa71431 for ; Fri, 13 Jul 2001 23:27:23 -0400 (EDT) (envelope-from lars.bensmann@epost.de) Received: from fwd05.sul.t-online.de by mailout03.sul.t-online.de with smtp id 15LG5O-0005oT-00; Sat, 14 Jul 2001 05:27:18 +0200 Received: from skywalker.ddts.net (520053192776-0001@[217.80.203.122]) by fmrl05.sul.t-online.com with smtp id 15LG5C-0JY7aCC; Sat, 14 Jul 2001 05:27:06 +0200 Received: (qmail 9357 invoked by uid 1002); 14 Jul 2001 03:20:50 -0000 Date: Sat, 14 Jul 2001 05:20:50 +0200 From: Lars Bensmann To: pgsql-interfaces@postgresql.org Subject: Re: pgaccess - international characters Message-ID: <20010714052050.B9290@epost.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010713013221.A1515@epost.de> User-Agent: Mutt/1.3.18i X-Sender: 520053192776-0001@t-dialin.net X-Archive-Number: 200107/56 X-Sequence-Number: 1809 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: "o: "u: "A: <84> "O: <96> "U: <9C> "s: <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.