Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [HACKERS] UNICODE/UTF-8 on win32
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "John Hansen" <john(at)geeknet(dot)com(dot)au>
- 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: [HACKERS] UNICODE/UTF-8 on win32
- Date: Fri, 25 Feb 2005 13:25:35 -0500
- Message-id: <6918(dot)1109355935(at)sss(dot)pgh(dot)pa(dot)us>
"John Hansen" <john(at)geeknet(dot)com(dot)au> writes: >> "It fails on my machine" should not be read as "it doesn't >> work for anyone". >> It all depends on how your local mbstowcs() works. > Ok,... Do you have an example of a system on which it works? 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 ;-). Nonetheless, it's clear that in C locale mbstowcs cannot be buying us anything compared to using the old <ctype.h> macros, so I'm fine with adding a check on the locale as per previous discussion. regards, tom lane
- References:
- Re: [HACKERS] UNICODE/UTF-8 on win32
- From: John Hansen
- Re: [HACKERS] UNICODE/UTF-8 on win32
- Prev by Date: Re: [HACKERS] UNICODE/UTF-8 on win32
- Next by Date: Re: [HACKERS] UNICODE/UTF-8 on win32
- Previous by thread: Re: [HACKERS] UNICODE/UTF-8 on win32
- Next by thread: Re: [HACKERS] UNICODE/UTF-8 on win32
- Indexes: