[gdk-pixbuf] Removed entities from the code markup as they are not being expanded

[Xabier Rodriguez Calvar <xrcalvar src gnome org>]

commit 53af8a11cba05072c8f0117fa9bb18a823941750
Author: Xabier Rodriguez Calvar <xrcalvar igalia com>
Date:   Mon Jul 30 13:16:46 2012 +0200

    Removed entities from the code markup as they are not being expanded

 gdk-pixbuf/gdk-pixbuf-animation.c |    4 ++--
 gdk-pixbuf/gdk-pixbuf-io.c        |   16 ++++++++--------
 gdk-pixbuf/gdk-pixbuf-scale.c     |    2 +-
 gdk-pixbuf/gdk-pixdata.c          |    2 +-
 4 files changed, 12 insertions(+), 12 deletions(-)
---
diff --git a/gdk-pixbuf/gdk-pixbuf-animation.c b/gdk-pixbuf/gdk-pixbuf-animation.c
index fda0b23..c342def 100644
--- a/gdk-pixbuf/gdk-pixbuf-animation.c
+++ b/gdk-pixbuf/gdk-pixbuf-animation.c
@@ -35,13 +35,13 @@
  * @Title: Animations
  * @See_also: #GdkPixbufLoader.
  * 
- * The &gdk-pixbuf; library provides a simple mechanism to load and
+ * The GdkPixBuf library provides a simple mechanism to load and
  * represent animations. An animation is conceptually a series of
  * frames to be displayed over time. The animation may not be
  * represented as a series of frames internally; for example, it may
  * be stored as a sprite and instructions for moving the sprite around
  * a background. To display an animation you don't need to understand
- * its representation, however; you just ask &gdk-pixbuf; what should
+ * its representation, however; you just ask GdkPixBuf what should
  * be displayed at a given point in time.
  * 
  */
diff --git a/gdk-pixbuf/gdk-pixbuf-io.c b/gdk-pixbuf/gdk-pixbuf-io.c
index ccfb9a4..0106c47 100644
--- a/gdk-pixbuf/gdk-pixbuf-io.c
+++ b/gdk-pixbuf/gdk-pixbuf-io.c
@@ -56,7 +56,7 @@
  * @Title: File Loading
  * @See_also: #GdkPixbufLoader.
  * 
- * The &gdk-pixbuf; library provides a simple mechanism for loading
+ * The GdkPixBuf library provides a simple mechanism for loading
  * an image from a file in synchronous fashion.  This means that the
  * library takes control of the application while the file is being
  * loaded; from the user's point of view, the application will block
@@ -76,17 +76,17 @@
  * 
  * These functions allow to save a #GdkPixbuf in a number of 
  * file formats. The formatted data can be written to a file
- * or to a memory buffer. &gdk-pixbuf; can also call a user-defined
+ * or to a memory buffer. GdkPixBuf can also call a user-defined
  * callback on the data, which allows to e.g. write the image 
  * to a socket or store it in a database.
  */
 
 /**
  * SECTION:module_interface
- * @Short_description: Extending &gdk-pixbuf;
+ * @Short_description: Extending GdkPixBuf
  * @Title: Module Interface
  * 
- * If &gdk-pixbuf; has been compiled with GModule support, it can be extended by
+ * If GdkPixBuf has been compiled with GModule support, it can be extended by
  * modules which can load (and perhaps also save) new image and animation
  * formats. Each loadable module must export a
  * #GdkPixbufModuleFillInfoFunc function named <function>fill_info</function> and
@@ -99,7 +99,7 @@
  * signatures (and other information) via the <function>fill_info</function>
  * function. An external utility, <command>gdk-pixbuf-query-loaders</command>, 
  * uses this to create a text file containing a list of all available loaders and 
- * their signatures. This file is then read at runtime by &gdk-pixbuf; to obtain
+ * their signatures. This file is then read at runtime by GdkPixBuf to obtain
  * the list of available loaders and their signatures. 
  * 
  * 
@@ -108,7 +108,7 @@
  * <function>fill_vtable</function> function will simply not set the corresponding
  * function pointers of the #GdkPixbufModule structure. If a module supports
  * incremental loading (i.e. provides #begin_load, #stop_load and
- * #load_increment), it doesn't have to implement #load, since &gdk-pixbuf; can 
+ * #load_increment), it doesn't have to implement #load, since GdkPixBuf can
  * supply a generic #load implementation wrapping the incremental loading. 
  * 
  * 
@@ -128,11 +128,11 @@
  * </itemizedlist>
  * 
  * 
- * The &gdk-pixbuf; interfaces needed for implementing modules are contained in 
+ * The GdkPixBuf interfaces needed for implementing modules are contained in
  * <filename>gdk-pixbuf-io.h</filename> (and
  * <filename>gdk-pixbuf-animation.h</filename> if the module supports animations).
  * They are not covered by the same stability guarantees as the regular 
- * &gdk-pixbuf; API. To underline this fact, they are protected by 
+ * GdkPixBuf API. To underline this fact, they are protected by
  * <literal>#ifdef GDK_PIXBUF_ENABLE_BACKEND</literal>.
  */
 
diff --git a/gdk-pixbuf/gdk-pixbuf-scale.c b/gdk-pixbuf/gdk-pixbuf-scale.c
index 6dbe18b..45706f4 100644
--- a/gdk-pixbuf/gdk-pixbuf-scale.c
+++ b/gdk-pixbuf/gdk-pixbuf-scale.c
@@ -33,7 +33,7 @@
  * @Title: Scaling
  * @See_also:    <link linkend="gdk-GdkRGB">GdkRGB</link>.
  * 
- * The &gdk-pixbuf; contains functions to scale pixbufs, to scale
+ * The GdkPixBuf contains functions to scale pixbufs, to scale
  * pixbufs and composite against an existing image, and to scale
  * pixbufs and composite against a solid color or checkerboard.
  * Compositing a checkerboard is a common way to show an image with
diff --git a/gdk-pixbuf/gdk-pixdata.c b/gdk-pixbuf/gdk-pixdata.c
index 8680229..a7a92aa 100644
--- a/gdk-pixbuf/gdk-pixdata.c
+++ b/gdk-pixbuf/gdk-pixdata.c
@@ -29,7 +29,7 @@
  * 
  * Using #GdkPixdata, images can be compiled into an application,
  * making it unnecessary to refer to external image files at runtime.
- * &gdk-pixbuf; includes a utility named gdk-pixbuf-csource, which 
+ * GdkPixBuf includes a utility named gdk-pixbuf-csource, which
  * can be used to convert image files into #GdkPixdata structures suitable
  * for inclusion in C sources. To convert the #GdkPixdata structures back 
  * into #GdkPixbuf<!-- -->s, use gdk_pixbuf_from_pixdata.