Re: - Mailing list pgadmin-hackers

From Hiroshi Saito
Subject Re:
Date
Msg-id 018801c38837$c2eaea60$1f324d80@w2k
Whole thread Raw
In response to Re:  ("Serguei A. Mokhov" <mokhov@cs.concordia.ca>)
List pgadmin-hackers
Dear Serguei.

It is strange.
Server has encoding as follows.

-- UNICODE --> KOI8R
CREATE DEFAULT CONVERSION pg_catalog.utf_8_to_koi8_r FOR 'UNICODE' TO 'KOI8R' FR
OM utf8_to_koi8r;
-- KOI8R --> UNICODE
CREATE DEFAULT CONVERSION pg_catalog.koi8_r_to_utf_8 FOR 'KOI8R' TO 'UNICODE' FR
OM koi8r_to_utf8;

Please Try psql command.
\l         <-- list all databases

regards
Hiroshi Saito

----- Original Message -----
From: "Serguei A. Mokhov" <mokhov@cs.concordia.ca>


> Hi,
>
> I think I have a similar issue... A pgAdmin III user contacted me with the
> question why they can't see the data in Russian and how to to solve the
> problem. I queried them for more information. I think their data must be
> encoded in some other encoding (e.g. KOI8-R) and when it gets to the
> client side, it's not converted.
>
> Any other hints aside from below what to try?
>
> -s
>
> On Wed, 1 Oct 2003, Jean-Michel POURE wrote:
>
> > Le Mardi 30 Septembre 2003 17:23, Ã,ngelo Marcos Rigo a écrit :
> > > A Portuguese-Brazilian PgAdmin user describe me a
> > > problem with acentt code, the data on the database
> > > wich have acentt is not displayed properly in PgAdmin
> > > III but do appear properly in PgAdmin II.
> >
> > Hi Ã,ngelo,
> >
> > Could you:
> > - click on the database and show properties. What is the encoding of your
> > database:  SQL_ASCII or Unicode or anything else?
> >
> > - send me privately an attached file including the definition of the table
> > with one row of data. You can use pg_dump --table=TABLE to dump a table. I
> > will test display here.
> >
> > Are you using our stock binaries or did you compile pgAdmin3 yourself? What OS
> > are you running?
> >
> > Cheers, Jean-Michel
>


pgadmin-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: client encoding SQL_ASCII for server SQL_ASCII
Next
From: Andreas Pflug
Date:
Subject: Re: