From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bryan Green <dbryan.green@gmail.com>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: PRI?64 vs Visual Studio (2022)
In-reply-to: <c6379076-aabc-4ee8-920b-bd0d18bd2379@gmail.com>
References: <20250331.152829.1921392690375275165.horikyota.ntt@gmail.com>
 <001bdc3b-ef94-4f24-b017-ac8ff0a2ea55@eisentraut.org>
 <CA+hUKGJnmzTqiODmTjf-23yZ=E3HXqFTtKoyp3TF-MpB93hTMQ@mail.gmail.com>
 <1372793.1763519315@sss.pgh.pa.us>
 <CA+hUKGLzXzQcbjEHW08Z6g=mzBkpLtzSJ7Bt2S2XmxP1bwpq8A@mail.gmail.com>
 <1377512.1763522154@sss.pgh.pa.us>
 <e7b902aa-98ac-4d35-bae3-d7d282a938c2@eisentraut.org>
 <1462038.1763567038@sss.pgh.pa.us>
 <CA+hUKG+nMv9bmOcARaDFC6rG=SGWC=TwWSRLrxi29oGeRNKemg@mail.gmail.com>
 <1881391.1765782112@sss.pgh.pa.us>
 <CA+hUKGJaX3AcuKSdEUOZiWc+mzL=+dvGnbMqCvWGY22y6oh9Nw@mail.gmail.com>
 <1991599.1765818338@sss.pgh.pa.us>
 <c6379076-aabc-4ee8-920b-bd0d18bd2379@gmail.com>
Comments: In-reply-to Bryan Green <dbryan.green@gmail.com>
	message dated "Mon, 15 Dec 2025 11:24:34 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2117909.1765823286.1@sss.pgh.pa.us>
Date: Mon, 15 Dec 2025 13:28:06 -0500
Message-ID: <2117910.1765823286@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2117910.1765823286%40sss.pgh.pa.us>
Precedence: bulk

Bryan Green <dbryan.green@gmail.com> writes:
> On 12/15/2025 11:05 AM, Tom Lane wrote:
>> ... That's
>> colored by seeing that less than half of the buildfarm is finding any
>> variant of es_ES to test in.  That's not great, but I'm not seeing
>> anything to be done about it.  The only locale names we can be sure
>> will be accepted are C/POSIX, and I'd expect gettext() to
>> short-circuit that case and not look for a translation.  I'm thinking
>> though that it's still worth checking that the untranslated string is
>> processed correctly.

> The GNU gettext implementation does not short-circuit that.  It still
> goes through the path of trying to find the message catalogue, it fails,
> there is no fallback, messages are untranslated. This is true on Windows
> as well as Linux.

It'd be great to not need the assumption of es_ES being installed.
However, I tried making a POSIX.po file and setting lc_messages to
POSIX, and it didn't work.  The msgfmt infrastructure seemed unfazed
and installed a .mo file under $sharedir/locale/POSIX/LC_MESSAGES as
I'd expect, but no translation happened (this on a Linux box).  Same
with 'C'.  It did work if I set lc_messages to 'C.utf8', which is a
known name according to this box's "locale -a", but this doesn't give
me a warm feeling about this approach being a lot more portable than
what we have.  Any ideas?

			regards, tom lane