Received: from www1.translationforge.com (unknown [212.11.36.58]) by postgresql.org (Postfix) with ESMTP id 7E61A47587E for ; Wed, 17 Apr 2002 05:49:18 -0400 (EDT) Received: from linus.translationforge.com ([192.168.1.102]) by www1.translationforge.com (8.12.1/8.12.1) with ESMTP id g3H9nFoX019038; Wed, 17 Apr 2002 11:49:15 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Jean-Michel POURE Reply-To: jm.poure@freesurf.fr Organization: Translationforge To: "Areski Belaid" , Subject: Re: Unicode Secret Date: Wed, 17 Apr 2002 11:49:13 +0200 X-Mailer: KMail [version 1.4] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200204171149.13675.jm.poure@freesurf.fr> X-Archive-Number: 200204/36 X-Sequence-Number: 1060 1) Unicode database > I thing that must create a UNICODE database > compile postgres with unicode support, > ./configure --enable-multibyte > ::> createdb -E UNICODE me-e Correct. If you are new to PostgreSQL, why not simply use PostgreSQL RPMs= =20 which should be compiled by default with the --enable-multibyte feature=20 (Mandrake RPMs are). 2) PHP multi-byte compatibility > I need to use Mbstring or... PHP needs to be compiled with multi-byte options as explained in=20 http://www.php.net/manual/en/install.configure.php Please note you can overload PHP string functions with their multi-byte saf= e=20 equivalent using "mbstring.func_overload =3D positive value" in php.ini. A more detailed information can be found at=20 http://www.php.net/manual/en/ref.mbstring.php. Cheers, Jean-Michel POURE