Re: Windows question: when is LC_MESSAGES defined?

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Windows question: when is LC_MESSAGES defined?
Date: 2025-07-10 04:33:34
Message-ID: CA+hUKGLUP8RVunFDFCpPX+1Sau_O6RmK+PG3EirT=MSp41UfOw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 10, 2025 at 3:45 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> [03:28:24.318] Program msgfmt found: NO

Correction, that ^ is the reason it's not reached on the MSVC task,
while -Dnls=disabled is the reason for the MinGW task. But the
conclusion is the same: MinGW is the easiest way to test this code
on CI, if you're hacking on it.

Given that the build farm also doesn't test Windows + NLS, it's a
small miracle that it even compiles. Hmm, I guess that the EDB
installer build must have it enabled, so I suppose they'd tell us if
we broke it. I guess that because sometimes we see reports of
encoded-garbled error messages in other languages on the lists, which
also tells us that it might have bugs in that department. What I
don't recall is whether they looked like the
"some-contexts-have-no-defined-encoding" problem (that exists on Unix
too but no one cares anymore since we all switched everything to UTF-8
ages ago), or something else...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-07-10 05:04:28 Re: CHECKPOINT unlogged data
Previous Message Dilip Kumar 2025-07-10 04:25:37 Re: CHECKPOINT unlogged data