Horton

Re: Solaris versus our NLS files

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Nico Williams <nico@cryptonector.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-12-09T23:36:19Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add a regression test to verify that NLS translation works.

  2. Translation updates

  3. Translation updates for 8.4 release.

Thomas Munro <thomas.munro@gmail.com> writes:
> On Wed, Dec 10, 2025 at 11:22 AM Nico Williams <nico@cryptonector.com> 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