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 ED38655EE3 for ; Mon, 14 Mar 2005 10:43:15 +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 62441-08 for ; Mon, 14 Mar 2005 10:43:06 +0000 (GMT) Received: from sranda.klamovka.kosire.czf (unknown [82.113.63.66]) by svr1.postgresql.org (Postfix) with ESMTP id 4C4B2563AB for ; Mon, 14 Mar 2005 10:42:59 +0000 (GMT) Received: (qmail 15315 invoked from network); 14 Mar 2005 11:43:01 +0100 Received: from startnet.klamovka.kosire.czf (HELO ?192.168.11.101?) (10.15.6.17) by mail.klamovka.kosire.czf with AES256-SHA encrypted SMTP; 14 Mar 2005 11:43:01 +0100 Message-ID: <42356AB5.1010306@startnet.cz> Date: Mon, 14 Mar 2005 11:43:01 +0100 From: =?windows-1252?Q?Miroslav_=8Aulc?= Organization: StartNet s.r.o. User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pginfo Cc: pgsql-sql@postgresql.org Subject: Re: lower and unicode References: <423528B6.2070407@t1.unisoftbg.com> <42354812.7030106@startnet.cz> <42355BFC.4080409@t1.unisoftbg.com> In-Reply-To: <42355BFC.4080409@t1.unisoftbg.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------060807070402080002080807" X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/195 X-Sequence-Number: 20674 This is a multi-part message in MIME format. --------------060807070402080002080807 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit pginfo wrote: > Hi, > I am uusing pg 8.0.1 on FreeBSD 5.3 but I am ready t use the version > taht supports correct unicode. I think that should be fine. I use PostgreSQL 8.0.1 on Linux (Gentoo) without these problems (I used cs_CZ.utf8 to init my db). What you write seems to me that you have your database initialized to something else than xy_XY.utf8 which must be used to have databases working correctly with UNICODE. Try 'locale -a' and choose your locale that has *.utf8 to initialize the database. Then things should be O.K. :-) I don't remember I've seen some note in documentation that users must use for databases the same encoding as they used for initdb. If this is true, it would be time saving to mention this in documentation (if it is not already there). > > regards, > ivan. Miroslav --------------060807070402080002080807 Content-Type: text/x-vcard; charset=utf-8; name="miroslav.sulc.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="miroslav.sulc.vcf" begin:vcard fn;quoted-printable:Miroslav =C5=A0ulc n;quoted-printable:=C5=A0ulc;Miroslav org:StartNet s.r.o. adr;quoted-printable;quoted-printable:;;Vrchlick=C3=A9ho 161/5;Praha 5;;150 00;=C4=8Cesk=C3=A1 republika email;internet:miroslav.sulc@startnet.cz title:CEO tel;work:+420 257 225 602 tel;cell:+420 603 711 413 x-mozilla-html:TRUE url:http://www.startnet.cz version:2.1 end:vcard --------------060807070402080002080807--