gtk2 0.90.2-x86-mingw32 → 0.90.3-x86-mingw32

data/vendor/local/share/aclocal/pkg.m4

@@ -1,155 +0,0 @@
-# pkg.m4 - Macros to locate and utilise pkg-config.            -*- Autoconf -*-
-# 
-# Copyright © 2004 Scott James Remnant <scott@netsplit.com>.
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2 of the License, or
-# (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful, but
-# WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
-# General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
-#
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# PKG_PROG_PKG_CONFIG([MIN-VERSION])
-# ----------------------------------
-AC_DEFUN([PKG_PROG_PKG_CONFIG],
-[m4_pattern_forbid([^_?PKG_[A-Z_]+$])
-m4_pattern_allow([^PKG_CONFIG(_PATH)?$])
-AC_ARG_VAR([PKG_CONFIG], [path to pkg-config utility])dnl
-if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then
-	AC_PATH_TOOL([PKG_CONFIG], [pkg-config])
-fi
-if test -n "$PKG_CONFIG"; then
-	_pkg_min_version=m4_default([$1], [0.9.0])
-	AC_MSG_CHECKING([pkg-config is at least version $_pkg_min_version])
-	if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then
-		AC_MSG_RESULT([yes])
-	else
-		AC_MSG_RESULT([no])
-		PKG_CONFIG=""
-	fi
-		
-fi[]dnl
-])# PKG_PROG_PKG_CONFIG
-
-# PKG_CHECK_EXISTS(MODULES, [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND])
-#
-# Check to see whether a particular set of modules exists.  Similar
-# to PKG_CHECK_MODULES(), but does not set variables or print errors.
-#
-#
-# Similar to PKG_CHECK_MODULES, make sure that the first instance of
-# this or PKG_CHECK_MODULES is called, or make sure to call
-# PKG_CHECK_EXISTS manually
-# --------------------------------------------------------------
-AC_DEFUN([PKG_CHECK_EXISTS],
-[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl
-if test -n "$PKG_CONFIG" && \
-    AC_RUN_LOG([$PKG_CONFIG --exists --print-errors "$1"]); then
-  m4_ifval([$2], [$2], [:])
-m4_ifvaln([$3], [else
-  $3])dnl
-fi])
-
-
-# _PKG_CONFIG([VARIABLE], [COMMAND], [MODULES])
-# ---------------------------------------------
-m4_define([_PKG_CONFIG],
-[if test -n "$$1"; then
-    pkg_cv_[]$1="$$1"
- elif test -n "$PKG_CONFIG"; then
-    PKG_CHECK_EXISTS([$3],
-                     [pkg_cv_[]$1=`$PKG_CONFIG --[]$2 "$3" 2>/dev/null`],
-		     [pkg_failed=yes])
- else
-    pkg_failed=untried
-fi[]dnl
-])# _PKG_CONFIG
-
-# _PKG_SHORT_ERRORS_SUPPORTED
-# -----------------------------
-AC_DEFUN([_PKG_SHORT_ERRORS_SUPPORTED],
-[AC_REQUIRE([PKG_PROG_PKG_CONFIG])
-if $PKG_CONFIG --atleast-pkgconfig-version 0.20; then
-        _pkg_short_errors_supported=yes
-else
-        _pkg_short_errors_supported=no
-fi[]dnl
-])# _PKG_SHORT_ERRORS_SUPPORTED
-
-
-# PKG_CHECK_MODULES(VARIABLE-PREFIX, MODULES, [ACTION-IF-FOUND],
-# [ACTION-IF-NOT-FOUND])
-#
-#
-# Note that if there is a possibility the first call to
-# PKG_CHECK_MODULES might not happen, you should be sure to include an
-# explicit call to PKG_PROG_PKG_CONFIG in your configure.ac
-#
-#
-# --------------------------------------------------------------
-AC_DEFUN([PKG_CHECK_MODULES],
-[AC_REQUIRE([PKG_PROG_PKG_CONFIG])dnl
-AC_ARG_VAR([$1][_CFLAGS], [C compiler flags for $1, overriding pkg-config])dnl
-AC_ARG_VAR([$1][_LIBS], [linker flags for $1, overriding pkg-config])dnl
-
-pkg_failed=no
-AC_MSG_CHECKING([for $1])
-
-_PKG_CONFIG([$1][_CFLAGS], [cflags], [$2])
-_PKG_CONFIG([$1][_LIBS], [libs], [$2])
-
-m4_define([_PKG_TEXT], [Alternatively, you may set the environment variables $1[]_CFLAGS
-and $1[]_LIBS to avoid the need to call pkg-config.
-See the pkg-config man page for more details.])
-
-if test $pkg_failed = yes; then
-        _PKG_SHORT_ERRORS_SUPPORTED
-        if test $_pkg_short_errors_supported = yes; then
-	        $1[]_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors "$2" 2>&1`
-        else 
-	        $1[]_PKG_ERRORS=`$PKG_CONFIG --print-errors "$2" 2>&1`
-        fi
-	# Put the nasty error message in config.log where it belongs
-	echo "$$1[]_PKG_ERRORS" >&AS_MESSAGE_LOG_FD
-
-	ifelse([$4], , [AC_MSG_ERROR(dnl
-[Package requirements ($2) were not met:
-
-$$1_PKG_ERRORS
-
-Consider adjusting the PKG_CONFIG_PATH environment variable if you
-installed software in a non-standard prefix.
-
-_PKG_TEXT
-])],
-		[AC_MSG_RESULT([no])
-                $4])
-elif test $pkg_failed = untried; then
-	ifelse([$4], , [AC_MSG_FAILURE(dnl
-[The pkg-config script could not be found or is too old.  Make sure it
-is in your PATH or set the PKG_CONFIG environment variable to the full
-path to pkg-config.
-
-_PKG_TEXT
-
-To get pkg-config, see <http://pkg-config.freedesktop.org/>.])],
-		[$4])
-else
-	$1[]_CFLAGS=$pkg_cv_[]$1[]_CFLAGS
-	$1[]_LIBS=$pkg_cv_[]$1[]_LIBS
-        AC_MSG_RESULT([yes])
-	ifelse([$3], , :, [$3])
-fi[]dnl
-])# PKG_CHECK_MODULES

data/vendor/local/share/doc/gtk+-bundle_2.20.1-20100912_win32/components.lst

@@ -1,24 +0,0 @@
-gettext-runtime_0.18.1.1-2_win32
-gettext-runtime-dev_0.18.1.1-2_win32
-glib_2.24.2-2_win32
-glib-dev_2.24.2-2_win32
-pkg-config_0.23-3_win32
-pkg-config-dev_0.23-3_win32
-atk_1.30.0-2_win32
-atk-dev_1.30.0-2_win32
-pango_1.28.1-2_win32
-pango-dev_1.28.1-2_win32
-cairo_1.10.0-1_win32
-cairo-dev_1.10.0-1_win32
-fontconfig_2.8.0-2_win32
-fontconfig-dev_2.8.0-2_win32
-expat_2.0.1-1_win32
-expat-dev_2.0.1-1_win32
-freetype_2.4.2-1_win32
-freetype-dev_2.4.2-1_win32
-libpng_1.4.3-1_win32
-libpng-dev_1.4.3-1_win32
-zlib_1.2.5-2_win32
-zlib-dev_1.2.5-2_win32
-gtk+_2.20.1-3_win32
-gtk+-dev_2.20.1-3_win32

data/vendor/local/share/gtk-doc/html/gdk-pixbuf/apa.html

@@ -1,66 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Appendix A. Porting applications from Imlib to gdk-pixbuf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GDK-PixBuf Reference Manual">
-<link rel="up" href="index.html" title="GDK-PixBuf Reference Manual">
-<link rel="prev" href="api-index-2-14.html" title="Index of new symbols in 2.14">
-<link rel="next" href="apas02.html" title="Differences between Imlib and gdk-pixbuf">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="api-index-2-14.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td> </td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GDK-PixBuf Reference Manual</th>
-<td><a accesskey="n" href="apas02.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="appendix" title="Appendix A. Porting applications from Imlib to gdk-pixbuf">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="id479230"></a>Appendix A. Porting applications from <span class="application">Imlib</span> to <span class="application">gdk-pixbuf</span>
-</h2></div></div></div>
-<p>
-      This appendix contains the basic steps needed to port an
-      application that uses the <span class="application">Imlib</span> library to use <span class="application">gdk-pixbuf</span>
-      instead.
-    </p>
-<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
-<h3 class="title">Note</h3>
-<p>
-	This appendix refers to version 1 of the <span class="application">Imlib</span> library; this
-	discussion is not relevant to Imlib 2.  Also, we discuss the
-	gdk_imlib API instead of the Xlib-based API.
-      </p>
-</div>
-<div class="sect1" title="Introduction">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id436034"></a>Introduction</h2></div></div></div>
-<p>
-	Prior to the GNOME 1.2 platform, the <span class="application">Imlib</span> library was the
-	preferred way of loading and rendering images in GNOME
-	applications.  Unfortunately, <span class="application">Imlib</span> has important design
-	limitations that make it hard to write efficient and highly
-	modular applications.
-      </p>
-<p>
-	The <span class="application">gdk-pixbuf</span> library was designed as a solution to
-	<span class="application">Imlib</span>'s shortcomings.  It provides a simple, orthogonal API
-	and convenience functions for the most common operations.  In
-	addition, it supports full transparency information for
-	images, or alpha channel.  More importantly, it has
-	well-defined semantics for memory management through the use
-	of reference counting; <span class="application">Imlib</span> has an intractably complex
-	memory management mechanism and cache that will make your head
-	spin.
-      </p>
-</div>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.14</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gdk-pixbuf/apas02.html

@@ -1,140 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Differences between Imlib and gdk-pixbuf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GDK-PixBuf Reference Manual">
-<link rel="up" href="apa.html" title="Appendix A. Porting applications from Imlib to gdk-pixbuf">
-<link rel="prev" href="apa.html" title="Appendix A. Porting applications from Imlib to gdk-pixbuf">
-<link rel="next" href="apas03.html" title="Converting Applications to gdk-pixbuf">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="apa.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="apa.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GDK-PixBuf Reference Manual</th>
-<td><a accesskey="n" href="apas03.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="sect1" title="Differences between Imlib and gdk-pixbuf">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id496665"></a>Differences between <span class="application">Imlib</span> and <span class="application">gdk-pixbuf</span>
-</h2></div></div></div>
-<p>
-	Generally, applications that use <span class="application">Imlib</span> do not have to be
-	changed extensively to use <span class="application">gdk-pixbuf</span>; its simple and
-	flexible API makes things easy.  This section describes the
-	differences between <span class="application">Imlib</span> and <span class="application">gdk-pixbuf</span>; you should take
-	these into account when modifying your applications to use
-	<span class="application">gdk-pixbuf</span>.
-      </p>
-<div class="sect2" title="Initialization">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id478921"></a>Initialization</h3></div></div></div>
-<p>
-	  The <span class="application">gdk-pixbuf</span> library does not need to be initialized.
-	</p>
-<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
-<h3 class="title">Note</h3>
-<p>
-	    In GNOME applications you normally don't need to
-	    initialize <span class="application">Imlib</span>, as <code class="function">gnome_init()</code>
-	    calls <code class="function">gdk_imlib_init()</code> automatically.
-	  </p>
-</div>
-</div>
-<div class="sect2" title="Memory management">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id528688"></a>Memory management</h3></div></div></div>
-<p>
-	  The <span class="application">gdk-pixbuf</span> library provides a simple, well-defined
-	  memory management mechanism for images in the form of
-	  reference counting.  This makes it very convenient to use
-	  for large-scale applications that need to share images
-	  between different parts of the program.  In stark contrast,
-	  <span class="application">Imlib</span> has a terribly complex mechanism of an image and
-	  pixmap cache which makes it very hard for applications to
-	  share image structures between different parts of the
-	  program.  Unfortunately this mechanism makes things very
-	  prone to memory leaks and tricky bugs.
-	</p>
-<p>
-	  The basic principle in <span class="application">gdk-pixbuf</span> is that when you obtain
-	  a new <a class="link" href="gdk-pixbuf-gdk-pixbuf.html#GdkPixbuf">GdkPixbuf</a> structure,
-	  it is created with an initial reference count of 1.  When
-	  another part of the program wants to keep a reference to the
-	  pixbuf, it should call <code class="function">g_object_ref()</code>;
-	  this will increase the reference count by 1.  When some part
-	  of the program does not need to keep a reference to a pixbuf
-	  anymore and wants to release the pixbuf, it should call
-	  <code class="function">g_object_unref()</code>; this will decrease
-	  the reference count by 1.  When the reference count drops to
-	  zero, the pixbuf gets destroyed or
-	  <span class="emphasis"><em>finalized</em></span> and its memory is freed.
-	</p>
-<p>
-	  For applications that need to implement a cache of loaded
-	  images, <span class="application">gdk-pixbuf</span> provides a way to hook to the last
-	  unreference operation of a pixbuf; instead of finalizing the
-	  pixbuf, the user-installed hook can decide to keep it around
-	  in a cache instead.
-	</p>
-<p>
-	  Finally, <span class="application">gdk-pixbuf</span> does not provide a cache of rendered
-	  pixmaps.  This is unnecessary for most applications, since
-	  the scaling and rendering functions are quite fast and
-	  applications may need to use subtly different values each
-	  time they call these functions, for example, to take into
-	  account dithering and zooming offsets.
-	</p>
-<p>
-	  Most applications will simply need to call
-	  <code class="function">g_object_ref()</code> when they want to keep
-	  an extra reference to a pixbuf, and then
-	  <code class="function">g_object_unref()</code> when they are done
-	  with it.
-	</p>
-</div>
-<div class="sect2" title="The Rendering Process">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id522182"></a>The Rendering Process</h3></div></div></div>
-<p>
-	  The <span class="application">gdk-pixbuf</span> library has the policy of always rendering
-	  pixbufs to GDK drawables you provide; it will not create
-	  them for you.  This is in general more flexible than
-	  <span class="application">Imlib</span>'s policy of always creating a pixmap and making you
-	  use that instead.
-	</p>
-<p>
-	  The disadvantage of always having a pixmap created for you
-	  is that it wastes memory in the X server if you intend to
-	  copy that rendered data onto another drawable, for example,
-	  the final destination window or a temporary pixmap for
-	  drawing.  This is the most common case, unfortunately, so
-	  the <span class="application">Imlib</span> policy introduces unnecessary copying.
-	</p>
-<p>
-	  Also, <span class="application">Imlib</span> can only render pixmaps that are the whole
-	  size of the source image; you cannot render just a subset
-	  region of the image.  This is inconvenient for applications
-	  that need to render small portions at a time, such as
-	  applications that do scrolling.  Since the whole image must
-	  be rendered at a time, this can lead to performance and
-	  memory usage problems.
-	</p>
-<p>
-	  The <span class="application">gdk-pixbuf</span> library lets you render any rectangular
-	  region from an image onto any drawable that you provide.
-	  This lets the application have fine control the way images
-	  are rendered.
-	</p>
-</div>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.14</div>
-</body>
-</html>

data/vendor/local/share/gtk-doc/html/gdk-pixbuf/apas03.html

@@ -1,174 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Converting Applications to gdk-pixbuf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
-<link rel="home" href="index.html" title="GDK-PixBuf Reference Manual">
-<link rel="up" href="apa.html" title="Appendix A. Porting applications from Imlib to gdk-pixbuf">
-<link rel="prev" href="apas02.html" title="Differences between Imlib and gdk-pixbuf">
-<link rel="next" href="license.html" title="Appendix B. License">
-<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
-<link rel="stylesheet" href="style.css" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
-<td><a accesskey="p" href="apas02.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
-<td><a accesskey="u" href="apa.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
-<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
-<th width="100%" align="center">GDK-PixBuf Reference Manual</th>
-<td><a accesskey="n" href="license.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
-</tr></table>
-<div class="sect1" title="Converting Applications to gdk-pixbuf">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id517491"></a>Converting Applications to <span class="application">gdk-pixbuf</span>
-</h2></div></div></div>
-<p>
-	This sections describes the actual changes you need to make in
-	an <span class="application">Imlib</span> program to make it use <span class="application">gdk-pixbuf</span> instead.
-      </p>
-<div class="sect2" title="Image loading and creation">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id517520"></a>Image loading and creation</h3></div></div></div>
-<p>
-	  The <span class="application">gdk-pixbuf</span> library can load image files synchronously
-	  (i.e. with a single function call), create images from RGB
-	  data in memory, and as a convenience, it can also create
-	  images from inline XPM data.
-	</p>
-<p>
-	  To load an image file in a single function call, simply use
-	  <code class="function">gdk_pixbuf_new_from_file()</code>.  Note that
-	  this will make the program block until the whole file has
-	  been read.  This function effectively replaces
-	  <code class="function">gdk_imlib_load_image()</code>.
-	</p>
-<p>
-	  If you have RGB data in memory, you can use
-	  <code class="function">gdk_pixbuf_new_from_data()</code> to create a
-	  pixbuf out of it; this is a replacement for
-	  <code class="function">gdk_imlib_create_image_from_data()</code>.
-	  <span class="application">gdk-pixbuf</span> does not copy the image data; it is up to you
-	  to define the ownership policy by providing a destroy
-	  notification function that will be called when the image
-	  data needs to be freed.  The function you provide can then
-	  free the data or do something else, as appropriate.
-	</p>
-<p>
-	  As a convenience, you can use the
-	  <code class="function">gdk_pixbuf_new_from_xpm_data()</code> function
-	  to create a pixbuf out of inline XPM data that was compiled
-	  into your C program.  This is a replacement for
-	  <code class="function">gdk_imlib_create_image_from_xpm_data()</code>.
-	</p>
-<p>
-	  After you have created a pixbuf, you can manipulate it in
-	  any way you please and then finally call
-	  <code class="function">g_object_unref()</code> when you are done
-	  with it.  This can be thought of as a replacement for
-	  <code class="function">gdk_imlib_destroy_image()</code> but with much
-	  cleaner semantics.
-	</p>
-</div>
-<div class="sect2" title="Rendering Images">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id516581"></a>Rendering Images</h3></div></div></div>
-<p>
-	  Applications that use <span class="application">Imlib</span> must first call
-	  <code class="function">gdk_imlib_render()</code> to render the whole
-	  image data onto a pixmap that <span class="application">Imlib</span> creates.  Then they
-	  must copy that pixmap's data into the final destination for
-	  the image.
-	</p>
-<p>
-	  In contrast, <span class="application">gdk-pixbuf</span> provides convenience functions to
-	  render arbitrary rectangular regions of an image onto a
-	  drawable that your application provides.  You can use
-	  <code class="function">gdk_draw_pixbuf()</code> to do this; having
-          your application provide the destination drawable and
-	  specify an arbitrary region means your application has
-          complete control over the way images are rendered.
-	</p>
-<p>
-	  As a convenience, <span class="application">gdk-pixbuf</span> also provides the
-	  <code class="function">gdk_pixbuf_render_pixmap_and_mask()</code>
-	  function; this will create new pixmap and mask drawables for
-	  a whole pixbuf and render the image data onto them.  Only
-	  trivially simple applications should find a use for this
-	  function, since usually you want finer control of how things
-	  are rendered.
-	</p>
-</div>
-<div class="sect2" title="Scaling Images">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id521103"></a>Scaling Images</h3></div></div></div>
-<p>
-	  <span class="application">Imlib</span> lets you render scaled image data at the time you
-	  call <code class="function">gdk_imlib_render()</code>.  Again, this
-	  unfortunately scales and renders the whole image onto a new
-	  pixmap.
-	</p>
-<p>
-	  <span class="application">gdk-pixbuf</span> provides a number of functions that do scaling
-	  of arbitrary regions of a source pixbuf onto a destination
-	  one.  These functions can also perform compositing
-	  operations against the data in the destination pixbuf or
-	  against a solid color or a colored checkerboard.
-	  <sup>[<a name="id523191" href="#ftn.id523191" class="footnote">1</a>]</sup>
-	</p>
-<p>
-	  Very simple applications may find it sufficient to use
-	  <code class="function">gdk_pixbuf_scale_simple()</code> or
-	  <code class="function">gdk_pixbuf_composite_color_simple()</code>.
-	  These functions scale the whole source image at a time and
-	  create a new pixbuf with the result.
-	</p>
-<p>
-	  More sophisticated applications will need to use
-	  <code class="function">gdk_pixbuf_scale()</code>,
-	  <code class="function">gdk_pixbuf_composite()</code>, or
-	  <code class="function">gdk_pixbuf_composite_color()</code> instead.
-	  These functions let you scale and composite an arbitrary
-	  region of the source pixbuf onto a destination pixbuf that
-	  you provide.
-	</p>
-</div>
-<div class="sect2" title="Getting Image Data from a Drawable">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id523249"></a>Getting Image Data from a Drawable</h3></div></div></div>
-<p>
-	  <span class="application">Imlib</span> lets you create an image by fetching a drawable's
-	  contents from the X server and converting those into RGB
-	  data.  This is done with the
-	  <code class="function">gdk_imlib_create_image_from_drawable()</code>
-	  function.
-	</p>
-<p>
-	  <span class="application">gdk-pixbuf</span> provides the
-	  <code class="function">gdk_pixbuf_get_from_drawable()</code> function
-	  instead.  It lets you specify a destination pixbuf instead
-	  of always creating a new one for you.
-	</p>
-</div>
-<div class="footnotes">
-<br><hr width="100" align="left">
-<div class="footnote">
-<p><sup>[<a name="ftn.id523191" href="#id523191" class="para">1</a>] </sup>
-	      You can use a colored checkerboard as the background for
-	      compositing when you want to provide a visual indication
-	      that the image has partially opaque areas.  This is
-	      normally used in image editing and viewing programs.
-	    </p>
-<p>
-	      Compositing against a single solid color is actually a
-	      special case of a checkerboard; it simply uses checks of
-	      the same color.
-	    </p>
-</div>
-</div>
-</div>
-<div class="footer">
-<hr>
-          Generated by GTK-Doc V1.14</div>
-</body>
-</html>