I ran it through xxd and the hex-bytes are different than those of the proper utf8 character:
03300a0: 7472 c383 c2b6 6d65 7209 3009 5c4e 0931 tr....mer.0.\N.1 (from the dump file)
ö : c3b6
Ã¶ : c383 c2b6
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Friday, April 6, 2012 at 6:19 PM, Steve Crawford wrote:
> On 04/06/2012 01:10 PM, Matt Williams wrote:
> > With that same dump file that is displaying incorrectly open in vim, I
> > can paste in the utf8 character I provided as an example and it
> > displays correctly.
> I usually find a good first step is to run the file through something
> that will give you a hex dump (i.e. xxd or similar) and so I *know* the
> actual bytes in the file rather than relying on how they may be
> interpreted somewhere else along the chain. Find the hex-byte(s) of your
> suspect character and look it up.
> Since you are in vim, it may be worth checking ":set termencoding",
> ":set encoding" and ":set fileencoding".
In response to
pgsql-admin by date
|Next:||From: Dave Johansen||Date: 2012-04-08 04:35:15|
|Subject: Re: libpqxx for x86 builds of RHEL?|
|Previous:||From: Steve Crawford||Date: 2012-04-06 22:19:27|
|Subject: Re: utf8 database not dumping utf8 characters|