Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 410561BFF91E for ; Fri, 6 Apr 2012 19:19:40 -0300 (ADT) Received: from cerberus.pinpointresearch.com ([66.7.238.130] helo=polaris.pinpointresearch.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SGHVK-00022x-Nh for pgsql-admin@postgresql.org; Fri, 06 Apr 2012 22:19:39 +0000 Received: from betelgeuse.pinpointresearch.com (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id 8EFECE00EC82; Fri, 6 Apr 2012 15:19:25 -0700 (PDT) Message-ID: <4F7F6BEF.6010007@pinpointresearch.com> Date: Fri, 06 Apr 2012 15:19:27 -0700 From: Steve Crawford User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19 MIME-Version: 1.0 To: Matt Williams CC: pgsql-admin@postgresql.org Subject: Re: utf8 database not dumping utf8 characters References: <5D15382C1CF943D8A7B69D102A2BCBD4@williams-tech.net> <4F7F4C2E.7050007@pinpointresearch.com> <2F1A03239AE84E5F8217570AE41AA4C4@williams-tech.net> In-Reply-To: <2F1A03239AE84E5F8217570AE41AA4C4@williams-tech.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201204/26 X-Sequence-Number: 39362 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". Cheers, Steve