X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 910DF3A3E8A for ; Tue, 16 Nov 2004 10:26:33 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60999-05 for ; Tue, 16 Nov 2004 10:26:28 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 8FA5B3A3E81 for ; Tue, 16 Nov 2004 10:26:28 +0000 (GMT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id iAGAQPZ21099; Tue, 16 Nov 2004 19:26:25 +0900 Message-ID: <000a01c4cbc6$ded1a1a0$7201a8c0@mst1x5r347kymb> From: "Iain" To: "Peter Eisentraut" Cc: "pgsql-admin list" References: <200411160818.54201.peter_e@gmx.net> <002b01c4cbb8$975c0df0$7201a8c0@mst1x5r347kymb> <200411161043.52605.peter_e@gmx.net> Subject: Re: evil characters #bfef cause dump failure Date: Tue, 16 Nov 2004 19:27:22 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-15"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/130 X-Sequence-Number: 15514 Hi Peter, I know that the unicode standards are far from perfect, but I'm wondering why you consider it a failure. Is it technical, or just an acceptance thing?