Re: BUG #18362: unaccent rules and Old Greek text

Cees van Zeeland <cees.van.zeeland@freedom.nl>

From: Cees van Zeeland <cees.van.zeeland@freedom.nl>
To: Michael Paquier <michael@paquier.xyz>, Thomas Munro <thomas.munro@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2024-02-26T12:33:28Z
Lists: pgsql-bugs
Thomas Munro <thomas.munro@gmail.com> wrote:
 >    If I tell the script to follow such "simple" redirections, I
 >   get over a thousand new mappings, including those.  See attached.
 >   There is probably more correct terminology that I'm using here...

Michael Paquier wrote:
 > It seems to me that it is a bit more complicated than that, because
 > Unicode.data decomposes the characters with Oxia as characters with
 > Tonos, and then characters with Tonos are decomposed with the "base"
 > alphabet characters + Tonos.  We do a recursive lookup at the unicode
 > table in get_plain_letter() and is_letter_with_marks(), so it seems to
 > me that we're not missing much, and I suspect that there should be no
 > need for a new custom range of characters..
 >
 > Cees, perhaps you would like to get a shot at that?
 >
 > [1]: https://en.wikipedia.org/wiki/Greek_diacritics#Unicode

I'm not an expert, but obviously computers make a difference between the 
two versions of the characters.
We are talking about this series:
U+1F70 - U+1F7D:    ὰ     ά     ὲ     έ     ὴ     ή     ὶ     ί ὸ     ό 
     ὺ     ύ     ὼ     ώ
Is it possible to filter / limit in some way the redirection in the 
script to this range?

~
Cees


Commits

  1. Add simple codepoint redirections to unaccent.rules.