From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: fixing pg_upgrade strings (was Re: pgsql: Add new files to nls.mk and add translation) |
Date: | 2017-08-03 04:15:52 |
Message-ID: | 13948.1501733752@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-08-03 16:01:08 | pgsql: Teach map_partition_varattnos to handle whole-row expressions. |
Previous Message | Tom Lane | 2017-08-03 03:59:17 | Re: [COMMITTERS] pgsql: Fix pg_dump's errno checking for zlib I/O |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2017-08-03 04:24:04 | Re: INSERT ON CONFLICT and partitioned tables |
Previous Message | Tom Lane | 2017-08-03 03:59:17 | Re: [COMMITTERS] pgsql: Fix pg_dump's errno checking for zlib I/O |