From klodoma@ar-sd.net Wed Nov 10 08:59:49 2004 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 73F143A2B41 for ; Wed, 10 Nov 2004 08:59:49 +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 60161-07 for ; Wed, 10 Nov 2004 08:59:42 +0000 (GMT) Received: from ar-sd.net (unknown [82.77.155.72]) by svr1.postgresql.org (Postfix) with ESMTP id E7C3A3A1D8F for ; Wed, 10 Nov 2004 08:59:42 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 6DA02E8A2 for ; Wed, 10 Nov 2004 11:01:41 +0200 (EET) Received: from ar-sd.net ([127.0.0.1]) by localhost (linz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29859-06 for ; Wed, 10 Nov 2004 11:01:40 +0200 (EET) Received: from forge (unknown [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id A23D2E82A for ; Wed, 10 Nov 2004 11:01:39 +0200 (EET) Message-ID: <013601c4c703$9ef98b00$0b00a8c0@forge> From: "Andrei Bintintan" To: Subject: How to support German, French and other characters. Date: Wed, 10 Nov 2004 10:59:41 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0133_01C4C714.6110C9A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Virus-Scanned: by amavisd-new at ar-sd.net X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.8 tagged_above=0.0 required=5.0 tests=HTML_30_40, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200411/85 X-Sequence-Number: 15470 This is a multi-part message in MIME format. ------=_NextPart_000_0133_01C4C714.6110C9A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi to all,=20 We are using pgsql as a "multilanguage" database. But I noticed = yesterday a strange problem with the german umlaut characters. I cannot = convert the in upper case in lowercase. Probably there are also other = bad functionalities.=20 Now. I searched the internet for answers but they were not quite exact, = so I could't find a solution.=20 We use ASCII encoding for the database, but I tried the Latin1 -> Latin = 10 and the behavior is the same. In some forums there is written = something about some "locale" setting... etc etc.=20 What settings do I have to make so that we won't have these problems in = the future. We intend to work with French characters also, and in the = future with Hungarian.=20 As system the pgsql is v.7.4 running on a Suse 9.1 machine. The locale = command gives me: linz:/var/lib/pgsql/data # locale LANG=3D LC_CTYPE=3Den_US.UTF-8 LC_NUMERIC=3D"POSIX" LC_TIME=3D"POSIX" LC_COLLATE=3D"POSIX" LC_MONETARY=3D"POSIX" LC_MESSAGES=3D"POSIX" LC_PAPER=3D"POSIX" LC_NAME=3D"POSIX" LC_ADDRESS=3D"POSIX" LC_TELEPHONE=3D"POSIX" LC_MEASUREMENT=3D"POSIX" LC_IDENTIFICATION=3D"POSIX" LC_ALL=3D Thank you in advance. Andy. ------=_NextPart_000_0133_01C4C714.6110C9A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
Hi to all,
 
We are using pgsql as a "multilanguage" = database.=20 But I noticed yesterday a strange problem with the german umlaut = characters. I=20 cannot convert the in upper case in lowercase. Probably there are also = other bad=20 functionalities.
 
Now. I searched the internet for = answers but they=20 were not quite exact, so I could't find a solution.
 
We use ASCII encoding for the database, = but I tried=20 the Latin1 -> Latin 10 and the behavior is the same. In some forums = there is=20 written something about some "locale" setting... etc etc.
 
What settings do I have to make so that = we won't=20 have these problems in the future. We intend to work with French = characters=20 also, and in the future with Hungarian.
 
As system the pgsql is v.7.4 running on = a Suse 9.1=20 machine. The locale command gives me:
 
linz:/var/lib/pgsql/data #=20 locale
LANG=3D
LC_CTYPE=3Den_US.UTF-8
LC_NUMERIC=3D"POSIX"
LC= _TIME=3D"POSIX"
LC_COLLATE=3D"POSIX"
LC_MONETARY=3D"POSIX"
LC_ME= SSAGES=3D"POSIX"
LC_PAPER=3D"POSIX"
LC_NAME=3D"POSIX"
LC_ADDRESS= =3D"POSIX"
LC_TELEPHONE=3D"POSIX"
LC_MEASUREMENT=3D"POSIX"
LC_ID= ENTIFICATION=3D"POSIX"
LC_ALL=3D
 
Thank you in advance.
Andy.
------=_NextPart_000_0133_01C4C714.6110C9A0-- From klodoma@ar-sd.net Thu Nov 11 17:13:26 2004 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 2469D3A464C for ; Thu, 11 Nov 2004 17:13:26 +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 43382-04 for ; Thu, 11 Nov 2004 17:13:22 +0000 (GMT) Received: from ar-sd.net (unknown [82.77.155.72]) by svr1.postgresql.org (Postfix) with ESMTP id DC3173A4AC1 for ; Thu, 11 Nov 2004 15:31:37 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by ar-sd.net (Postfix) with ESMTP id 80D25E92A; Thu, 11 Nov 2004 10:24:26 +0200 (EET) Received: from ar-sd.net ([127.0.0.1]) by localhost (linz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08322-01; Thu, 11 Nov 2004 10:24:24 +0200 (EET) Received: from forge (unknown [192.168.0.11]) by ar-sd.net (Postfix) with SMTP id EF669E455; Thu, 11 Nov 2004 10:24:23 +0200 (EET) Message-ID: <009401c4c7c7$9a09f660$0b00a8c0@forge> From: "Andrei Bintintan" To: "Ivo Rossacher" Cc: References: <013601c4c703$9ef98b00$0b00a8c0@forge> <200411102057.25780.rossacher@bluewin.ch> Subject: Re: How to support German, French and other characters. Date: Thu, 11 Nov 2004 10:22:34 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Virus-Scanned: by amavisd-new at ar-sd.net 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/97 X-Sequence-Number: 15482 Hi Ivo, If I use UNICODE encoding for the DB I get some errors: For example the following query: select lower('MöBÜEL') returns ERROR: Unicode characters greater than or equal to 0x10000 are not supported. I found this on a forum: ---------------------------------------------------------------- ---------------------------------------------------------------- > postgres 7.4 on linux, glibc 2.2.4-6 > I've a table containing unicode-data and the lower()-function does not > work proper. While it lowers standard letters like A->a,B->b ... it > fails on special letters like german umlauts (Ä , Ö ...) that are simply > keeped untouched. upper() and lower() didn't support multibyte character sets before 8.0. regards, tom lane ---------------------------------------------------------------- ---------------------------------------------------------------- We are using these king of comparations and character translations in our DB. I really cannot figure out what solution to use. Best regards, Andy. ----- Original Message ----- From: "Ivo Rossacher" To: "Andrei Bintintan" Sent: Wednesday, November 10, 2004 9:57 PM Subject: Re: [ADMIN] How to support German, French and other characters. > Dear Andy, > > ASCII encoding means that the database does not care (and know) about the > encoding. So the client is in full charge to deal with the encoding issue. > This is very uncomfortable within a multilanguage enviroment. Without the > encoding the caption can not be determined correctly by the database it self. > Suse 9.1 does use unicode as the default encoding for all the desctop. For my > multilanguage projects I do use therefore UNICODE as encoding for the > database. (createdb -EUNICODE dbname will generate a unicode database more > precisly a UTF8 database) > Most of the Microsoft clients are internal UNICODE anyway and can deal with > this setting. Older Unix or Linux installations need some tweaking probably. > > Best regards > Ivo Rossacher > > Am Mittwoch, 10. November 2004 09.59 schrieben Sie: > > Hi to all, > > > > We are using pgsql as a "multilanguage" database. But I noticed yesterday a > > strange problem with the german umlaut characters. I cannot convert the in > > upper case in lowercase. Probably there are also other bad functionalities. > > > > Now. I searched the internet for answers but they were not quite exact, so > > I could't find a solution. > > > > We use ASCII encoding for the database, but I tried the Latin1 -> Latin 10 > > and the behavior is the same. In some forums there is written something > > about some "locale" setting... etc etc. > > > > What settings do I have to make so that we won't have these problems in the > > future. We intend to work with French characters also, and in the future > > with Hungarian. > > > > As system the pgsql is v.7.4 running on a Suse 9.1 machine. The locale > > command gives me: > > > > linz:/var/lib/pgsql/data # locale > > LANG= > > LC_CTYPE=en_US.UTF-8 > > LC_NUMERIC="POSIX" > > LC_TIME="POSIX" > > LC_COLLATE="POSIX" > > LC_MONETARY="POSIX" > > LC_MESSAGES="POSIX" > > LC_PAPER="POSIX" > > LC_NAME="POSIX" > > LC_ADDRESS="POSIX" > > LC_TELEPHONE="POSIX" > > LC_MEASUREMENT="POSIX" > > LC_IDENTIFICATION="POSIX" > > LC_ALL= > > > > > > Thank you in advance. > > Andy. > > -- > Ivo Rossacher >