Re: Redundant/mis-use of _(x) gettext macro?
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Peter Smith <smithpb2250@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-01T11:52:02Z
Lists: pgsql-hackers
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 »" -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "In fact, the basic problem with Perl 5's subroutines is that they're not crufty enough, so the cruft leaks out into user-defined code instead, by the Conservation of Cruft Principle." (Larry Wall, Apocalypse 6)
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix translatable string construction in psql
- 5459223edb1d 19 (unreleased) landed
-
Fix translatable string construction
- 3692a622d3fd 19 (unreleased) landed