luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-24 14:36:13 +01:00
Code Issues Packages Projects Releases Wiki Activity

Further Win32 edits.

Browse Source
This commit is contained in:
Tor Lillqvist 2004-12-15 22:08:37 +00:00
parent 72eab4d04d
commit eefa2d9763
1 changed files with 15 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.in
View File

@ -31,18 +31,27 @@ Notes about GLib 2.6.0
on-disk encoding on Unix, but UTF-8 on Windows. All GLib functions on-disk encoding on Unix, but UTF-8 on Windows. All GLib functions
returning or accepting pathnames have been changed to expect returning or accepting pathnames have been changed to expect
filenames in this encoding, and the common POSIX functions dealing filenames in this encoding, and the common POSIX functions dealing
with pathnames have been wrapped. On Windows these wrappers use the with pathnames have been wrapped. These wrappers are declared in the
wide-character API to do the actual file handling, so applications header <glib/gstdio.h> which must be included explicitly, it is not
can handle file names containing any Unicode characters, not just included through <glib.h>.
those in the system codepage. (Wide character API is not available
on Win9x.) On current (NT-based) Windows versions, where the on-disk file names
are Unicode, these wrappers use the wide-character API in the C
library. Thus applications can handle file names containing any
Unicode characters through GLib's own API and its POSIX wrappers,
not just file names restricted to characters in the system codepage.
To keep binary compatibility with applications compiled against To keep binary compatibility with applications compiled against
older versions of GLib, the Windows DLL still provides entry points older versions of GLib, the Windows DLL still provides entry points
with the old semantics using the old names, and applications with the old semantics using the old names, and applications
compiled agains GLib 2.6 will actually use new names for the compiled against GLib 2.6 will actually use new names for the
functions. This is transparent to the programmer. functions. This is transparent to the programmer.
When compiling against GLib 2.6, applications intended to be
portable to Windows must take the UTF-8 file name encoding into
consideration, and use the gstdio wrappers to access files whose
names have been constructed from strings returned from GLib.
* Likewise, g_get_user_name() and g_get_real_name() have been changed to return * Likewise, g_get_user_name() and g_get_real_name() have been changed to return
UTF-8 on Windows, while keeping the old semantics for applications compiled UTF-8 on Windows, while keeping the old semantics for applications compiled
against older versions of GLib. against older versions of GLib.