> Date: Thu, 8 Oct 2026 17:16:39 +0200 > From: Patrice Dumas <[email protected]> > Cc: [email protected], Eli Zaretskii <[email protected]> > > On Thu, Oct 08, 2026 at 04:31:35PM +0200, Bruno Haible wrote: > > Patrice Dumas wrote: > > > However, if the locale is the C locale, it must be > > > changed first to any other locale such that LANGUAGE is obeyed, and it > > > is this code that is skipped on _WIN32, which is probably wrong. > > > > Yes, such code is needed, because gettext returns untranslated strings > > when the locale is "C". > > > > The only real differences between _WIN32 and POSIX systems are the > > locale names: What is "fr_FR.ISO-8859-1" in POSIX systems, is > > "French_France.1252" on _WIN32. > > Is there a locale, and what could be its name, that is always installed > on _WIN32 systems, such that we can switch to that locale from the C > locale?
"Installed" in what sense? what does the test suite need from a locale? > (On POSIX, we try "en_US.UTF-8", "en_US" and 'locale -a' command > output). You can use "English_United_States" or its short alias "ENU" where you use en_US on Posix systems. But how will that let you test translation, when the original is already in US English? I think you can also use "French_France", at least for translation to French. If that locale is not available (I think this should be very rare, if it at all happens, but Bruno will correct me if I'm wrong), then translation to French should be skipped anyway.
