Horton

Re: Solaris versus our NLS files

Álvaro Herrera <alvherre@kurilemu.de>

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

On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:

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

> > 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:

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.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"I can see support will not be a problem.  10 out of 10."    (Simon Wittber)
      (http://archives.postgresql.org/pgsql-general/2004-12/msg00159.php)