Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-hackers-win32] 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: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Date: 2005-02-25 18:25:35
Message-ID: 6918.1109355935@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-win32
"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

In response to

pgsql-hackers by date

Next:From: Jeff DavisDate: 2005-02-25 18:26:55
Subject: Re: idea for concurrent seqscans
Previous:From: Marc G. FournierDate: 2005-02-25 18:21:21
Subject: Re: [pgsql-hackers] Daily digest v1.4988 (21 messages)

pgsql-hackers-win32 by date

Next:From: John HansenDate: 2005-02-25 18:38:29
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Previous:From: John HansenDate: 2005-02-25 18:17:48
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group