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
--
Serguei A. Mokhov | /~\ The ASCII
Computer Science Department | \ / Ribbon Campaign
Concordia University | X Against HTML
Montreal, Quebec, Canada | / \ Email!
"I swear, education is the only industry, where
the consumer is happier when they get less
for their money" -- Julia Timofeev
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
