From: Jasen Betts <jasen@xnet.co.nz>
To: pgsql-sql@postgresql.org
Subject: Re: UTF characters compromising data import.
Date: 12 Feb 2011 09:15:11 GMT
Message-ID: <ij5j2v$t8v$1@reversiblemaps.ath.cx> (raw)
References: <DB66CD37-D380-4C8A-8239-E90B5BD95073@palcare.com.au>
On 2011-02-08, Gavin Beau Baumanis <beau@palcare.com.au> wrote:
> I understand the error message - but what I don't know is what I
> need to set the encoding to - in order to import / use the data.
if you run it through
iconv --from-code=ASCII -to-code=UTF8 -c
it'll strip out all the non-ascii symbols, without knowing the
encoding it's impossible to assign any useful meaning to them.
This step may render your data useless, it would be much better to
find out what the encoding should be.
perhaps you can figure it out by observation?
--
⚂⚃ 100% natural
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jasen@xnet.co.nz
Subject: Re: UTF characters compromising data import.
In-Reply-To: <ij5j2v$t8v$1@reversiblemaps.ath.cx>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox