Date: Fri, 4 Jan 2019 22:00:48 +0900
From: Michael Paquier <michael@paquier.xyz>
To: Hugh Ranalli <hugh@whtc.ca>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>,
	Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
	thomas.munro@enterprisedb.com,
	Daniel Verite <daniel@manitou-mail.org>,
	pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15548: Unaccent does not remove combining diacritical
 characters
Message-ID: <20190104130048.GD2067@paquier.xyz>
References: <201901031819.hi4hjki2pzr5@alvherre.pgsql>
 <23619.1546539744@sss.pgh.pa.us>
 <CAAhbUMMrNL9uXXpwS+BPTGjKQv5Sxvr+OY2C73Ag7oFyjSOiEQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="6Nae48J/T25AfBN4"
Content-Disposition: inline
In-Reply-To: 
 <CAAhbUMMrNL9uXXpwS+BPTGjKQv5Sxvr+OY2C73Ag7oFyjSOiEQ@mail.gmail.com>
Precedence: bulk


--6Nae48J/T25AfBN4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 03, 2019 at 04:48:33PM -0500, Hugh Ranalli wrote:
> On Thu, 3 Jan 2019 at 13:22, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>>> I think the point is that if the committee updates with a further
>>> version of the file, how do you find the new version?  We need a URL
>>> that's one step removed from the final file, so that we can see if we
>>> need to update it.  Maybe we can provide both URLs for convenience.
>>
>> +1.  Could be phrased along the lines of "documents are at URL1,
>> currently synced with URL2" so that it's clear that URL2 should
>> be updated when we re-sync with a newer release.
>>
>=20
> Yes, this is what I was thinking. I was integrating this into my installe=
r,
> used the "new" URL provided to download the file, and spent several minut=
es
> wondering why the script was failing (and what I had broken in it), before
> realising what had happened.

I think that we could just use the URLs I am mentioning here:
https://www.postgresql.org/message-id/20181227064958.GK2106@paquier.xyz

I haven't been able to finish what I wanted for the proposed patch set
yet, but what I was thinking about is to include:
1) The root URL where all the release folders are present
2) The full URL of the current Latin-ASCII.xml being used for the
generation, not as a URL pointing to the latest version, but as a URL
pointing to an exact version in time (I doubt that a released version
never changes in this tree, but who knows..).
3) The version used to generate the rules.
--
Michael

--6Nae48J/T25AfBN4
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlwvWQAACgkQnvQgOdby
QH29bw/9EgF5hott3NBtQ5ZcBiueVVfqYf12pMdtVCrO+aqyHH8REMFacOI206+y
vijpyQj6hgK8XhGfGnHgeuHtveRjtfgWO0yg6WvwirLPeS5MfJsczT0zxKiBL8VR
16hxHihyKGMuVkYcCmBbDUv69PlvbQR7bwzFZOIhcEc1IYp6yKZ95SXfHKFfiQzt
b7d+jx78XDAbiGlOni2ykAEJcDTwaUt7ZEHVjWrtksZINKm9ceLndKVGdiAzrDws
V51y/0v5PjZ2QFPTWRxxaotWxBWHl9Jmab18YIJfE2Sg8Ld0QRzeFsRST7aPa0Yo
59rnhxnOgf3jFHu2ngghnBZfnULuFO+UPxgU/iBVcTKCY80ouWLzivf2fShdF1mx
lvW4cfW11JiZ1hQ+UvhLKcPZalm9sBV4/OwyJrJCBqEQrIFW8/MMheRYAQErvwSL
yGtJNSDm7XOyYmy0phUJ80ymlT5XakseAbgfpTkZn5Gh0Y4d4gKGxL3z0CoWNNfR
qBTMhLM1iy+0AIZ4IVKlzEIhJPDgBASb4B7SdLGZ/uZklgiFM09jRji7mqok7gUn
ScKuNTR37/pAGeL4pY3t0PoxX8tD2wyCA2S4ffPsbEZjwHd/3i9wKmic/fGS0Bio
V0kxHQ0hoETaccXmXmgkGBmdlOx/MQNItFiFqYXXRcJXskcpiMo=
=oUQR
-----END PGP SIGNATURE-----

--6Nae48J/T25AfBN4--