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

pgsql: Re-add translation markers that were lost

From
Peter Eisentraut
Date:
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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/90c9648212f7c3f0838fdaafe006ed40556a1364

Modified Files
--------------
src/port/win32security.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)


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

From
Michael Paquier
Date:
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