Re: (non) translatable string splicing - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: (non) translatable string splicing
Date
Msg-id 20221221.162314.534889274118410330.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: (non) translatable string splicing  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
At Mon, 19 Dec 2022 13:20:55 +0900, Michael Paquier <michael@paquier.xyz> wrote in
> On Fri, Dec 16, 2022 at 07:24:52AM -0600, Justin Pryzby wrote:
> > Due to incomplete translation, that allows some pretty fancy output,
> > like:
> > | You must identify the directory where the residen los binarios del clúster antiguo.
> >
> > That commit also does this a couple times:
> >
> > +                        _(" which is an index on \"%s.%s\""),

For this specific case I didn't feel a difficulty since it is
compatible with "This is blah" in that context.

> Ugh.  Perhaps we could just simplify the wordings as of "index on
> blah", "index on OID %u", "TOAST table for blah" and "TOAST table for
> OID %u" with newlines after each item?

I'm fine with just removing " which ". but I don't understand about
the extra newlines.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Force streaming every change in logical decoding
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: (non) translatable string splicing