Re: upper()/lower() truncates the result under Japanese Windows - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: upper()/lower() truncates the result under Japanese Windows
Date
Msg-id 4946D7F2.3070908@tpf.co.jp
Whole thread Raw
In response to Re: upper()/lower() truncates the result under Japanese Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Hiroshi Inoue <inoue@tpf.co.jp> writes:
>> Upper(), lower() or initcap() function truncates the result
>> under Japanese Windows with e.g. the server encoding=UTF-8
>> and the LC_CTYPE setting Japanese_japan.932 .
> 
> Hmm, I guess that makes sense, since the LC_CTYPE implies an encoding
> other than UTF-8; MB_CUR_MAX should be set according to LC_CTYPE.
> 
> The proposed patch seems pretty ugly though.  Why don't we just stop
> using MB_CUR_MAX altogether?  These three functions are the only
> references to it AFAICS.

Although it looks ugly, it only follows what wchar2char() does.
Though I don't like to use MB_CUR_MAX, it seems safe as long as
wchar2char() calls wcstombs().

regards,
Hiroshi Inoue




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] odd output in restore mode
Next
From: Simon Riggs
Date:
Subject: Re: [PATCHES] odd output in restore mode