Date: Fri, 12 May 2023 09:48:40 +0000 (UTC)
From: Domenico Sgarbossa <sbraaaa@yahoo.it>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
	Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: "pgsql-translators@postgresql.org" <pgsql-translators@postgresql.org>
Message-ID: <1376171153.235165.1683884920908@mail.yahoo.com>
In-Reply-To: <20230511180709.qlkfk5dnfvsofyf6@alvherre.pgsql>
References: <48ea72af-c0f6-1cc2-c0df-ff3787424c9e@enterprisedb.com>
 <20230511180709.qlkfk5dnfvsofyf6@alvherre.pgsql>
Subject: Re: branching time
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 1206
Archived-At: 
 <https://www.postgresql.org/message-id/1376171153.235165.1683884920908%40mail.yahoo.com>
Precedence: bulk

Could we start to fix them right now?
I mean: are those files to be considered stable?


Il gioved=C3=AC 11 maggio 2023 alle ore 20:07:19 CEST, Alvaro Herrera <alvh=
erre@alvh.no-ip.org> ha scritto:=20


PSA: there's a lot of translation percentages going heavily down in the
branch for v16, especially in pg_upgrade and libpq.=C2=A0 Many of those are
just changes in newlines.=C2=A0 It's very easy to update these automaticall=
y,
using the scripts from 2019:
https://postgr.es/m/20190428173733.GA12483@alvherre.pgsql

I suggest to first run Dennis' Python script over each file, then run
mine.=C2=A0 Dennis only changes single-line messages, but is able to remove
the 'fuzzy' marking; my approach can process multi-line messages, but
you need to remove the 'fuzzy' mark manually.

Some messages have lost *two* consecutive \n\n (in pg_upgrade).=C2=A0 For
those, you can modify my script to handle that case.=C2=A0 I didn't try, bu=
t
it should be easy.

This can save you quite a lot of manual work.

--=20
=C3=81lvaro Herrera=C2=A0 =C2=A0 =C2=A0 =C2=A0 Breisgau, Deutschland=C2=A0 =
=E2=80=94=C2=A0 https://www.EnterpriseDB.com/
Si no sabes adonde vas, es muy probable que acabes en otra parte.