| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Solaris versus our NLS files |
| Date: | 2025-12-10 16:35:35 |
| Message-ID: | aTmhV01tlJLYDJCS@ubby |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 10, 2025 at 05:02:14PM +0100, Peter Eisentraut wrote:
> On 09.12.25 22:22, Tom Lane wrote:
> > At least Solaris is kind enough to let you do that with
> > symlinks [2], so that after
> >
> > cd $INSTALLATION/share/locale
> > ln -s es es_ES.UTF-8
> >
> > translation starts working for that particular value of
> > lc_messages.
> >
> > This policy dictates making a rather large number of symlinks
> > in that directory, which we've never done TTBOMK.
>
> How would one know all the country codes to create links for?
Does OpenIndiance really require this? Oh, I guess it does:
That's a bummer.
Well, a list of country codes can probably be hardcoded into PG's build.
Or... the installation packaging could check at install time what
locales are installed and create these symlinks (but this is
unsatisfying because what if the locales in question get installed after
PG?).
Maybe PG should contribute a fix to Illumos :joy:
Nico
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-12-10 16:49:02 | Re: Solaris versus our NLS files |
| Previous Message | Heikki Linnakangas | 2025-12-10 16:31:48 | Re: not translating backend types for ps and log_line_prefix |