Re: Windows question: when is LC_MESSAGES defined?
От | Thomas Munro |
---|---|
Тема | Re: Windows question: when is LC_MESSAGES defined? |
Дата | |
Msg-id | CA+hUKGLUP8RVunFDFCpPX+1Sau_O6RmK+PG3EirT=MSp41UfOw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Windows question: when is LC_MESSAGES defined? (Thomas Munro <thomas.munro@gmail.com>) |
Список | pgsql-hackers |
On Thu, Jul 10, 2025 at 3:45 PM Thomas Munro <thomas.munro@gmail.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...
В списке pgsql-hackers по дате отправления: