Re: pg_upgrade: prep_status doesn't translate messages - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_upgrade: prep_status doesn't translate messages
Date
Msg-id 20190610074842.GH2199@paquier.xyz
Whole thread Raw
In response to pg_upgrade: prep_status doesn't translate messages  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: pg_upgrade: prep_status doesn't translate messages
List pgsql-hackers
On Mon, Jun 10, 2019 at 01:57:14PM +0900, Kyotaro Horiguchi wrote:
> If we don't do that, translation lines in po files are
> useless. prep_stauts must be removed from TETTEXT_TRIGGERS, and a
> comment that explains the reason for not translating.
>
> Any opinions?

I agree with your point that it should be an all-or-nothing, and not
something in the middle.  Now, I would fall into the category of
people which would prefer making the full set of contents translated,
and there has been some work in this area recently:
https://www.postgresql.org/message-id/20170523002827.lzc2jkzh2gubclqb@alvherre.pgsql
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_basebackup failure after setting default_table_access_methodoption
Next
From: Alex
Date:
Subject: Re: Why to index a "Recently DEAD" tuple when creating index