Re: Solaris versus our NLS files - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Solaris versus our NLS files
Date
Msg-id 202512100925.wutmtw5tx7m5@alvherre.pgsql
Whole thread Raw
In response to Re: Solaris versus our NLS files  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Solaris versus our NLS files
List pgsql-hackers
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.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Los cuentos de hadas no dan al niño su primera idea sobre los monstruos.
Lo que le dan es su primera idea de la posible derrota del monstruo."
                                                   (G. K. Chesterton)



pgsql-hackers by date:

Previous
From: tushar
Date:
Subject: Re: Non-text mode for pg_dumpall
Next
From: Álvaro Herrera
Date:
Subject: not translating backend types for ps and log_line_prefix