Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 6C5541F60608
	for <pgsql-admin@postgresql.org>; Sat,  7 Apr 2012 00:28:29 -0300 (ADT)
Received: from mail-qa0-f53.google.com ([209.85.216.53])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <matt@williams-tech.net>) id 1SGMKA-0003H0-Ng
	for pgsql-admin@postgresql.org; Sat, 07 Apr 2012 03:28:28 +0000
Received: by qadc11 with SMTP id c11so640974qad.19
	for <pgsql-admin@postgresql.org>; Fri, 06 Apr 2012 20:28:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=date:from:to:cc:message-id:in-reply-to:references:subject:x-mailer
	:mime-version:content-type:x-gm-message-state;
	bh=QT5ZT2kKgBTDITUQPLhL6c00kizYjO3tlqJF0tN4aRA=;
	b=S2ohtjl67hYI0vD8z3mYVX6za5Ag0cbVkDmFotKf5grsUhCVy1bmTUKZT2NefYnL6g
	+ZRLiOV+uImBRWrl9JQNrhGZkkwcB6dfvwEPXHPuK9DqQTDKy3oAM/Ymr40JTEEwbbC3
	p+iHU59J4HVnH5pYon0rb6BJca82YOXu7ZMa+DieDtSmonXU8N0W4e97siratKPs3OO+
	CS6BbH1/QFIadJTogHuq1R1FZGE3kwgfY8+xfwRohsDzDvqjXDDlYBhSpxnULcvAkZ6M
	qEALG4BKMuOnY/HM4KGKjShYtBGh2+ureVAUwdJU/muU9H2bZH6QZAjHG3W+Y891ND5+
	gt/w==
Received: by 10.224.211.72 with SMTP id gn8mr290696qab.10.1333769293320;
	Fri, 06 Apr 2012 20:28:13 -0700 (PDT)
Received: from Macs-MacBook-Pro.local (va-67-237-163-66.dhcp.embarqhsd.net.
	[67.237.163.66])
	by mx.google.com with ESMTPS id i8sm13922171qah.4.2012.04.06.20.28.10
	(version=TLSv1/SSLv3 cipher=OTHER);
	Fri, 06 Apr 2012 20:28:11 -0700 (PDT)
Date: Fri, 6 Apr 2012 23:28:09 -0400
From: Matt Williams <matt@williams-tech.net>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-admin@postgresql.org
Message-ID: <2BEA6CD7145B481EBC76D45CC3EC2060@williams-tech.net>
In-Reply-To: <4F7F6BEF.6010007@pinpointresearch.com>
References: <5D15382C1CF943D8A7B69D102A2BCBD4@williams-tech.net>
	<4F7F4C2E.7050007@pinpointresearch.com>
	<2F1A03239AE84E5F8217570AE41AA4C4@williams-tech.net>
	<4F7F6BEF.6010007@pinpointresearch.com>
Subject: Re: utf8 database not dumping utf8 characters
X-Mailer: sparrow 1.5 (build 1043)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f7fb449_5ec6afd4_f71e"
X-Gm-Message-State: 
 ALoCoQnAXV0YwrIRZ3aCW9Yp3RhCx7pIOiGrBaY5WWcb89QZAayA4GYTEnOP5rYefY443oP1iIxt
X-Pg-Spam-Score: -2.0 (--)
X-Archive-Number: 201204/27
X-Sequence-Number: 39363

--4f7fb449_5ec6afd4_f71e
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I ran it through xxd and the hex-bytes are different than those of the pr=
oper utf8 character:

03300a0: 7472 c383 c2b6 6d65 7209 3009 5c4e 0931  tr....mer.0.=5CN.1 (fro=
m the dump file)

=C3=B6 : c3b6 =20

=C3=83=C2=B6 : c383 c2b6

-- =20
Matt Williams
Sent with Sparrow (http://www.sparrowmailapp.com/=3Fsig)


On =46riday, 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 =20
> > can paste in the utf8 character I provided as an example and it =20
> > displays correctly.
> > =20
> =20
> I usually find a good first step is to run the file through something =20
> that will give you a hex dump (i.e. xxd or similar) and so I *know* the=
 =20
> actual bytes in the file rather than relying on how they may be =20
> interpreted somewhere else along the chain. =46ind the hex-byte(s) of y=
our =20
> suspect character and look it up.
> =20
> Since you are in vim, it may be worth checking =22:set termencoding=22,=
 =20
> =22:set encoding=22 and =22:set fileencoding=22.
> =20
> Cheers,
> Steve
> =20
> =20



--4f7fb449_5ec6afd4_f71e
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


                <div>I ran it through xxd and the hex-bytes are different=
 than those of the proper utf8 character:</div><div><br></div><div>03300a=
0: 7472 c383 c2b6 6d65 7209 3009 5c4e 0931 &nbsp;tr....mer.0.=5CN.1&nbsp;=
(from the dump file)</div><div><div><br></div><div>=C3=B6 : c3b6</div></d=
iv>
                <div><div><br></div><div>=C3=83=C2=B6 : c383 c2b6</div><d=
iv><br></div><div>--&nbsp;</div><div>Matt Williams</div><div>Sent with <a=
 href=3D=22http://www.sparrowmailapp.com/=3Fsig=22>Sparrow</a></div><div>=
<br></div></div>
                =20
                <p style=3D=22color: =23A0A0A8;=22>On =46riday, April 6, =
2012 at 6:19 PM, Steve Crawford wrote:</p>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><div><div><div>On 04/06/2012 01:10 PM, Matt Wil=
liams wrote:</div><blockquote type=3D=22cite=22><div><div>With that same =
dump file that is displaying incorrectly open in vim, I </div><div>can pa=
ste in the utf8 character I provided as an example and it </div><div>disp=
lays correctly.</div></div></blockquote><div>I usually find a good first =
step is to run the file through something </div><div>that will give you a=
 hex dump (i.e. xxd or similar) and so I *know* the </div><div>actual byt=
es in the file rather than relying on how they may be </div><div>interpre=
ted somewhere else along the chain. =46ind the hex-byte(s) of your </div>=
<div>suspect character and look it up.</div><div><br></div><div>Since you=
 are in vim, it may be worth checking =22:set termencoding=22, </div><div=
>=22:set encoding=22 and =22:set fileencoding=22.</div><div><br></div><di=
v>Cheers,</div><div>Steve</div></div></div></span>
                =20
                =20
                =20
                =20
                </blockquote>
                =20
                <div>
                    <br>
                </div>
            
--4f7fb449_5ec6afd4_f71e--