pgsql: Re-add translation markers that were lost

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема pgsql: Re-add translation markers that were lost
Дата
Msg-id E1bmOLC-0007ts-Qc@gemulon.postgresql.org
обсуждение исходный текст
Ответы Re: pgsql: Re-add translation markers that were lost  (Michael Paquier <michael.paquier@gmail.com>)
Список 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(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: pgsql: Use PostmasterRandom(), not random(), for DSM control segment ID
Следующее
От: Peter Eisentraut
Дата:
Сообщение: pgsql: Re-add translation markers that were lost