summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
Diffstat (limited to 'README')
-rw-r--r--README42
1 files changed, 32 insertions, 10 deletions
diff --git a/README b/README
index bdc28f335..4b6ba7619 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
General Information
===================
-This is GTK+ version 2.10.2. GTK+ is a multi-platform toolkit for
+This is GTK+ version 2.11.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.
@@ -27,6 +27,27 @@ Installation
See the file 'INSTALL'
+Release notes for 2.12
+======================
+
+* Functions: gtk_about_dialog_get/set_name() were deprecated in favour of
+ gtk_about_dialog_get/set_program_name(), the GtkAboutDialog now uses the
+ "program-name" property instead of the conflicting "name" property.
+
+* The tiff loader now requires libtiff 3.6.0 or later.
+
+* Support for Windows 9x/ME has officially been removed. It hasn't worked
+ since 2.6 anyway.
+
+* The GtkTextBufferTargetInfo enumeration values have been changed from
+ G_MAXUINT-0, G_MAXUINT-1, G_MAXUINT-2, etc, to -1, -2, -3 to stay within
+ ANSI C limits.
+
+* A change in the handling of _NET_WM_USER_TIME properties on toplevel
+ windows can cause deadlock problems with window managers that are using
+ GDK for drawing decorations. In particular, metacity <= 2.18.0 is affected
+ by this. The problem has been fixed in metacity 2.18.1.
+
Release notes for 2.10
======================
@@ -126,7 +147,7 @@ Release notes for 2.8
Release notes for 2.6
=====================
-* GTK+ 2.6 supports clipboard persistence. To make use of this feature,
+* 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/clipboard-manager-spec
must be running. A sample implementation of such a clipboard manager
@@ -137,11 +158,11 @@ Release notes for 2.6
* 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 ownership
+ 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 environment variable may be
+ specification. Setting the XDG_DATA_DIRS environtment variable may be
necessary if your icons aren't installed in the default location
/usr/share/icons.
@@ -151,7 +172,7 @@ Release notes for 2.6
see the gtk-update-icon-cache man page or the GTK+ documentation.
* To reduce code size and improve efficiency, GTK+, when compiled
- with the GNU tool chain, has separate internal and external entry
+ 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.
@@ -179,7 +200,7 @@ Release notes for 2.6
compatibility are provided.
* On Unix, the assumption of GLib and GTK+ by default is that filenames on
- the file system are encoded in UTF-8 rather than the encoding of the locale;
+ 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.
@@ -197,7 +218,7 @@ Release notes for 2.6
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 code page was used. As 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.
@@ -233,7 +254,7 @@ In the bug report please include:
that can be downloaded.
* If the bug was a crash, the exact text that was printed out when the
- crash occurred.
+ 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,
@@ -251,7 +272,8 @@ report.
Otherwise, enter a new bug report that describes the patch, and attach
the patch to that bug report.
-Bug reports containing patches that add to or change the GTK+ programming
-interface should include the API keyword in their keyword fields.
+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.)