Re: Redundant/mis-use of _(x) gettext macro?
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Peter Smith <smithpb2250@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-24T12:43:43Z
Lists: pgsql-hackers
On Sat, 25 Apr 2026 at 00:14, Álvaro Herrera <alvherre@kurilemu.de> wrote: > > On 2026-Apr-24, Peter Smith wrote: > > > OK. Including the comma within a larger translated string seems like a > > better idea. > > > > Since you now have the list `length`, I wondered why not simplify > > further to use list_nth indexing? Then you can remove > > `foreach_current_index` and `lc`. > > WFM. Wouldn't it be simpler to put the comma on the other end of the name and use that if (foreach_current_index(lc) > 0) ? Or was this to reuse a translation and you didn't want to swap "\"%s\", " for , "\"%s\" ? David
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