Re: [PATCH] Completed unaccent dictionary with many missing characters - Mailing list pgsql-hackers

From Przemysław Sztoch
Subject Re: [PATCH] Completed unaccent dictionary with many missing characters
Date
Msg-id ee5e0b6f-2a1c-a15c-041e-70208d4a0d86@sztoch.pl
Whole thread Raw
In response to Re: [PATCH] Completed unaccent dictionary with many missing characters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Completed unaccent dictionary with many missing characters  (Michael Paquier <michael@paquier.xyz>)
List 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

pgsql-hackers by date:

Previous
From: Przemysław Sztoch
Date:
Subject: Re: [PATCH] Completed unaccent dictionary with many missing characters
Next
From: Przemysław Sztoch
Date:
Subject: Re: Re: Add --{no-,}bypassrls flags to createuser