Re: [PATCH] Completed unaccent dictionary with many missing characters

From: Przemysław Sztoch <przemyslaw(at)sztoch(dot)pl>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Subject: Re: [PATCH] Completed unaccent dictionary with many missing characters
Date: 2022-07-13 10:12:43
Message-ID: b37f4698-9a83-1c19-48f0-6bee0fa07b0a@sztoch.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Michael P.,
> 3. The matter is not that simple. When I change priorities (ie
> Latin-ASCII.xml is less important than Unicode decomposition),
> then "U + 33D7" changes not to pH but to PH.
> In the end, I left it like it was before ...
>
> If you decide what to do with point 3, I will correct it and send new
> patches.
What is your decision?
Option 1: We leave x as in Latin-ASCII.xml and we also have full
compatibility with previous PostgreSQL versions.
If they fix Latin-ASCII.xml at Unicode, it will fix itself.

Option 2:  We choose a lower priority for entries in Latin-ASCII.xml

I would choose option 1.

P.S. I will be going on vacation and it would be nice to close this
patch soon. TIA.

--
Przemysław Sztoch | Mobile +48 509 99 00 66

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-07-13 10:28:30 Re: CREATE TABLE ( .. STORAGE ..)
Previous Message houzj.fnst@fujitsu.com 2022-07-13 09:57:35 Collect ObjectAddress for ATTACH DETACH PARTITION to use in event trigger