Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qXVpF-006RX8-Uy for pgsql-bugs@arkaria.postgresql.org; Sat, 19 Aug 2023 23:57:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qXVpC-002gsv-GM for pgsql-bugs@arkaria.postgresql.org; Sat, 19 Aug 2023 23:57:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qXVpA-002gsl-Sx for pgsql-bugs@lists.postgresql.org; Sat, 19 Aug 2023 23:57:46 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qXVp6-0018SB-B3 for pgsql-bugs@lists.postgresql.org; Sat, 19 Aug 2023 23:57:44 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id B68F1320070D; Sat, 19 Aug 2023 19:57:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 19 Aug 2023 19:57:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1692489456; x=1692575856; bh=uT mGV4yVF49a1b1Kh1H/YA9yAjRUOxoBx0P3+iWii8s=; b=FFuTftbSlgo0DWLfyz NaWvqsbHUWFi/nl5xcwUVL/DjFHFZJLfTpC+nIpLhX9pT4wBa0NwWz9hDK5V9WiV C0+Lh/KgPVRNOnXIvtUEk/AV+abMqEtAL20F3mhvZNNqtaZ9glcvfmj18e3MFQ9c 8kZ9pg9BAPNGeQbKrMR/bJzwtQShwdpjwz8v2i0EAIfsqIjsN9vbGhtBeLJKsztu uvci5t/rg4AahJOie3wq6hskGdktM30xAdt3s3ELabVErfiII/zSsjJrEdThNq7c rmFIQzxSAW7ResMXf/Jya6dsyxOwxT3XrlCOYuXhiefOiJR5LuQU3sldxLk/ECfL iYtg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1692489456; x=1692575856; bh=uTmGV4yVF49a1 b1Kh1H/YA9yAjRUOxoBx0P3+iWii8s=; b=x3N5v8GsMlU9GYCpFrIpIUVIcXXK4 gQpSiHHJkqAnmpgw8v8E001G9XfMxYyDse44rCrj6aIRm0NORbv+y7SSry0/5bBa z16xlEmz66xBsWURO6DQ6mMfKLHSTNigtw4CeQwzk6t8L41UANX87j4AlAZYoUhz f0lPf+XZ/9AEjLvaig1Ws86Y9rgwWtkXXq/cKfy+ZKFYDwSawCw2QnQ3R86ST8Ke PzN5Dy/PUzvyS6AqCTCTdCeRu3CUje68LRaUFVXyHrodfVU5yqWsHUv30xBvFU/N V+knCSszLCILL81NZd5aZaYPOmg1k45N2qPeDKYa4IgUuoMEg0paCKOXg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudduiedgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdljedtmdenucfjughrpeffhf fvvefukfhfgggtuggjsehgtderredttdejnecuhfhrohhmpefoihgthhgrvghlucfrrghq uhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvg hrnhepveetjefgjeevgedukeehieeuieeuieevueeiudegheevuefggfduueelgeelieet necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitg hhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 19 Aug 2023 19:57:34 -0400 (EDT) Date: Sun, 20 Aug 2023 08:57:29 +0900 From: Michael Paquier To: Tom Lane Cc: martin@schlossarek.me, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18057: unaccent removes intentional spaces Message-ID: References: <18057-62712cad01bd202c@postgresql.org> <2334732.1692462604@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u03DBbeRIneOLEAT" Content-Disposition: inline In-Reply-To: <2334732.1692462604@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --u03DBbeRIneOLEAT Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 19, 2023 at 12:30:04PM -0400, Tom Lane wrote: > Yeah, we could extend the parsing rules that way. It would break > any rules files that currently use double quote as a plain character, > but it seems unlikely that there are any. In any case, as long as > this wasn't back-patched I think such a change would be acceptable. Okay, thanks. Note that we do use double-quotes as a translated character in a few cases, but as long as these are only handled as a single character we could be OK. Or actually, wouldn't it be better to always force escaping even for double quotes listed as single characters? Based on what unaccent.rules has, that's not necessary, but it could simplify the python code generating the file or the C parsing. For example, the existing '=E2=80=9D' would become listed as "\""= in our unaccent.rules. -- Michael --u03DBbeRIneOLEAT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmThVukACgkQnvQgOdby QH1wMg/+J3/YtIoXYbN7DjAPmfzJw9LjOddIlLmZ6x7VTQi1NkJuQ62G64JQgjxc MVQZehOdqrdOkvDNvPrYEMoWsek3r2CfP3uqABom2i/kDODVarz5J3TPUIYhx7q/ DnNsLhMQKvxZDo0UdRkpQpIMlI9oGKDxqD2wGVfF8PLvoCjqkK6J1o9QFWYf16eL wtR0VE4J9VUBTasrD59TpVCyr4s4PuBL2yerM8azK8hUAg2neukzmZRQgRadsvNG OxM+VFGACPPQumZMEJugYvF36FwZ0hxQwG4QgtgKbHYC/Nybaa49txxcNS1rUt+R /j8m0o3NRpJlWeR7LS6LN2FxjXEENxgpBuIgApv/h/18SK8uOrbU3JrCZb7yG2gj kns8d29xp/QaeBwUlymSygOtDqEMpLkxYrieIbnOvPNg+6glbuZ5YbY7pxfzSsi2 YmpNJAEDtWvuHvxwp7BscGuFGXjMDij5hiZ7ri4QvyXeBo7NDYQFHNmEzQ8nAvXK IFKnISj3VojU4Ka4+t1Lm92CT1NFmdFCn3MP7vbsCa9HxxAfhHZJoM54BP/OKDhL fwllGJQKEUs59iV+ClmFHECP/t/NJdcLyFHJakBY7wKdY8YG+tQTeIma8o+VVA8G OIfGBrwfwp9rPn41L1cWEY3Bhy0+YjsvQZLiILGAKlZ4fJ89hwY= =NNhb -----END PGP SIGNATURE----- --u03DBbeRIneOLEAT--