Re: pgsql2shp : Encoding headache
От | Arnaud Lesauvage |
---|---|
Тема | Re: pgsql2shp : Encoding headache |
Дата | |
Msg-id | 4AD8756F.5060105@codata.eu обсуждение исходный текст |
Ответ на | pgsql2shp : Encoding headache (Arnaud Lesauvage <arnaud.listes@codata.eu>) |
Ответы |
Re: [postgis-users] pgsql2shp : Encoding headache
|
Список | 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
В списке pgsql-general по дате отправления: