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

Re: UNICODE/UTF-8 on win32

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "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: UNICODE/UTF-8 on win32
Date: 2005-01-02 13:27:54
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE4764A9@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
>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.

The main issue is not with upper/lower, it's with ORDER BY (and doesn't
that affect indexes as well). This affects Japanese as well, no?

I didn't consider the C locale. Do you know for a fact that it works
there on win32 as well, or is that an assumption? (I don't know either
way)


>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.

I was under the impression that *no* languages worked. If some do work,
then we definitly should not kill it.

It would be good to have some way of detecting if it worked or not at
the time of creation of the database. But I have no idea on how to do
that in a reasonable way.


//Magnus

Responses

pgsql-hackers by date

Next:From: Marc G. FournierDate: 2005-01-02 14:56:09
Subject: PostgreSQL 8.0.0 Release Candidate 3
Previous:From: Tatsuo IshiiDate: 2005-01-02 11:55:55
Subject: Re: UNICODE/UTF-8 on win32

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2005-01-02 17:45:33
Subject: Re: UNICODE/UTF-8 on win32
Previous:From: Tatsuo IshiiDate: 2005-01-02 11:55:55
Subject: Re: UNICODE/UTF-8 on win32

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