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 ce52d7bd6a3d67bfef9a469d7b0746e93b7adeab..b5d9b470a037110326ffc57d99aa88cb388f65b7 100644 (file)
--- a/src/pl/plpgsql/src/scan.l
+++ b/src/pl/plpgsql/src/scan.l
@@ -9,7 +9,7 @@
  *
  *
  * IDENTIFICATION
- *       $PostgreSQL: pgsql/src/pl/plpgsql/src/scan.l,v 1.69 2009/04/19 21:50:09 tgl Exp $
+ *       $PostgreSQL: pgsql/src/pl/plpgsql/src/scan.l,v 1.70 2009/06/10 22:34:11 petere Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -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)));