Re: Charset WIN1252

From: "Gevik Babakhani" <gevik(at)xs4all(dot)nl>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Charset WIN1252
Date: 2004-11-04 05:41:39
Message-ID: 200411040541.iA45fTWH041569@smtp-vbr4.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----Original Message-----
From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Roland Volkmann
Sent: Sunday, October 31, 2004 9:09 PM
To: pgsql-hackers(at)postgresql(dot)org
Subject: [HACKERS] Charset WIN1252

Hello Developers,

now, where the native Win32-Version of PostgreSQL is nearly ready for
Production use, I'm still missing support of WIN1252 charset. And UTF-8
can't be used on server side in West Europe, because it's implementation
isn't complete yet (e.g. upper() / lower() missing for umlauts).

Therefore I've added / modyfied all related sources, headers, and tables for
WIN1252-Support.

Because I can't build Win32-Version of PostgreSQL from source myself, please
let me know who of you would be so kind to add it to the project. I will
send the related ZIP (16 kByte) to everybody who is interested. Meanwhile I
use a binary patched version of the utf8_and_win1250.dll on Server side, so
I can use WIN1252 in the database, and both WIN1252 and UTF-8 on Client side
(but have to specify WIN1250).

With best regards,

Roland.

--
Roland Volkmann
Stuttgart / Germany

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2004-11-04 05:46:18 Re: [HACKERS] Possible make_oidjoins_check Security Issue
Previous Message Tom Lane 2004-11-04 05:07:02 Re: plans for bitmap indexes?