Date: Fri, 26 Apr 2019 14:14:03 -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: <20190426181403.GA10450@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20190426165006.GA1273@alvherre.pgsql>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Apr-26, Alvaro Herrera wrote:

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

I think it's quite possible to do this with msgfilter ... but you need
to read the 'info' documentation, not the 'man' documentation, because
the latter is completely useless.

I think we need to write a filter program that compares MSGFILTER_MSGID
to MSGFILTER_PREV_MSGID, and if the only difference is the leading "%s: " 
and the trailing "\n", then strip those thing from stdin and write that
to stdout.  Then invoke that filter for every .po in the new branch.
That should restore the translated percentages to much better values,
raising morale.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services