Feedback-ID: ie3de48e3:Fastmail
Date: Wed, 19 Nov 2025 18:07:16 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>,
	Thomas Munro <thomas.munro@gmail.com>,
 Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: PRI?64 vs Visual Studio (2022)
Message-ID: <202511191705.fxfewzkxoj27@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1462038.1763567038@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/202511191705.fxfewzkxoj27%40alvherre.pgsql>
Precedence: bulk

On 2025-Nov-19, Tom Lane wrote:

> Peter Eisentraut <peter@eisentraut.org> writes:
> > On 19.11.25 04:15, Tom Lane wrote:
> >> I think we should do it
> >> honestly with a regression test.  It doesn't need to be very
> >> complicated --- I think checking one message in one translation is
> >> sufficient, so long as it includes a PRI?64 usage.
> 
> > We could generate an English message catalog that translates all 
> > messages unchanged, and run the whole test suite with that.  This would 
> > exercise the whole gettext run-time machinery.
> 
> ... except that if it were actually doing nothing whatsoever, you
> could not tell.

You could feed the message catalog a translated string that differs from
the original in some simple way, say, by adding a constant prefix
"[translated]" or something like that.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/