Date: Fri, 26 Apr 2019 12:50:06 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-translators@postgresql.org
Subject: Re: branching time
Message-ID: <20190426165006.GA1273@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <dc7b60dd-da95-9ba2-1080-60e5d2b46a8e@2ndquadrant.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

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