Tor Lillqvist d867b9a8df Merge from stable:
2003-01-19  Tor Lillqvist  <tml@iki.fi>

	Merge from stable:

	Fix for #103614 and some other problems with GtkFileSelection on
	Windows:

	* gtk/fnmatch.c (get_char): Need to use g_unichar_tolower(), not
	g_ascii_tolower(). Windows file names are case-insensitive for all
	Unicode letters.

	* gtk/gtkfilesel.c: Instead of checking for G_OS_WIN32 or
	G_WITH_CYGWIN, check G_PLATFORM_WIN32. Move inclusion of gtkintl.h
	earlier, as it includes config.h unconditionally, and gtkprivate.h
	redefines GTK_LOCALEDIR.
	(struct _CompletionDirSent): Ifdef out the fields not used on
	Windows.
	(compare_utf8_filenames, compare_sys_filenames): Need different
	comparison implementation for UTF-8 file names and system locale
	file names on Win32. Cannot simply use g_ascii_strcasecmp(), but
	need to casefold all Unicode letters.
	(cmpl_completion_matches, open_dir, correct_parent): Ifdef out
	variables not used on Win32 to avoid warnings about unused
	variables.
	(open_ref_dir): Use g_path_skip_root() to skip past potential
	drive letter in front of the leading (back)slash.
	(open_new_dir): Ifdef out use of CompletionDirSent fields not
	there on Win32.
	(correct_parent): Bypass inode check also on Cygwin.

	Fix bug noticed by Alex Shaduri: Tooltips and other
	GDK_WINDOW_TEMP windows were activated. This looked very odd, and
	was a regression from earlier versions.

	* gdk/win32/gdkwindow-win32.c (show_window_internal): Fine-tune
	behaviour. Don't ever activate GDK_WINDOW_TEMP windows.
	(gdk_window_move, gdk_window_resize): Add debug logging.

	* gdk/win32/gdkevents-win32.c (gdk_event_translate): When we get a
	WM_SIZE message for a non-visible (withdrawn) window, don't clear
	the GDK_WINDOW_STATE_WITHDRAWN bit. The window is still withdrawn
	even if its size changes.
2003-01-19 21:18:15 +00:00
2002-09-29 21:24:24 +00:00
2003-01-19 21:18:15 +00:00
2003-01-19 21:18:15 +00:00
2003-01-16 12:44:16 +00:00
2002-03-15 01:43:08 +00:00
2003-01-19 21:18:15 +00:00
2002-03-15 22:58:49 +00:00
2002-12-28 21:24:40 +00:00
2003-01-19 21:18:15 +00:00
2003-01-19 21:18:15 +00:00
2003-01-19 21:18:15 +00:00
2003-01-19 21:18:15 +00:00
2002-03-05 21:04:09 +00:00
2002-03-05 21:04:09 +00:00
2001-04-03 18:48:46 +00:00
2003-01-12 04:44:23 +00:00
2002-03-05 21:04:09 +00:00
2002-12-21 01:59:14 +00:00
2002-12-21 01:59:14 +00:00
2002-12-21 01:59:14 +00:00
2002-12-21 01:59:14 +00:00
2002-12-21 01:59:14 +00:00
1999-09-28 20:19:13 +00:00

General Information
===================

This is GTK+ version 2.2.0. GTK+ is a multi-platform toolkit for
creating graphical user interfaces. Offering a complete set of widgets,
GTK+ is suitable for projects ranging from small one-off projects to
complete application suites.

GTK+ is free software and part of the GNU Project. However, the
licensing terms for GTK+, the GNU LGPL, allow it to be used by all
developers, including those developing proprietary software, without any
license fees or royalties.

The official ftp site is:
  ftp://ftp.gtk.org/pub/gtk

The official web site is:
  http://www.gtk.org/

Information about mailing lists can be found at
  http://www.gtk.org/mailinglists.html

Installation
============

See the file 'INSTALL'

Release notes
=============

* As compared to GTK+-1.2, the default configuration of GTK+-2 has been 
  stream-lined to reduce confusion on the part of new users or users 
  coming from other environments.  Users used to older versions of 
  GTK+ may want to make some adjustments to the default configuration.

   - Emacs keybindings such as Control-A and Control-E to move to the
     ends of lines are not enabled by default in the editing widgets. To
     turn on Emacs keybindings, add the line:

      gtk-key-theme-name = "Emacs"
   
     To your ~/.gtkrc-2.0

   - Editing of menu accelerators by pressing an accelerator over the
     menu item is disabled by default. To enable, it, add:

      gtk-can-change-accels = 1

     to your ~/.gtkrc-2.0

   - To improve useability for keyboard operation, GTK+ now selects the
     contents of an entry when tabbing into it or when it is focused on
     initial window map. To disable this behavior, add:

      gtk-entry-select-on-focus = 0
 
     to your ~/.gtkrc-2.0

* The GTK+ libraries use an '_' prefix to indicate private symbols that
  must not be used by applications. On some platforms, symbols beginning 
  with prefixes such as _gtk, _gdk, and _pango will be exported
  from the library, on others not. In no case can applications
  use these private symbols.

* GTK+-2.2 can be build either with Pango-1.0 and version 1 of
  the Xft library or Pango-1.2 and version 2 of the Xft library
  (Xft is used to to display anti-aliased fonts) By default, GTK+ and 
  Pango are built so that applications will not have explicit dependencies 
  on either version of Xft. To make sure that your application will be 
  binary compatible with future versions of GTK+:

    - Do not configure Pango or GTK+ with the --enable-static or
      --enable-explicit-deps options, since they will cause dependencies 
      on the particular version of Xft.

    - Do not use Xft version 1 directly in your applications.

* There is a bug in the Xft library in XFree86-4.1 and possibly previous
  versions that causes random crashes when using the Pango Xft
  backend. If you want to use Xft fonts, you should upgrade to
  XFree86-4.2.

* Xft support is on by default when using Xft2 but off by
  default when using Xft1. To change this default, set the
  variable GDK_USE_XFT to '1' or '0'. For instance, to 
  turn on Xft fonts when Xft1.

   GDK_USE_XFT=1
   export GDK_USE_XFT

* The gdk_pixbuf_xlib library included in the contrib/ directory of GTK+
  is provided on a as-is basis and has not been tested at all. No
  guarantees about the degree of workingness or about future
  compatibility are provided.

* While efforts have been made to make gdk-pixbuf robust against
  invalid images, using gdk-pixbuf to load untrusted data 
  is not recommended, due to the likelyhood that there are
  additional problems where an invalid image could cause
  gdk-pixbuf to crash or worse.

* The assumption of GLib and GTK+ by default is that filenames on the
  filesystem are encoded in UTF-8 rather than the encoding of the locale;
  The GTK+ developers consider that having filenames whose interpretation
  depends on the current locale is fundamentally a bad idea.

  If you have filenames encoded in the encoding of your locale, then
  you may want to set the G_BROKEN_FILENAMES environment variable:
  
   G_BROKEN_FILENAMES=1
   export G_BROKEN_FILENAMES

  Best integration of GTK+-2.2 with the environment is achieved by 
  using a UTF-8 locale.

How to report bugs
==================

Bugs should be reported to the GNOME bug tracking system.
(http://bugzilla.gnome.org, product gtk+.) You will need to create an
account for yourself.
  
In the bug report please include:
  
* Information about your system. For instance:

   - What operating system and version
   - What version of X
   - For Linux, what version of the C library

  And anything else you think is relevant.

* How to reproduce the bug. 

  If you can reproduce it with the testgtk program that is built in the
  gtk/ subdirectory, that will be most convenient.  Otherwise, please
  include a short test program that exhibits the behavior.  As a last
  resort, you can also provide a pointer to a larger piece of software
  that can be downloaded.

* If the bug was a crash, the exact text that was printed out when the
  crash occured.

* Further information such as stack traces may be useful, but is not
  necessary. If you do send a stack trace, and the error is an X error,
  it will be more useful if the stacktrace is produced running the test
  program with the --sync command line option.

Patches
=======

Patches should also be submitted to bugzilla.gnome.org. If the patch
fixes an existing bug, add the patch as an attachment to that bug
report.

Otherwise, enter a new bug report that describes the patch, and attach
the patch to that bug report.

Bug reports containing patches should include the PATCH keyword in their
keyword fields. If the patch adds to or changes the GTK programming
interface, the API keyword should also be included.
  
Patches should be in unified diff form. (The -u option to GNU diff.)
Description
No description provided
Readme 363 MiB
Languages
C 88.6%
CSS 10.1%
Meson 0.4%
SCSS 0.4%
JavaScript 0.2%
Other 0.1%