From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-translators@postgresql.org
Subject: Re: branching time
Date: Fri, 26 Apr 2019 12:50:06 -0400
Message-ID: <20190426165006.GA1273@alvherre.pgsql> (raw)
In-Reply-To: <dc7b60dd-da95-9ba2-1080-60e5d2b46a8e@2ndquadrant.com>
On 2019-Apr-12, Peter Eisentraut wrote:
> We branched last year around this time, I suggest we do the same again.
>
> I propose to do the branching in about a week, giving some time for
> committing anything before the branching.
Thanks for doing that. I managed to update my translation just in time \o/
The numbers have gone down in a pretty horrid way for this new branch,
and I suspect that \n removal (or something very similar) because of
frontend message centralization is the culprit. What about updating
translations centrally in some automated way? I think it's worth a
small programming effort (I think msgfilter can do that), since
otherwise translators are going to be overwhelmed.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-translators@postgresql.org
Cc: alvherre@2ndquadrant.com, peter.eisentraut@2ndquadrant.com
Subject: Re: branching time
In-Reply-To: <20190426165006.GA1273@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox