Peter Eisentraut writes:
> On 10.12.25 17:14, Tom Lane wrote:
>> Yeah, I've been wrestling with that question. The best idea
>> I have at the moment is to look at "locale -a" output to see
>> which country codes Solaris thinks there are for each language,
>> and duplicate that.
> I wonder how ot
On 10.12.25 17:14, Tom Lane wrote:
Peter Eisentraut writes:
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 v
I wrote:
> Encoding-specific behaviors might be worth testing later, but
> I'm not excited about that personally.
Despite that disclaimer, I experimented with the questionable nb.po
file on my OpenIndiana installation, and it seems to Just Work
after creating the nb_NO.UTF-8 -> nb locale symlink:
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes:
> Digging a bit more in the history of **/nb.po, there seems to be a
> policy that files that are less than 80% translated are removed¹,
BTW, while the wiki page does still say that, I have a vague idea
that the policy might have been changed late
I wrote:
> Peter Eisentraut writes:
>> How would one know all the country codes to create links for?
> Yeah, I've been wrestling with that question. The best idea
> I have at the moment is to look at "locale -a" output to see
> which country codes Solaris thinks there are for each language,
> an
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes:
> Álvaro Herrera writes:
>> 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.
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 work
Peter Eisentraut writes:
> 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.
> H
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 la
=?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes:
> Looking at the translations repo, there's 30 .po files (out of 530) that
> are not UTF-8, but I guess only nb/pg_config.po meets the 80% threshold
> and makes it into the main repo. To avoid future breakage, should we
> ask the translation team
Tom Lane writes:
> =?utf-8?Q?=C3=81lvaro?= Herrera writes:
>
>> 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.
>
> Shall I ju
Álvaro Herrera writes:
> On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
>
>> Álvaro Herrera 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 br
=?utf-8?Q?=C3=81lvaro?= Herrera writes:
> On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
>> 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,
On 2025-Dec-10, Dagfinn Ilmari Mannsåker wrote:
> Álvaro Herrera 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 mast
Álvaro Herrera 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-t
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 i
Thomas Munro writes:
> On Wed, Dec 10, 2025 at 11:22 AM Nico Williams 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
On Wed, Dec 10, 2025 at 11:22 AM Nico Williams wrote:
> On Wed, Dec 10, 2025 at 11:03:00AM +1300, Thomas Munro wrote:
> > On Wed, Dec 10, 2025 at 10:54 AM Thomas Munro
> > wrote:
> > > if you create codesetless symlinks
> >
> > Oops, wrote that too fast... you want to add the suffixes. Well the
On Wed, Dec 10, 2025 at 11:23 AM 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-na
Thomas Munro writes:
> On Wed, Dec 10, 2025 at 10:22 AM Tom Lane wrote:
>> After some quality time with Google, I learned why: with Solaris's
>> apparently-locally-hacked version of gettext, it's not good enough
>> to have $INSTALLATION/share/locale/ subdirectories named like
>> "es", "fr", etc.
On Wed, Dec 10, 2025 at 11:03:00AM +1300, Thomas Munro wrote:
> On Wed, Dec 10, 2025 at 10:54 AM Thomas Munro wrote:
> > if you create codesetless symlinks
>
> Oops, wrote that too fast... you want to add the suffixes. Well then
> it's the other way around, and you'd have to generate new files w
On Wed, Dec 10, 2025 at 10:54 AM Thomas Munro wrote:
> if you create codesetless symlinks
Oops, wrote that too fast... you want to add the suffixes. Well then
it's the other way around, and you'd have to generate new files with
the right encoding and suffixes (which means knowing which
combinati
On Wed, Dec 10, 2025 at 10:22 AM Tom Lane wrote:
> After some quality time with Google, I learned why: with Solaris's
> apparently-locally-hacked version of gettext, it's not good enough
> to have $INSTALLATION/share/locale/ subdirectories named like
> "es", "fr", etc. They have to be named after
I idly tried the NLS-testing patch at [1] on a Solaris image
(actually OpenIndiana), and was not really astonished to find that
it fails. Everything compiles cleanly, but the test shows that no
message translation happens, and manual checking confirms that.
After some quality time with Google, I
24 matches
Mail list logo
