Skip to content
Snippets Groups Projects
Commit 820984ba authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files

Clarify to the translator that yyerror() deals with the translation of

"syntax error", not the literal string.  I was previously confused on this
matter, but I have now verified that everything is translated properly.
parent b966b519
No related branches found
No related tags found
No related merge requests found
......@@ -24,7 +24,7 @@
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/parser/scan.l,v 1.148 2009/01/01 17:23:46 momjian Exp $
* $PostgreSQL: pgsql/src/backend/parser/scan.l,v 1.149 2009/03/04 13:02:32 petere Exp $
*
*-------------------------------------------------------------------------
*/
......@@ -880,7 +880,7 @@ 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)),
lexer_errposition()));
}
......@@ -888,7 +888,7 @@ 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),
lexer_errposition()));
}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment