Re: (non) translatable string splicing

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: (non) translatable string splicing
Date: 2022-12-19 04:20:55
Message-ID: Y5/mp+71I+hfPxqt@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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\""),

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?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-12-19 04:30:14 Re: GROUP BY ALL
Previous Message Andrey Borodin 2022-12-19 04:19:10 GROUP BY ALL