Feedback-ID: ia2694551:Fastmail
Date: Thu, 11 May 2023 20:07:09 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-translators@postgresql.org
Subject: Re: branching time
Message-ID: <20230511180709.qlkfk5dnfvsofyf6@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <48ea72af-c0f6-1cc2-c0df-ff3787424c9e@enterprisedb.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20230511180709.qlkfk5dnfvsofyf6%40alvherre.pgsql>
Precedence: bulk

PSA: there's a lot of translation percentages going heavily down in the
branch for v16, especially in pg_upgrade and libpq.  Many of those are
just changes in newlines.  It's very easy to update these automatically,
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.  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).  For
those, you can modify my script to handle that case.  I didn't try, but
it should be easy.

This can save you quite a lot of manual work.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
Si no sabes adonde vas, es muy probable que acabes en otra parte.