Skip site navigation (1) Skip section navigation (2)

Re: German umlauts in pgadmin III

From: Tino Wildenhain <tino(at)wildenhain(dot)de>
To: Albin Blaschka <Albin(dot)Blaschka(at)bal(dot)bmlfuw(dot)gv(dot)at>
Cc: "'pgadmin-support(at)postgresql(dot)org'" <pgadmin-support(at)postgresql(dot)org>,Reinhard Resch <Reinhard(dot)Resch(at)bal(dot)bmlfuw(dot)gv(dot)at>,Wilhelm Graiss <Wilhelm(dot)Graiss(at)bal(dot)bmlfuw(dot)gv(dot)at>
Subject: Re: German umlauts in pgadmin III
Date: 2003-10-20 09:08:16
Message-ID: 3F93A600.9050004@wildenhain.de (view raw or flat)
Thread:
Lists: pgadmin-support
Hi Albin,

Albin Blaschka wrote:
> Hello,
> 
> I am confronted with a little problem in pgadmin III:
> 
> Table cells and comments on database objects are not 
> properly displayed if they contain a german umlaut.
> The table cells just contain  ", the comments (on tables,
> for example) are completly empty.
> In pgadmin II everything is okay, if I connect via
> ODBC/Access to the tables, the umlauts are properly
> displayed, too.
> 
> Plattform for pgadmin: Win 2000
> Database: Postgres 7.3.2 on Debian Linux Woody (3.0),
> Database encoding SQL_ASCII
                     ^^^^^^^^^^

This is wrong. You cant have Umlauts with ASCII.
If you input them, you violate the ASCII codeset,
wich is 7 Bit only.
You'll have to recode your data to ISO8859-1
(Latin-1) or any superset (UNICODE)
Then pgadminIII works as well as any other
application. For migration or your apps
they should just set their client_encoding
to iso8859-1 then (if you choose UNICODE)

Regards
Tino Wildenhain


In response to

Responses

pgadmin-support by date

Next:From: Reshat SabiqDate: 2003-10-21 05:10:56
Subject: Re: German umlauts in pgadmin III
Previous:From: Andreas PflugDate: 2003-10-20 09:07:29
Subject: Re: German umlauts in pgadmin III

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group