Re: branching time

From: Domenico Sgarbossa <sbraaaa(at)yahoo(dot)it>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: "pgsql-translators(at)postgresql(dot)org" <pgsql-translators(at)postgresql(dot)org>
Subject: Re: branching time
Date: 2023-05-12 09:48:40
Message-ID: 1376171153.235165.1683884920908@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-translators

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

Il giovedì 11 maggio 2023 alle ore 20:07:19 CEST, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> ha scritto:

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.

In response to

Responses

Browse pgsql-translators by date

  From Date Subject
Next Message Alvaro Herrera 2023-05-12 10:56:30 Re: branching time
Previous Message Alvaro Herrera 2023-05-11 18:07:09 Re: branching time