Re: Redundant/mis-use of _(x) gettext macro? - Mailing list pgsql-hackers

From Peter Smith
Subject Re: Redundant/mis-use of _(x) gettext macro?
Date
Msg-id CAHut+PtnpNoJKAgwG54-BFRcH5rTn91T6njJnrnTK5+8BbzzBg@mail.gmail.com
Whole thread
In response to Re: Redundant/mis-use of _(x) gettext macro?  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: Redundant/mis-use of _(x) gettext macro?
List pgsql-hackers
On Wed, Apr 1, 2026 at 10:52 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> On 2026-Apr-01, Peter Smith wrote:
>
> > Hi.
> >
> > As originally reported [1] in the EXCEPT (TABLE ...) thread, I felt
> > the _() gettext macro is mis-used when it contains nothing but a
> > quoted format string.
>
> No, you feel wrong -- this is necessary so that the translator has
> control over the quoting style of a list of items.  Not all translations
> use double quoting.  Some examples from different language files:
>
> msgstr "unbekannte Komprimierungsoption: »%s«"
> msgstr "opción de compresión no reconocida: «%s»"
> msgstr "option de compression inconnue : « %s »"
> msgstr "tidak dapat menentukan encoding untuk lokal « %s » : codesetnya adalah « %s »"
>

OK. Thanks for your explanation.

======
Kind Regards,
Peter Smith.
Fujitsu Australia



pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Next
From: Chao Li
Date:
Subject: pg_test_timing: fix unit typo and widen diff type