> From: Bruno Haible <br...@clisp.org> > Cc: egg...@cs.ucla.edu, collin.fu...@gmail.com, bug-gnulib@gnu.org > Date: Thu, 06 Jun 2024 16:58:44 +0200 > > > Windows 9X in general don't have any _w* "wide" functions, and need to > > use UNICOWS.DLL to do so. > > You're confusing me now. I see many _w* "wide" functions in the msvcrt > from 1996-1998.
Yes. But they are stubs that don't really help. > Do you expect (generally) that these functions will work in Windows > 9x+UNICOWS, > or not? Yes, they should work, provided that UNICOWS has a non-stub version of them. > > UNICOWS.DLL does not come with header files AFAIK, it comes with the > > DLL and the corresponding .lib file. > > OK. So what matters is the set of header files of early Microsoft SDKs > and early mingw.org versions. Here I have the list of header files from > mingw.org from 2003: > https://git.savannah.gnu.org/gitweb/?p=gnulib/maint-tools.git;a=blob;f=platforms/various-includes/mingw.list > locale.h is contained there. Right. > So, would you agree that there is no problem with using <locale.h>? Yes, I already said (in the original discussion, in response to Paul's question) that MinGW should have no problem with using locale.h and setlocale. It was _wsetlocale that got me bothered, for the reason I explained in this thread.
