Re: pg_upgrade: prep_status doesn't translate messages

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade: prep_status doesn't translate messages
Date: 2019-06-10 07:48:42
Message-ID: 20190610074842.GH2199@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex 2019-06-10 07:59:58 Re: Why to index a "Recently DEAD" tuple when creating index
Previous Message Michael Paquier 2019-06-10 07:37:33 Re: pg_basebackup failure after setting default_table_access_method option