--On söndag, maj 08, 2005 22.19.25 +0900 Tatsuo Ishii <[EMAIL PROTECTED]> wrote:
> > > On Sun, May 08, 2005 at 02:07:29PM +1000, John Hansen wrote: > > > > Tatsuo Ishii wrote: > > > > > > > > So Japanese(including ASCII)/UNICODE behavior is > > > perfectly correct > > > > > at this moment. > > > > > > > > Right, so you _never_ use accented ascii characters in > Japanese? > > > > (like è for example, whose uppercase is È) > > > > > > That isn't ASCII. It's latin1 or some other ASCII extension. > > > > Point taken... > > But... > > > > If you want EUC_JP (Japanese + ASCII) then use that as your > backend encoding, not UTF-8 (unicode). > > UTF-8 encoded databases are very useful for representing multiple > > languages in the same database, but this usefulness > vanishes if functions like upper/lower doesn't work correctly. > > I'm just curious if Germany/French/Spanish mixed text can be > sorted correctly. I think these languages need their own > locales even with UNICODE/ICU.
No, they will not sort correctly, for that you still need the locale.
I'm confused. I thought the ICU patches is intended for using on broken locale platforms?
It will sort correctly in *one* locale, using ICU. You still cannot mix different locales in the same database cluster, the collation locale is still fixed at initdb time, unfortunately.
/Palle
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
