Date: Tue, 7 May 2019 16:05:06 +0300
From: Pavlo Golub <pavlo.golub@gmail.com>
Reply-To: Pavlo Golub <pavlo.golub@gmail.com>
Message-ID: <9210009448.20190507160506@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>,
 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
CC: pgsql-translators@postgresql.org
Subject: Re: branching time
In-Reply-To: <20190426165006.GA1273@alvherre.pgsql>
References: <dc7b60dd-da95-9ba2-1080-60e5d2b46a8e@2ndquadrant.com>
 <20190426165006.GA1273@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hello fellows,

Friday, April 26, 2019, 7:50:06 PM, you wrote:

> 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.

I want to remind you that work in progress for Ukrainian language.
These are translated and reviewed.
https://redmine.postgresql.org/issues/4032

40% of all strings for PG11

> Thanks for doing that.  I managed to update my translation just in time \o/

I  want  to  add  UK to babel.postgresql.org for PG12 to finish before
official  release.

I  have request for European Portuguese as well. Guys will
start and we will see how thing are going.

> 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.


-- 
Best regards,
Pavlo Golub