Re: fixing pg_upgrade strings (was Re: pgsql: Add new files to nls.mk and add translation)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2017-08-03T04:15:52Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add new files to nls.mk and add translation markers
- 5ff3d73813eb 10.0 cited
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> It does this:
> pg_fatal("You must identify the directory where the %s.\n"
> "Please use the %s command-line option or the %s environment variable.\n",
> description, cmdLineOption, envVarName);
> and the callsites are like this:
> check_required_directory(&new_cluster.bindir, NULL, "PGBINNEW", "-B",
> _("new cluster binaries reside"));
> check_required_directory(&old_cluster.pgdata, &old_cluster.pgconfig,
> "PGDATAOLD", "-d", _("old cluster data resides"));
> note the declensions don't match even in the English original.
FWIW, I think the English declensions are fine as long as you consider
"data" to be a group noun --- "data reside" would read a bit funny IMO.
But certainly this is an utter translatability fail. Maybe pass a boolean
to indicate one of two first sentences to use? Or actually, might as well
consider the entire message string to be one of two translatable options.
It's not like we have a need to indicate more than one option or envar
name for each case.
regards, tom lane