Re: pgsql: Re-add translation markers that were lost

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Re-add translation markers that were lost
Date: 2016-09-21 01:54:23
Message-ID: CAB7nPqStQ39MWNCA0XuFufo8Gko2YWEKydLokwE7YkbHxfRQcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Sep 21, 2016 at 1:56 AM, Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2016-09-21 10:26:49 pgsql: Print test parameters like "foo: 123", and results like "foo = 1
Previous Message Peter Eisentraut 2016-09-21 00:59:30 pgsql: pg_restore: Add -N option to exclude schemas