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

From Chao Li
Subject Re: Redundant/mis-use of _(x) gettext macro?
Date
Msg-id E04A82BE-ED1F-4BFB-A95D-4508BFA45756@gmail.com
Whole thread Raw
In response to Re: Redundant/mis-use of _(x) gettext macro?  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Redundant/mis-use of _(x) gettext macro?
List pgsql-hackers

> On Apr 2, 2026, at 10:55, Peter Smith <smithpb2250@gmail.com> wrote:
>
> 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.
>

Yep, good to learn. Noted.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/







pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: pg_test_timing: fix unit typo and widen diff type
Next
From: Tom Lane
Date:
Subject: Re: Redundant/mis-use of _(x) gettext macro?