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

From Álvaro Herrera
Subject Re: Redundant/mis-use of _(x) gettext macro?
Date
Msg-id aeteISM1k7ZtM4Cs@alvherre.pgsql
Whole thread
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 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.

> Also, why did you choose to implement `last` versus `first` logic?
> e.g. How about this?

>         {
>             if (first)
>                 appendStringInfo(dest, _("\"%s\""), pubname);
>             else
>                 appendStringInfo(dest, _(", \"%s\""), pubname);
>         }

I don't know, it just seemed more natural.  The whole ", foo" style
simply feels weird to me.  It seems a matter of choice only though, so
if you feel strongly about this, I'm not opposed.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"Hay dos momentos en la vida de un hombre en los que no debería
especular: cuando puede permitírselo y cuando no puede" (Mark Twain)



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Fix DROP PROPERTY GRAPH "unsupported object class" error
Next
From: Ashutosh Bapat
Date:
Subject: Re: Property graph: fix error handling when dropping non-existent label property