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.

diff --git a/src/pl/plpgsql/src/scan.l b/src/pl/plpgsql/src/scan.l
index 1917eef95be1fe1487aa422ac86ec25d9f48e5bc..e4b1fd0d1c4c2ed423a2632f1646d4daa91ef2b8 100644 (file)
--- 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)));