From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
cc: Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= <ilmari@ilmari.org>,
        Thomas Munro <thomas.munro@gmail.com>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Solaris versus our NLS files
In-reply-to: <202512101432.rkz3zbykficx@alvherre.pgsql>
References: <202512101432.rkz3zbykficx@alvherre.pgsql>
Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
	message dated "Wed, 10 Dec 2025 15:33:50 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <619007.1765379928.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 10 Dec 2025 10:18:48 -0500
Message-ID: <619008.1765379928@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/619008.1765379928%40sss.pgh.pa.us>
Precedence: bulk

=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
> On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
>> That translation commit was on the REL_12_STABLE branch, after it was
>> cut from master (after rc1, even).  Looking more closely, the
>> post-branch translation updates deleted it from version 12, 13, 14, and
>> 15, but not 16 onwards, and the file is still there in master:

Hah, yeah, I failed to notice that there's a gap in which branches
have that file.  But it's definitely there in master.

> Oh.  Well, that's clearly a process failure, and the fix will require us
> deleting that file on all branches from 16 and up anyway, so I have no
> issues with the plan of requiring all message catalogs to be UTF-8.

Shall I just go delete those files, or is there more process that
ought to be observed here?

			regards, tom lane