Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 4F0801BFF91D for ; Fri, 6 Apr 2012 17:11:06 -0300 (ADT) Received: from mail-ob0-f174.google.com ([209.85.214.174]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SGFUt-0004xh-1z for pgsql-admin@postgresql.org; Fri, 06 Apr 2012 20:11:05 +0000 Received: by obbtb18 with SMTP id tb18so3506048obb.19 for ; Fri, 06 Apr 2012 13:10:49 -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=gOwMW7QqYejbYx/JlfHdp1OwAkN9EEGyeEE/LDS4K50=; b=HhwcymFjauURf5INt2k8FSk/Lrijwdt3ywwm0zT8i0ov+hCudvbbYwnG0w+Runr5BT Va9CG/6wtK8bEQbi4cuM5mQ43I9Kj+3sYsgUIZsmzqDCd+uF3FUzLdYTP0YwQajnQgiF 5osUadR9xtX6dFhmDggM63JH9CykXaGxppOls24V2m2Al85OOTwUydT5JlQbE8iC9ClN NzDYOJ5bEDYjf+I+6NQjXBlDxlk3kLFy4ClvdZl3uKqAoKZVFA+ZMNIhFP+0n07E7Zco 7g8C18CZKrWT/BETm3vVQmttLoBHXFjo8Yv4zuhMblwRDZXmoYwiJY1F4NbrjArTu0f8 GarQ== Received: by 10.182.72.71 with SMTP id b7mr10871615obv.11.1333743049609; Fri, 06 Apr 2012 13:10:49 -0700 (PDT) Received: from Macs-MacBook-Pro.local (h254.124.149.24.cable.rstb.jetbroadband.com. [24.149.124.254]) by mx.google.com with ESMTPS id yv3sm8196038obb.3.2012.04.06.13.10.48 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 Apr 2012 13:10:49 -0700 (PDT) Date: Fri, 6 Apr 2012 16:10:46 -0400 From: Matt Williams To: Steve Crawford Cc: pgsql-admin@postgresql.org Message-ID: <2F1A03239AE84E5F8217570AE41AA4C4@williams-tech.net> In-Reply-To: <4F7F4C2E.7050007@pinpointresearch.com> References: <5D15382C1CF943D8A7B69D102A2BCBD4@williams-tech.net> <4F7F4C2E.7050007@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="4f7f4dc6_555c55b5_f71e" X-Gm-Message-State: ALoCoQkZXBvWewHbW9NwlQX0VxcatOpPK5VQLg3fdGpvExm0uacGPTYR8nVwFzb8nyD7oYChjV2W X-Pg-Spam-Score: -2.0 (--) X-Archive-Number: 201204/24 X-Sequence-Number: 39360 --4f7f4dc6_555c55b5_f71e Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline With that same dump file that is displaying incorrectly open in vim, I ca= n paste in the utf8 character I provided as an example and it displays co= rrectly. =20 -- =20 Matt Williams Sent with Sparrow (http://www.sparrowmailapp.com/=3Fsig) On =46riday, April 6, 2012 at 4:03 PM, Steve Crawford wrote: > On 04/06/2012 12:55 PM, Matt Williams wrote: =20 > > I have a database that is utf8 and displays utf8 values correctly in = psql. When dumped, it displays the utf8 characters incorrectly. ie. =C3=B6= turns into =C3=83 > > =20 > > In the header of the dump file, I have: =20 > > =20 > > SET client=5Fencoding =3D 'UT=468'; =20 > > =20 > > So I'm not sure where the disconnect is=3F =20 > > =20 > > Thoughts=3F =20 > > =20 > > Thanks, =20 > > =20 > > -- =20 > > Matt Williams > > Sent with Sparrow (http://www.sparrowmailapp.com/=3Fsig) > > =20 > With what are you viewing the dump file and is everything in the chain = (terminal, less/vi/...) set to interpret/display that data as UT=468=3F Y= ou can always use a hex-dump program to see the actual bytes in the file = and determine if they are what you expect for UT=468. > =20 > Cheers, > Steve > =20 --4f7f4dc6_555c55b5_f71e Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
With that same dump file that is displaying incorrect= ly open in vim, I can paste in the utf8 character I provided as an exampl= e and it displays correctly.

-- 
Matt Williams=
Sent with Sparrow

=20

On =46riday, April 6, = 2012 at 4:03 PM, Steve Crawford wrote:

=20 =20 =20 On 04/06/2012 12:55 PM, Matt Williams wrote:
I have a database that is utf8 and displays utf8 values correctly in psql. When dumped, it displays the utf8 characters incorrectly. ie. =C3=B6= turns into =C3=83

In the header of the dump= file, I have:

SET client=5Fencoding =3D= 'UT=468';

So I'm not sure where the disconnect is=3F=

Thoughts=3F

Thanks,

-- 
Matt Williams
Sent with Sparrow

With what are you viewing the dump file and is everything in the chain (terminal, less/vi/...) set to interpret/display that data as UT=468=3F You can always use a hex-dump program to see the actual byt= es in the file and determine if they are what you expect for UT=468.
=
Cheers,
Steve

=20
=20 =20 =20 =20
=20

--4f7f4dc6_555c55b5_f71e--