Обсуждение: Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC

Поиск
Список
Период
Сортировка

Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC

От
Jeff Davis
Дата:
On Fri, 2025-01-10 at 16:36 -0800, Jeff Davis wrote:
> On Mon, 2024-12-16 at 12:49 -0800, Jeff Davis wrote:
> > On Wed, 2024-12-11 at 15:52 -0800, Jeff Davis wrote:
> > > Attached is a series of patches to implement full case mapping as
> > > the
> > > locale PG_UNICODE_FAST.
> >
> > Rebased and attached.
>
> Rebased and attached v3.

I plan to commit 0001 and 0002 soon. There seems to be general
agreement that we want full case mapping[1], and we can potentially use
the infrastructure to extend the additional case variants into pattern
matching[2].

0003 requires more discussion.

Regards,
    Jeff Davis

[1]https://www.postgresql.org/message-id/27bb0e52-801d-4f73-a0a4-02cfdd4a9ada@eisentraut.org
[2]
https://www.postgresql.org/message-id/c10ed44c7e5dcbb7b4597889f02d029298f0c919.camel@j-davis.com




Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC

От
Jeff Davis
Дата:
On Wed, 2025-01-15 at 13:21 -0800, Jeff Davis wrote:
> I plan to commit 0001 and 0002 soon.

Committed 0001 and 0002.

Upon reviewing the discussion threads, I removed the Unicode "adjust to
Cased" behavior when titlecasing. As Peter pointed out[1], it doesn't
match the documentation or expectations for INITCAP().

I also expanded the C tests a lot in 0001 so that it compares
exhaustively against ICU for single-codepoint strings, and also added
more multi-codepoint test strings.

I don't plan to commit 0003 in v18, so I'm considering this series to
be done for now. We can revisit whether UCS_BASIC should change
behavior in 19.

Regards,
    Jeff Davis




Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC

От
Jeff Davis
Дата:
On Fri, 2025-01-17 at 16:06 -0800, Jeff Davis wrote:
> Upon reviewing the discussion threads, I removed the Unicode "adjust
> to
> Cased" behavior when titlecasing. As Peter pointed out[1], it doesn't
> match the documentation or expectations for INITCAP().

Forgot to add a link to the discussion. Here are some relevant
messages:

https://www.postgresql.org/message-id/4c9eea58-08a1-4629-a004-439e2cf12de8%40eisentraut.org
https://www.postgresql.org/message-id/610d7f1b-c68c-4eb8-a03d-1515da304c58%40manitou-mail.org

Regards,
    Jeff Davis