> Date: Sun, 23 Oct 2022 13:08:14 +0200 > From: [email protected] > Cc: [email protected], [email protected] > > > Here's the diff to Translations.pm, it is AFAIU needed because the > > Windows locale names don't follow the Posix patterns. Instead, they > > are 3-letter names, like "ENU" for en_US, "FRA" for fr_FR, etc. > > Ok. Hopefully it does not interfere with translations, only with file > names encodings.
Please tell more: how is this locale used for translations? I assumed that, since the original Unix code sets the locale to en_US as fallback, and even falls back to the "C" locale later, that using the equivalent of en_US on Windows should be okay. > > The > > diff below should be obviously conditioned by this being MS-Windows. > > Is this locale supposed to always exist on Windows? Yes. Only very exotic locales need special packages to be installed on Windows, all the "usual" ones come preinstalled OOTB. > I am not sure that this patch is needed, as it seems to me that it > modifies a code that is no longer run on windows with a patch Gavin > applied very recently. Which commit is that?
