Received: from mailhub1.isdnet.net (mailhub1.isdnet.net [195.154.209.21]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9SFdHP56946 for ; Sun, 28 Oct 2001 10:39:17 -0500 (EST) (envelope-from jm.poure@freesurf.fr) Received: from station ([195.154.28.3]) by mailhub1.isdnet.net (8.9.3/8.9.3) with ESMTP id QAA04389; Sun, 28 Oct 2001 16:37:51 +0100 (CET) Message-Id: <4.2.0.58.20011028163302.00cdc890@pop.freesurf.fr> X-Sender: jm.poure@pop.freesurf.fr X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 28 Oct 2001 16:37:48 +0100 To: Marko Kreen From: Jean-Michel POURE Subject: Re: UNICODE Cc: pgsql-hackers@postgresql.org In-Reply-To: <20011028170945.A18241@l-t.ee> References: <4.2.0.58.20011028140833.00d13490@pop.freesurf.fr> <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr> <4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr> <4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr> <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr> <4.2.0.58.20011028140833.00d13490@pop.freesurf.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f9SG1ZM61963 X-Archive-Number: 200110/990 X-Sequence-Number: 14712 At 17:09 28/10/01 +0200, you wrote: >On Sun, Oct 28, 2001 at 02:34:49PM +0100, Jean-Michel POURE wrote: > > > > >psql uses your input literally - so is your console/xterm in > > >UNICODE/UTF8? > > Client: \encoding returns 'UNICODE'. > > Server: \list show databases. All databases are UNICODE (except TEMPLATE0 > > and TEMPLATE1 which are ASCII of course). I use a Mandrake 8.1 > distribution > > and think my console is UNICODE. > >You think? Try this: > > $ echo "accepté" | od -c > >If your term is in utf you should get: > > 0000000 a c c e p t 303 251 \n > 0000011 > >If in iso-8859-1: > > 0000000 a c c e p t 351 \n > 0000010 > >It may be in some other 8bit encoding too, then the last number >may be different. It is: 0000000 a c c e p t é \n 0000010 >Hmm. It may be a bug in input routines. You give PostgreSQL a >1byte 'é', it expects 2 byte char and overflows somewhere. Can >you reproduce it on 7.1.3? Maybe its fixed there, I cant >reproduce it. I noticed some longer routines with "é" worked without any problem. I cannot reproduce it as I converted my database to plain ASCII. Will try UNICODE on 7.2 beta when adding Japanese text to my database. Thank you very much for your help. Best regards, Jean-Michel POURE