Re: pgsql2shp : Encoding headache

From: Arnaud Lesauvage <arnaud(dot)listes(at)codata(dot)eu>
To: pgsql-general(at)postgresql(dot)org, postgis-users(at)postgis(dot)refractions(dot)net
Subject: Re: pgsql2shp : Encoding headache
Date: 2009-10-16 13:30:23
Message-ID: 4AD8756F.5060105@codata.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Arnaud Lesauvage a écrit :
> But then, if I dump it through a query to have my field in uppercase, I
> get an error 'character 0xc29f of encoding UTF8 has no equivalent in
> WIN1252' (translated by myself, the message is in French)
> The command is simply :
> pgsql2shp -f myouput.shp -u postgres -g mygeom mydatabase "SELECT
> upper(mytext) as mytext, mygeom FROM mytemptable"

OK, I narrowed down the problem to the WIN1252 encoding.
Using LATIN1 or LATIN9 for instance works correctly.
Since my application seems to work with LATIN9, I'll go with it.

I am still perplex though. What is this 0xc29f character ? An internet
search tells me that this is some Kanju character. I am quite confident
that if this is true, it would not convert any better to LATIN9 than to
WIN1252.

Also, doing a search like :
SELECT * FROM mytable WHERE upper(myflied) ILIKE u&'%c29f%';
Gives me 0 result.
Am I wrong to think that the error 'character 0xc29f of UTF8' relates to
the character with code point C29F in UTF8 ?

Thanks again for your help/lightings on this matter.

Arnaud

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-10-16 14:38:52 Re: savepoint name vs prepared transaction name
Previous Message Alban Hertroys 2009-10-16 12:59:13 Re: Wrong estimation of rows for hash join