Re: Mac OS: invalid byte sequence for encoding "UTF8" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Mac OS: invalid byte sequence for encoding "UTF8"
Date
Msg-id 4194.1455166527@sss.pgh.pa.us
Whole thread Raw
In response to Re: Mac OS: invalid byte sequence for encoding "UTF8"  (Chapman Flack <chap@anastigmatix.net>)
Responses Re: Mac OS: invalid byte sequence for encoding "UTF8"
List pgsql-hackers
Chapman Flack <chap@anastigmatix.net> writes:
> On 02/10/16 17:19, Tom Lane wrote:
>> I also verified that in UTF8-based locales, isspace() thinks that 0x85 and
>> 0xA0, and no other high-bit-set values, are spaces.  Not sure exactly why

> Unicode NEXT LINE (NEL) and NO-BREAK SPACE, respectively.

Yeah, I got that --- what seems squishier is that none of the other C1
control characters are considered whitespace?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: Mac OS: invalid byte sequence for encoding "UTF8"
Next
From: Chapman Flack
Date:
Subject: Re: Mac OS: invalid byte sequence for encoding "UTF8"