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

Przemysław Sztoch <przemyslaw@sztoch.pl>

From: Przemysław Sztoch <przemyslaw@sztoch.pl>
To: pgsql-hackers@lists.postgresql.org
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Date: 2022-05-05T19:44:15Z
Lists: pgsql-hackers
Tom Lane wrote on 5/4/2022 5:32 PM:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> On 28.04.22 18:50, Przemysław Sztoch wrote:
>>> Current unnaccent dictionary does not include many popular numeric symbols,
>>> in example: "m²" -> "m2"
>> Seems reasonable.
> It kinda feels like this is outside the charter of an "unaccent"
> dictionary.  I don't object to having these conversions available
> but it seems like it ought to be a separate feature.
>
> 			regards, tom lane
Tom, I disagree with you because many similar numerical conversions are 
already taking place, e.g. 1/2, 1/4...

Today Unicode is ubiquitous and we use a lot more weird characters.
I just completed these less common characters.

Therefore, the problem of missing characters in unaccent.rules affects 
the correct operation of the FTS mechanisms.
-- 
Przemysław Sztoch | Mobile +48 509 99 00 66

Commits

  1. Simplify a bit the special rules generating unaccent.rules