pgsql: Re-add translation markers that were lost

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Re-add translation markers that were lost
Date: 2016-09-20 16:56:18
Message-ID: E1bmOLC-0007ts-Qc@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2016-09-20 17:12:10 pgsql: doc: Correct ALTER USER MAPPING example
Previous Message Robert Haas 2016-09-20 16:32:54 pgsql: Use PostmasterRandom(), not random(), for DSM control segment ID