2.6.0

1 files changed, 32 insertions, 30 deletions

diff --git a/README.in b/README.in
index 0ba1ea0ba..a5c5945b6 100644
--- a/README.in
+++ b/README.in
@@ -30,29 +30,32 @@ Release notes
 
 * GTK+ 2.6 supports clipboard persistency. To make use of this feature,
   a clipboard manager following the specification at
-  http://www.freedesktop.org/wiki/Standards_2fclipboard_2dmanager_2dspec
+  http://www.freedesktop.org/wiki/Standards/clipboard-manager-spec
   must be running. A sample implementation of such a clipboard manager
   is available at 
   http://people.imendio.com/andersca/archives/clipboard-manager-0.3.tar.gz
+  Applications can use the function gdk_display_supports_clipboard_persistence() 
+  to find out if clipboard persistence is available.
 
-* The icon theme code in GTK+ 2.6 follows the icon theme specification.
-  Therefore, icon themes are looked for in $HOME/.icons, $XDG_DATA_HOME/icons, 
-  $XDG_DATA_DIRS/icons and /usr/share/pixmaps.
+* Notification on clipboard ownership changes via GdkOwnerChange events 
+  requires the XFIXES X extension. Applications can use the function
+  gdk_display_supports_selection_notification() to find out if ownerchip
+  change notification is available.
+
+* The icon theme code in GTK+ 2.6 follows the freedesktop.org icon theme 
+  specification. Setting the XDG_DATA_DIRS environtment variable may be 
+  necessary if your icons aren't installed in the default location 
+  /usr/share/icons.
 
 * The icon theme code in GTK+ 2.6 can make use of mmap()able cache files
   to avoid a lot of disk searching overhead. GTK+ includes a utility named
   gtk-update-icon-cache to generate these cache files. For further details,
   see the gtk-update-icon-cache man page or the GTK+ documentation.
 
-* GTK+ uses a technique involving macros for reducing the amount of PLT
-  redirections which has the side effect that the names of internally used
-  GLib functions are prefixed with IA__. The g_return_if_fail() macros
-  strip this prefix away, but it will show up e.g. in a debugger.
-
-* The linux framebuffer GDK backend included in the gdk/linux-fb 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.
+* To reduce code size and improve efficiency, GTK+, when compiled 
+  with the GNU toolchain, has separate internal and external entry 
+  points for exported functions. The internal names, which begin with 
+  IA__, may be seen when debugging a GTK+ program.
 
 * The following functions have been deprecated in GTK+ 2.6:
   gdk_pango_context_set_colormap
@@ -71,19 +74,19 @@ Release notes
   symbols private which were not in any installed header files and
   were never intended to be exported.
 
-* 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
+* The gdk_pixbuf_xlib library included in the contrib/ directory 
+  and the framebuffer GDK backend included in the gdk/linux-fb directory
+  of GTK+ are provided on an as-is basis and have not been tested at all. 
+  No guarantees about the degree of workingness or about future
   compatibility are provided.
 
-* 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;
+* On Unix, 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.
 
-  On Unix, if you have filenames encoded in the encoding of your
-  locale, then you may want to set the G_FILENAME_ENCODING environment
-  variable:
+  If you have filenames encoded in the encoding of your locale, then you 
+  may want to set the G_FILENAME_ENCODING environment variable:
   
    G_FILENAME_ENCODING=@local
    export G_FILENAME_ENCODING
@@ -94,17 +97,16 @@ Release notes
   Best integration of GTK+ 2.6 with the environment is achieved by 
   using a UTF-8 locale.
 
-  On Windows, filenames passed to GTK+ should always be in UTF-8, like
+  On Windows, filenames passed to GTK+ should always be in UTF-8, as
   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
+  where the system codepage was used. As 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.
+  consideration, and use the gstdio wrappers to access files whose 
+  names have been constructed from strings returned from GTK+ or GLib.
 
 How to report bugs
 ==================
@@ -125,10 +127,10 @@ In the bug report please include:
 
 * 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
+  If you can reproduce it with one of the tests or demos built with GTK+, 
+  such as demos/gtk-demo/gtk-demo, that would 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