delorie.com/archives/browse.cgi | search |
From: | noer AT cygnus DOT com (Geoffrey Noer) |
Subject: | Reason for SetFileApisToOEM call in dcrt0.cc? |
13 May 1998 14:49:01 -0700 : | |
Message-ID: | <199805132120.OAA18806.cygnus.cygwin32.developers@skaro.cygnus.com> |
To: | cygwin32-developers AT cygnus DOT com |
Cc: | noer AT cygnus DOT com (Geoffrey Noer) |
Do any of you understand why SetFileApisToOEM is called in dcrt0.cc (dll_crt0_1)??? I don't. Reading the MSDN info for the function didn't help matters -- it claims that (in my words): The normal defaults are OEM code page for 8-bit console functions and ANSI code page for others. A warning says that strings may not be compatible between these and that the best thing to do is to use the Unicode console functions and then use the ANSI code page for everything. We seem to be using the 8-bit console functions but setting the code page to OEM for all functions. I'm not convinced this is the right thing for Cygwin32 to be doing. -- Geoffrey Noer noer AT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |