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 1gYHMI-0005rO-Gd for pgsql-bugs@arkaria.postgresql.org; Sat, 15 Dec 2018 21:20:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gYHMF-0000o7-Sb for pgsql-bugs@arkaria.postgresql.org; Sat, 15 Dec 2018 21:20:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gYHMF-0000nz-MC for pgsql-bugs@lists.postgresql.org; Sat, 15 Dec 2018 21:20:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gYHM7-0001gq-GN for pgsql-bugs@lists.postgresql.org; Sat, 15 Dec 2018 21:20:22 +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 wBFLKBMP029420; Sat, 15 Dec 2018 16:20:11 -0500 From: Tom Lane To: Hugh Ranalli cc: Daniel Verite , thomas.munro@enterprisedb.com, 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> <16726.1544827803@sss.pgh.pa.us> <23237.1544899488@sss.pgh.pa.us> Comments: In-reply-to Hugh Ranalli message dated "Sat, 15 Dec 2018 16:03:33 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29418.1544908811.1@sss.pgh.pa.us> Date: Sat, 15 Dec 2018 16:20:11 -0500 Message-ID: <29419.1544908811@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hugh Ranalli writes: > The problem is that I downloaded the latest version of the Latin-ASCII > transliteration file (r34 rather than the r28 specified in the URL). Over 3 > years ago (in r29, of course) they changed the file format ( > https://unicode.org/cldr/trac/ticket/5873) so that > parse_cldr_latin_ascii_transliterator loads an empty rules set. Ah-hah. > I'd be > happy to either a) support both formats, or b), support just the newest and > update the URL. Option b) is cleaner, and I can't imagine why anyone would > want to use an older rule set (then again, struggling with Unicode always > makes my head hurt; I am not an expert on it). Thoughts? (b) seems sufficient to me, but perhaps someone else has a different opinion. Whichever we do, I think it should be a separate patch from the feature addition for combining diacriticals, just to keep the commit history clear. regards, tom lane