Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXwHb-0004ld-3d for pgsql-bugs@arkaria.postgresql.org; Fri, 14 Dec 2018 22:50:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gXwHZ-0000f1-Fr for pgsql-bugs@arkaria.postgresql.org; Fri, 14 Dec 2018 22:50:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXwHZ-0000UJ-4T for pgsql-bugs@lists.postgresql.org; Fri, 14 Dec 2018 22:50:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gXwHW-0007Ln-Al for pgsql-bugs@lists.postgresql.org; Fri, 14 Dec 2018 22:50:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id wBEMo3Zh016727; Fri, 14 Dec 2018 17:50:03 -0500 From: Tom Lane To: Hugh Ranalli cc: Daniel Verite , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15548: Unaccent does not remove combining diacritical characters In-reply-to: References: <10200.1544713542@sss.pgh.pa.us> <5d77cc08-d582-4f83-a17f-f2c992d123a9@manitou-mail.org> Comments: In-reply-to Hugh Ranalli message dated "Fri, 14 Dec 2018 17:42:05 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <16725.1544827803.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 14 Dec 2018 17:50:03 -0500 Message-ID: <16726.1544827803@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hugh Ranalli writes: > I've attached a patch removes combining diacriticals. As with Latin and > Greek letters, it uses ranges to restrict its activity. Cool. Please add it to the current CF so we don't forget about it: https://commitfest.postgresql.org/21/ > I have not submitted a patch for unaccent.rules, as it seems that a rules > file generated from generate_unaccent_rules.py will actually remove a large > number of rules (even before my changes), such as replacing the copyright > symbol © with (C), as well as other accented characters. It's probably > worth asking if the shipped unaccent.rules should correspond to what the > shipped generation utility produces, or not. I was surprised to see that it > didn't. Me too -- seems like that bears looking into. Perhaps the script's results are platform dependent -- what were you testing on? regards, tom lane