Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vT7Fu-00DPDf-2A for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Dec 2025 23:36:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vT7Fs-008f1L-19 for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Dec 2025 23:36:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vT7Fs-008f1D-0C for pgsql-hackers@lists.postgresql.org; Tue, 09 Dec 2025 23:36:28 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vT7Fq-00421q-2G for pgsql-hackers@lists.postgresql.org; Tue, 09 Dec 2025 23:36:27 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5B9NaJl4308001; Tue, 9 Dec 2025 18:36:19 -0500 From: Tom Lane To: Thomas Munro cc: Nico Williams , pgsql-hackers@lists.postgresql.org Subject: Re: Solaris versus our NLS files In-reply-to: References: <292844.1765315339@sss.pgh.pa.us> Comments: In-reply-to Thomas Munro message dated "Wed, 10 Dec 2025 11:58:00 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <307999.1765323379.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 09 Dec 2025 18:36:19 -0500 Message-ID: <308000.1765323379@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > On Wed, Dec 10, 2025 at 11:22=E2=80=AFAM Nico Williams wrote: >> How about supporting only UTF-8 locales? > Yeah, if nobody noticed this wasn't working at all, then it makes > sense to defer the generation of .mo files for non-UTF-8 codesets > until someone eventually does notice that it still doesn't work in > legacy locales and feels inclined to do something about it, ie > forever. Tom's goal of having basic tests pass will be satisfied by > UTF-8-only. Right. For the moment I only care about verifying that (a) some translation happens and (b) the PRI* macros work as-expected. Since we've already discovered platform-specific failures on both points, this seems like a very worthwhile exercise. Encoding-specific behaviors might be worth testing later, but I'm not excited about that personally. regards, tom lane