Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers-win32(at)postgresql(dot)org>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Date: 2005-02-22 20:50:10
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE476966@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
The installer does not permit it, but initdb lets you do anything yuo
want - I think that's where we are. If you know what you're doing, you
can use it by manually initdbing.

There is no such thing as "unicode locale". Unicode (UTF8) is an
encoding, that has to be paired with a locale. I assume you mean C
locale. 

While UPPER/LOWER does not matter, sort order does - for indexes if
nothing else. I'm unsure if this works - I think I read reports about
itn ot working, but I haven't tried it out myself.


I was hoping for a final solution for 8.1 which actually fixes it so it
works all the way. Not sure if I can make that happen myself, but I can
always try unless someone else does it.

//mha



>-----Original Message-----
>From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us] 
>Sent: den 22 februari 2005 04:43
>To: Tatsuo Ishii
>
>
>Magnus, where are we on this?   Seems we should allow unicode encoding
>and just not unicode locale in pginstaller.
>
>Also, Unicode is changing to UTF-8 in 8.1.
>
>---------------------------------------------------------------
>------------
>
>Tatsuo Ishii wrote:
>> I do understand the problem, but don't undertstand the decision you
>> guys made. The fact that UPPER/LOWER and some other 
>functions does not
>> work in win32 is surely a problem for some languages, but not a
>> problem for otheres. For example, Japanese (and probably Chinese and
>> Korean) does not have a concept upper/lower. So the fact UPPER/LOWER
>> does not work with UTF-8/win32 is not problem for Japanese (and for
>> some other languages). Just using C locale with UTF-8 is enough in
>> this case.
>> 
>> In summary, I think you guys are going to overkill the multibyte
>> support functionality on UTF-8/win32 because of the fact that some
>> langauges do not work.
>> 
>> Same thing can be said to EUC-JP, EUC-CN and EUC-KR and so 
>on as well.
>> 
>> I strongly object the policy to try to unconditionaly disable UTF-8
>> support on win32.
>> --
>> Tatsuo Ishii
>> 
>> From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
>> Subject: RE: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 
>> Date: Sat, 1 Jan 2005 14:48:04 +0100
>> Message-ID: 
><6BCB9D8A16AC4241919521715F4D8BCE4764A4(at)algol(dot)sollentuna(dot)se>
>> 
>> > UNICODE/UTF-8 does not work on the win32 server. The reason is that
>> > strcoll() and friends don't work with it. To support it on 
>win32, it
>> > needs to be converted to UTF16 and use the wide-character 
>versions of
>> > the fucntion. Which we do not do.
>> > (See
>> > 
>http://archives.postgresql.org/pgsql-hackers-win32/2004-11/msg00036.php
>> > and
>> > 
>http://archives.postgresql.org/pgsql-hackers-win32/2004-12/msg0
>0106.php)
>> > 
>> > 
>> > I don't *think* we need to disable ito n the client. 
>AFAIK, the client
>> > interfaces don't use any of these functions, and I've seen 
>reports of
>> > people using that long before we had a native win32 server.
>> > 
>> > 
>> > //Magnus
>> > 
>> > 
>> > >-----Original Message-----
>> > >From: Tatsuo Ishii [mailto:t-ishii(at)sra(dot)co(dot)jp] 
>> > >Sent: den 1 januari 2005 01:10
>> > >To: tgl(at)sss(dot)pgh(dot)pa(dot)us
>> > >Cc: Magnus Hagander; pgsql-hackers-win32(at)postgresql(dot)org
>> > >Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 
>> > >
>> > >
>> > >Sorry, but I don't subscribe to pgsql-hackers-win32 list. 
>What's the
>> > >problem here?
>> > >--
>> > >Tatsuo Ishii
>> > >
>> > >> "Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
>> > >> > We know it's broken and won't be fixed for 8.0.
>> > >> 
>> > >> > If we just #ifndef WIN32 the definitions in 
>> > >utils/mb/encnames.c it won't
>> > >> > be possible to select that encoding, right? Will that have 
>> > >any other
>> > >> > unwanted effects (such as breaking client encodings)? If 
>> > >not, I suggest
>> > >> > this is done.
>> > >> 
>> > >> I believe the subscripts in those arrays have to match 
>the encoding
>> > >> enum type, so you can't just ifdef out individual entries.
>> > >> 
>> > >> > (Or perhaps something can be done in 
>pg_valid_server_encoding?)
>> > >> 
>> > >> Making the valid_server_encoding function reject it might work.
>> > >> Tatsuo-san would know for sure.
>> > >> 
>> > >> Should we also reject it as a client encoding, or does 
>that work OK?
>> > >> 
>> > >> 			regards, tom lane
>> > >> 
>> > >
>> > 
>> 
>> ---------------------------(end of 
>broadcast)---------------------------
>> TIP 1: subscribe and unsubscribe commands go to 
>majordomo(at)postgresql(dot)org
>> 
>
>-- 
>  Bruce Momjian                        |  http://candle.pha.pa.us
>  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
>  +  If your life is a hard drive,     |  13 Roberts Road
>  +  Christ can be your backup.        |  Newtown Square, 
>Pennsylvania 19073
>

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2005-02-22 21:20:24
Subject: Re: Design notes for BufMgrLock rewrite
Previous:From: Robert TreatDate: 2005-02-22 20:37:25
Subject: Re: [NOVICE] Question on TRUNCATE privleges

pgsql-hackers-win32 by date

Next:From: Nicolai TufarDate: 2005-02-22 21:39:54
Subject: Re: Repleacement for src/port/snprintf.c
Previous:From: Magnus HaganderDate: 2005-02-22 19:34:00
Subject: Re: 8.0.1 release performance on Window

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group