From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | michael(at)paquier(dot)xyz |
Cc: | pryzby(at)telsasoft(dot)com, pgsql-hackers(at)postgresql(dot)org, peter_e(at)gmx(dot)net |
Subject: | Re: (non) translatable string splicing |
Date: | 2022-12-21 07:23:14 |
Message-ID: | 20221221.162314.534889274118410330.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Mon, 19 Dec 2022 13:20:55 +0900, Michael Paquier <michael(at)paquier(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2022-12-21 07:32:04 | Re: (non) translatable string splicing |
Previous Message | Masahiko Sawada | 2022-12-21 07:21:55 | Re: Force streaming every change in logical decoding |