Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC
Date
Msg-id 20250420125322.0b.nmisch@google.com
Whole thread Raw
In response to Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Sat, Apr 19, 2025 at 12:30:57PM -0700, Jeff Davis wrote:
> On Thu, 2025-04-17 at 06:58 -0700, Noah Misch wrote:
> > Should initcap_wbnext() pass in a locale-dependent "bool posix"
> > argument like
> > the others calls the commit changed?
> 
> Yes, I believe you are correct. Patch and tests attached.

That patch is ready for commit.

> > Long-term, pg_u_isword() should have a "bool posix" argument. 
> > Currently, only
> > tests call that function.  If it got a non-test caller,
> > https://www.unicode.org/reports/tr18/#word would have pg_u_isword()
> > follow the
> > choice of posix compatibility like pg_u_isalnum() does.
> 
> I based those functions on:
> 
> https://www.unicode.org/reports/tr18/#Compatibility_Properties
> 
> and the "word" class does not have a POSIX variant.

I missed that distinction.  I withdraw this part.



pgsql-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Next
From: Alexander Lakhin
Date:
Subject: Re: AIO v2.5