pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: ogjunk-pgjedan@yahoo.com
To: pgsql-admin@postgresql.org
Subject: Re: Character encoding problems and dump import
Date: Tue, 21 Mar 2006 06:46:46 -0800 (PST)
Message-ID: <20060321144646.71820.qmail@web50313.mail.yahoo.com> (raw)
In-Reply-To: <BFFB32F0-5FF9-4CEB-B0A6-83B90A17AC0D@pgedit.com>

Thanks John and Ivo for help.
It turned out that I had to manually SET CLIENT_ENCODING TO 'LATIN1' before processing the dump (which didn't have this specified).  This fixed the problem.

I thought a DB set to UNICODE char encoding (server_encoding) would process the Extended ASCII characters, but it didn't... not sure why.

Otis

----- Original Message ----
From: John DeSoi <desoi@pgedit.com>
To: ogjunk-pgjedan@yahoo.com
Cc: pgsql-admin@postgresql.org
Sent: Tuesday, March 21, 2006 12:31:16 AM
Subject: Re: [ADMIN] Character encoding problems and dump import


On Mar 20, 2006, at 3:21 PM, <ogjunk-pgjedan@yahoo.com> <ogjunk- 
pgjedan@yahoo.com> wrote:

> The data may not be the cleanest, and I have limited control over  
> that.
> But I am wondering if there is any way I can import this data, even  
> if that means converting some of the characters into something else.

inconv might be able to help you fix encoding problems

http://www.gnu.org/software/libiconv/documentation/libiconv/iconv.1.html



John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org






view thread (4+ messages)

Message-ID: <20060321144646.71820.qmail@web50313.mail.yahoo.com>
Permalink:  ../20060321144646.71820.qmail@web50313.mail.yahoo.com/
Also on:    postgresql.org/message-id/20060321144646.71820.qmail@web50313.mail.yahoo.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: ogjunk-pgjedan@yahoo.com
  Subject: Re: Character encoding problems and dump import
  In-Reply-To: <20060321144646.71820.qmail@web50313.mail.yahoo.com>
  References: <BFFB32F0-5FF9-4CEB-B0A6-83B90A17AC0D@pgedit.com> <20060321144646.71820.qmail@web50313.mail.yahoo.com>

* 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