Обсуждение: Re: Requesting an update from templates.

Hello there,

in trying to apply my own changes, submitted via pgfoundry,
to pg_ctl.po and pg_controldata.po, thus easing the burden
on the maintainer of translations, I stumbled on

  * the collection of msgid's contained in the Swedish
    po-files of the master branch are _NOT_ in sync with
    the master templates.

Do mend this status immediately, in order that I may
proceed to work on obtaining good coverage for Swedish.

I further recommend to implement some kind of semi-automatic
updating of all language files with the current template
messages, in order that other translators not be discuraged.

Best regards,
  Mats Erik Andersson, intending to improve the sv-catalogues.

Mats Erik Andersson wrote:
> Hello there,
>
> in trying to apply my own changes, submitted via pgfoundry,
> to pg_ctl.po and pg_controldata.po, thus easing the burden
> on the maintainer of translations, I stumbled on
>
>   * the collection of msgid's contained in the Swedish
>     po-files of the master branch are _NOT_ in sync with
>     the master templates.

This is normal.

What I do, as a translator(*), is to grab the merged files from babel,
which contain no difference in translations from the source files in
master (only merges to latest source code), and commit that.  This is a
mechanical but very bulky change with no interest.  Then translate that
file and commit separately.  This makes it easy for other people to
review the diffs, since human involvement only occurs in the second
commit.

We want to avoid spurious commits to the master branch, which is why
we don't do the first kind of commit separately.  At least, that's how I
see it.

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

måndag den 22 september 2014 klockan 18:55 skrev Alvaro Herrera detta:
> Mats Erik Andersson wrote:
> > Hello there,
> >
> > ...
> >
> >   * the collection of msgid's contained in the Swedish
> >     po-files of the master branch are _NOT_ in sync with
> >     the master templates.
>
> This is normal.
>
> What I do, as a translator(*), is to grab the merged files from babel,
> which contain no difference in translations from the source files in
> master (only merges to latest source code), and commit that.  This is a
> mechanical but very bulky change with no interest.  Then translate that
> file and commit separately.  This makes it easy for other people to
> review the diffs, since human involvement only occurs in the second
> commit.
>
> We want to avoid spurious commits to the master branch, which is why
> we don't do the first kind of commit separately.  At least, that's how I
> see it.

Fair enough, I will follow this path. Hence the only merit of this
thread is to preserve the suggestion as guide for other interested
parties. Also this is good to have on record.

Best regards,
  Mats Erik Andersson