Re: encoding and LC_COLLATE - Mailing list pgsql-general

From Mark Watson
Subject Re: encoding and LC_COLLATE
Date
Msg-id 54E8C425E06E494185C0A26730C309D6@Gateway
Whole thread Raw
In response to Re: encoding and LC_COLLATE  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: encoding and LC_COLLATE  (LPlateAndy <andy@centremaps.co.uk>)
List pgsql-general
De : pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] De la part de Adrian Klaver
>Envoyé : 14 novembre 2011 13:03
>...
>
>Second is the data coming in actually UTF8 or some other encoding?
>... 

Hi Andy,
I have to agree with Adrian in that the data may be coming in under a
different encoding. An e acute is a valid character in 1252 encoding.
However, if the source computer is using, for example, code page 850, an e
acute is hex(82) whereas the equivalent in 1252 is hex(e9). UTF-8 "doesn't
like" hex(82).
HTH,
Mark


pgsql-general by date:

Previous
From: Tarlika Elisabeth Schmitz
Date:
Subject: Upgrade 8.4 with contrib to 9.1
Next
From: MikeW
Date:
Subject: syntax highlighting in emacs after \e in psql