Re: Solaris versus our NLS files

Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>

From: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-12-10T14:19:27Z
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.

Álvaro Herrera <alvherre@kurilemu.de> writes:

> On 2025-Dec-09, Tom Lane wrote:
>
>> If you're right about Sun not doing transcoding, then I guess we would
>> only need to create symlinks matching the encodings used in our .po
>> files, which'd remove the symlink bloat problem and replace it with
>> how-do-we-extract-that-encoding-name ... although it looks like all
>> but one is in UTF-8, so maybe we should just decree they have to be
>> in UTF-8?  The lone exception is src/bin/pg_config/po/nb.po, which
>> seems not to have been touched since 2013.
>
> Hmm, where do you see that file?  It was removed by commit 3c70de2e12b9
> from branch 12 in 2019, and has never existed since.

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:

https://git.postgresql.org/cgit/postgresql.git/tree/src/bin/pg_config/po/nb.po

- ilmari