Re: Get rid of translation strings that only contain punctuation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Get rid of translation strings that only contain punctuation
Date: 2026-04-22 02:32:48
Message-ID: 889437.1776825168@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Smith <smithpb2250(at)gmail(dot)com> writes:
> Case#1: publication "XXX" has a problem
> Case#2: the following publications have a problem: "XXX", "YYY", "ZZZ"

Entirely aside from the mechanics of producing the output,
I am not sure I buy that emitting that is a desirable goal.
It seems to be based on an English-centric notion that singular
and indefinitely-many plural are the only two categories.
This is incorrect (see the documentation for ngettext()).

Is there a good reason not to output a separate message for
each publication? If we need to throw an ereport(ERROR)
covering them all, maybe list them in separate sentences
in a DETAIL message.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2026-04-22 02:58:01 Re: PoC: Add condition variable support to WaitEventSetWait()
Previous Message Peter Smith 2026-04-22 02:20:08 Re: Get rid of translation strings that only contain punctuation