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

From Magnus Hagander
Subject Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE4764A9@algol.sollentuna.se
Whole thread Raw
Responses Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
List pgsql-hackers
>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

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Next
From: Tom Lane
Date:
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32