AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2025-01-13 22:10:08 +00:00
Code Issues Projects Releases Wiki Activity

Win32 edits.

Browse Source
This commit is contained in:
Tor Lillqvist 2004-12-15 22:09:49 +00:00
parent 991314e620
commit ea4066c97e
1 changed files with 15 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.in
View File

@ -81,8 +81,9 @@ Release notes
the GTK+ developers consider that having filenames whose interpretation the GTK+ developers consider that having filenames whose interpretation
depends on the current locale is fundamentally a bad idea. depends on the current locale is fundamentally a bad idea.
If you have filenames encoded in the encoding of your locale, then On Unix, if you have filenames encoded in the encoding of your
you may want to set the G_FILENAME_ENCODING environment variable: locale, then you may want to set the G_FILENAME_ENCODING environment
variable:
G_FILENAME_ENCODING=@local G_FILENAME_ENCODING=@local
export G_FILENAME_ENCODING export G_FILENAME_ENCODING
@ -93,6 +94,18 @@ Release notes
Best integration of GTK+ 2.6 with the environment is achieved by Best integration of GTK+ 2.6 with the environment is achieved by
using a UTF-8 locale. using a UTF-8 locale.
On Windows, filenames passed to GTK+ should always be in UTF-8, like
in GLib 2.6. This is different than in previous versions of GTK+
where the system codepage was used. Like in GLib, for DLL ABI
stability, applications built against previous versions of GTK+ will
use entry points providing the old semantics.
When compiling against GTK+ 2.6, applications intended to be
portable to Windows must take the UTF-8 file name encoding into
consideration, and for instance use the gstdio wrappers to access
files whose names have been constructed from strings returned from
GTK+ or GLib.
How to report bugs How to report bugs
================== ==================