From 0a09f7ae4fe762340d4c7ae3418c4c1de71fd6c1 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 10 Jun 2009 22:34:11 +0000 Subject: [PATCH] Clarify to the translator that plpgsql_yyerror() deals with the translation of "syntax error", not the literal string. This same change was made in the backend a while ago; but it applies to plpgsql as well. --- src/pl/plpgsql/src/scan.l | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pl/plpgsql/src/scan.l b/src/pl/plpgsql/src/scan.l index 1917eef95b..e4b1fd0d1c 100644 --- a/src/pl/plpgsql/src/scan.l +++ b/src/pl/plpgsql/src/scan.l @@ -441,7 +441,7 @@ plpgsql_yyerror(const char *message) { ereport(ERROR, (errcode(ERRCODE_SYNTAX_ERROR), - /* translator: %s is typically "syntax error" */ + /* translator: %s is typically the translation of "syntax error" */ errmsg("%s at end of input", _(message)), internalerrposition(cursorpos), internalerrquery(scanstr))); @@ -450,7 +450,7 @@ plpgsql_yyerror(const char *message) { ereport(ERROR, (errcode(ERRCODE_SYNTAX_ERROR), - /* translator: first %s is typically "syntax error" */ + /* translator: first %s is typically the translation of "syntax error" */ errmsg("%s at or near \"%s\"", _(message), loc), internalerrposition(cursorpos), internalerrquery(scanstr))); -- 2.39.5