Re: BUG #15548: Unaccent does not remove combining diacritical characters
Hugh Ranalli <hugh@whtc.ca>
From: Hugh Ranalli <hugh@whtc.ca>
To: thomas.munro@enterprisedb.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Verite <daniel@manitou-mail.org>, pgsql-bugs@lists.postgresql.org
Date: 2018-12-17T20:22:37Z
Lists: pgsql-bugs, pgsql-hackers
On Sat, 15 Dec 2018 at 21:26, Thomas Munro <thomas.munro@enterprisedb.com> wrote: > +1 for updating to the latest file from time to time. After > http://unicode.org/cldr/trac/ticket/11383 makes it into a new release, > our special_cases() function will have just the two Cyrillic > characters, which should almost certainly be handled by adding > Cyrillic to the ranges we handle via the usual code path, and DEGREE > CELSIUS and DEGREE FAHRENHEIT. Those degree signs could possibly be > extracted from Unicode.txt (or we could just forget about them), and > then we could drop special_cases(). > Well, when I modified the code to handle the new version of the transliteration file, I discovered that was sufficient to handle the old version as well. That's not the way things usually go, but I'll take it. ;-) I've attached two patches, one to update generate_unaccent_rules.py, and another that updates unaccent.rules from the v34 transliteration file. I'll be happy to add these to the CF. Does anyone need to review them and give me approval before I do so? Best wishes, Hugh
Commits
-
Fix unaccent generation script in Windows
- 0afc0a784188 13.0 landed
-
Add combining characters to unaccent.rules.
- 456e3718e7b7 12.0 landed
-
Update unaccent rules with release 34 of CLDR for Latin-ASCII.xml
- e1c1d5444e43 12.0 landed
-
unaccent: Make generate_unaccent_rules.py Python 3 compatible
- 3d59da9ccdb9 12.0 landed
-
Convert unaccent tests to UTF-8
- b6f3649bba98 12.0 landed