Re: Change server encoding after the fact

From: Cody Caughlan <toolbag(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Change server encoding after the fact
Date: 2011-09-30 19:45:12
Message-ID: CAPVp=gazwcHgFNLTpSv1AjKqxSyFgNbwGxor1ZQLzVAMBnX74Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

That worked, but "file" shows no difference:

$ iconv -f utf-8 -t utf-8 -c foo.sql > utf.sql
$ file -i foo.sql
foo.sql: text/plain; charset=us-ascii

$file -i utf.sql
utf.sql: text/plain; charset=us-ascii

So iconv didnt actually convert the file OR does is the "file" command just
ignorant?

On Fri, Sep 30, 2011 at 12:41 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:

> On Fri, Sep 30, 2011 at 1:39 PM, Cody Caughlan <toolbag(at)gmail(dot)com> wrote:
> > Its a Rails app and I do have:
> > encoding: utf8
>
>
> Hmmm, if you try this does it work (mostly)?
>
> iconv -f utf-8 -t utf-8 -c < infile > outfile
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dario Beraldi 2011-09-30 19:53:14 Re: postgres for OLAP & data mining
Previous Message Scott Marlowe 2011-09-30 19:43:00 Re: Change server encoding after the fact