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

From Chapman Flack
Subject Re: Mac OS: invalid byte sequence for encoding "UTF8"
Date
Msg-id 56BC1350.2040909@anastigmatix.net
Whole thread Raw
In response to Re: Mac OS: invalid byte sequence for encoding "UTF8"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Mac OS: invalid byte sequence for encoding "UTF8"
List pgsql-hackers
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.

http://unicode.org/standard/reports/tr13/tr13-5.html
http://unicode.org/charts/PDF/U0080.pdf

-Chap



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)
Next
From: Tom Lane
Date:
Subject: Re: Mac OS: invalid byte sequence for encoding "UTF8"