Re: (non) translatable string splicing
От | Kyotaro Horiguchi |
---|---|
Тема | Re: (non) translatable string splicing |
Дата | |
Msg-id | 20221221.162314.534889274118410330.horikyota.ntt@gmail.com обсуждение исходный текст |
Ответ на | Re: (non) translatable string splicing (Michael Paquier <michael@paquier.xyz>) |
Список | 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 по дате отправления: