From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <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-25 18:38:29 |
Message-ID: | 5066E5A966339E42AA04BA10BA706AE5625E@rodrick.geeknet.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
> On HPUX 10.20, mbstowcs seems to treat all byte values as
> single-byte characters in C locale, so my sample-of-one says
> that it works everywhere ;-).
Right, so for the sample SQL I sent earlier, the result would be the same as the input?
That's hardly a working upper/lower....
If a character doesn't have case then fine, but one that does, should at least produce a warning if it cannot be converted.
... John
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-02-25 19:17:42 | Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 |
Previous Message | Bruce Momjian | 2005-02-25 18:36:57 | Re: UTF8 or Unicode |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-02-25 19:17:42 | Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 |
Previous Message | Tom Lane | 2005-02-25 18:25:35 | Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32 |