From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Missing latex-longtable value |
Date: | 2015-07-07 17:05:09 |
Message-ID: | 27164.1436288709@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Tue, Jul 7, 2015 at 11:48:13AM -0400, Tom Lane wrote:
>> It's a bug. Back-patch as needed.
> Doesn't that cause translation string differences that are worse than
> the original bug, e.g.:
> psql_error("\\pset: allowed formats are unaligned, aligned, wrapped, html, asciidoc, latex, latex-longtable, troff-ms\n");
No. When we've discussed this sort of thing in the past, people have been
quite clear that they'd rather have accurate messages that come out in
English than inaccurate-though-localized messages. Certainly we should
avoid gratuitous changes in back-branch localized strings, but this is a
factual error in the message.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2015-07-07 17:14:49 | Re: creating extension including dependencies |
Previous Message | Fujii Masao | 2015-07-07 16:58:26 | Re: [PATCH] correct the initdb.log path for pg_regress |