Re: pgsql: Re-add translation markers that were lost - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Re-add translation markers that were lost
Date
Msg-id CAB7nPqStQ39MWNCA0XuFufo8Gko2YWEKydLokwE7YkbHxfRQcg@mail.gmail.com
Whole thread Raw
In response to pgsql: Re-add translation markers that were lost  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-committers
On Wed, Sep 21, 2016 at 1:56 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> Re-add translation markers that were lost
>
> When win32security.c was moved from src/backend/port/win32/security.c,
> the message writing function was changed from write_stderr to log_error,
> but nls.mk was not updated.  We could add log_error to GETTEXT_TRIGGERS,
> but it's also used in src/common/exec.c in a different way and that
> would create some confusion or a larger patch.  For now, just put an
> explicit translation marker onto the strings that were previously
> translated.

Thanks for the workaround.
--
Michael


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: pg_restore: Add -N option to exclude schemas
Next
From: Heikki Linnakangas
Date:
Subject: pgsql: Print test parameters like "foo: 123", and results like "foo = 1