X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BC5DA5385B for ; Sun, 15 May 2005 14:02:47 -0300 (ADT) 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 40975-10 for ; Sun, 15 May 2005 17:02:43 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id D557953855 for ; Sun, 15 May 2005 14:02:41 -0300 (ADT) Received: (qmail 16336 invoked from network); 15 May 2005 19:03:02 +0200 Received: from unknown (HELO localhost) (boutiquenumerique-lists@192.168.0.4) by boutiquenumerique.com with SMTP; 15 May 2005 19:03:02 +0200 To: "Rajesh Mallah" , pgsql-sql@postgresql.org Subject: Re: Significance of Database Encoding References: <20050515153337.11724.qmail@web31015.mail.mud.yahoo.com> Message-ID: Date: Sun, 15 May 2005 19:02:37 +0200 From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <20050515153337.11724.qmail@web31015.mail.mud.yahoo.com> User-Agent: Opera M2(BETA2)/8.0 (Linux, build 987) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/105 X-Sequence-Number: 21418 > +--------------------------------------------------------------------------------------+ > | 私はガラス > +--------------------------------------------------------------------------------------+ You say it displays correctly in xterm (ie. you didn't see these in your xterm). There are HTML/XML unicode character entities, probably generated by your mailer from your Unicode cut'n'paste. Using SQL ASCII to store UTF8 encoded data will work, but postgres won't know that it's manipulating multibyte characters, so for instance the length of a string will be its Byte length instead of correctly counting the characters, collation rules will be funky, etc. And substring() may well cut in the middle of an UTF8 multibyte char which will then screw your application side processing... Apart from that, it'll work ;)