From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | pgsql-translators(at)postgresql(dot)org |
Subject: | Re: branching time |
Date: | 2023-05-11 18:07:09 |
Message-ID: | 20230511180709.qlkfk5dnfvsofyf6@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-translators |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Domenico Sgarbossa | 2023-05-12 09:48:40 | Re: branching time |
Previous Message | Peter Eisentraut | 2023-04-24 09:42:53 | Re: Oddities in NLS Status Tables |