Re: encoding and LC_COLLATE

From: "Mark Watson" <mark(dot)watson(at)jurisconcept(dot)ca>
To: "'LPlateAndy'" <andy(at)centremaps(dot)co(dot)uk>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: encoding and LC_COLLATE
Date: 2011-11-14 20:21:33
Message-ID: 54E8C425E06E494185C0A26730C309D6@Gateway
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


De : pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2011-11-14 21:20:39 Re: Upgrade 8.4 with contrib to 9.1
Previous Message Tarlika Elisabeth Schmitz 2011-11-14 18:12:46 Upgrade 8.4 with contrib to 9.1