1. libgd
  2. Untitled project
  3. gd-libgd

Commits

pajoye  committed be95d25

- 2.1.x+ will not have this file

  • Participants
  • Parent commits fc4f42e
  • Branches GD-2.0

Comments (0)

Files changed (1)

File src/index.html

  • Ignore whitespace
-<!-- REMEMBER TO EDIT index.html.source -->
-<head>
-<TITLE>gd 2.0.34</TITLE>
-</head>
-<body bgcolor="#FFFFFF">
-<!-- BANNER HERE -->
-<H2>gd 2.0.33</H2>
-<H3>A graphics library for fast image creation</H3>
-<H3>Follow this link to the
-<A HREF="http://libgd.org">latest version
-of this document</A>.</H3>
-<blockquote>
-<strong>UPGRADING UNIX USERS: READ THIS FIRST!</strong>
-Modern versions of gd install by default to /usr/local/lib and
-/usr/local/include. If you already have an older version of gd
-in /usr/lib and /usr/include, you may wish to use:
-<pre>
-./configure --prefix=/usr</pre> 
-To ensure that your
-new installation overwrites the old.
-<p>
-<strong>GIF support has been restored in gd 2.0.28 and above.</strong>
-The well-known patents on LZW compression held by Unisys
-have expired in all countries. British Telecom and IBM may hold related
-patents but have never chosen to require royalties for GIF applications,
-to the best of my knowledge. I am not a lawyer and cannot give
-legal advice regarding this issue. PNG remains a superior format especially
-if lossless truecolor images are needed.
-<p>
-When building from soruce, gd 2.0.33 <strong>requires</strong> that the 
-following libraries also be installed, in order to produce the related 
-image formats. The win32 binary release (bgd) already contains the
-appropriate libraries.
-You may skip libraries associated with formats you do not use:
-<p>
-libpng (see the <a href="http://www.libpng.org/pub/png/">libpng home page</a>), if you want PNG
-<p>
-zlib (see the <a href="http://www.info-zip.org/pub/infozip/zlib/">info-zip home page</a>), if you want PNG
-<p>
-jpeg-6b or later, if desired (see the <a href="http://www.ijg.org/">Independent JPEG Group home page</a>), if you want JPEG
-<p>
-If you want to use the TrueType font support, you must also
-install the <strong>FreeType 2.x library</strong>, including
-the header files. See the <a href="http://www.freetype.org/">Freetype 
-Home Page</a>, or <a href="http://freetype.sourceforge.net/">SourceForge</a>. 
-No, I cannot explain why that site is down on a particular day, and no, I 
-can't send you a copy.
-<p>
-If you want to use the Xpm color bitmap loading support, you must also
-have the X Window System and the Xpm library installed (Xpm is often
-included in modern X distributions). Most of the time you won't
-need Xpm.
-<p>
-Please read the documentation and install the required libraries.
-Do not send email asking why <code>png.h</code> is not found. 
-Do not send email asking why <code>libgd.so</code> is not found, either.
-See the <a href="#required">requirements section</a> for more
-information. Thank you!
-</blockquote>
-<H3>Table of Contents</H3>
-<UL>
-<LI><A HREF="#notice">Credits and license terms</A>
-<LI><A HREF="#whatsnew2.0.34">What's new in version "XYZ" of GD?</A>
-<LI><A HREF="#whatis">What is gd?</A>
-<LI><A HREF="#gdother">What if I want to use another programming language?</A>
-<LI><A HREF="#required">What else do I need to use gd?</A>
-<LI><A HREF="#getgd">How do I get gd?</A>
-<LI><A HREF="#buildgd">How do I build gd?</A>
-<LI><A HREF="#basics">gd basics: using gd in your program</A>
-<LI><A HREF="#webpng">webpng: a useful example</A>
-<LI><A HREF="#reference">Function and type reference by category</A>
-<LI><A HREF="#gdformat">About the additional .gd image file format</A>
-<LI><A HREF="#informing"><strong>Please</strong>
- tell us you're using gd!</A>
-<LI><A HREF="#support">How do I get support?</A>
-<LI><A HREF="#issues">How do I report issues, bugs or features request?</A>
-<LI><A HREF="#index">Alphabetical quick index</A>
-</UL>
-<P><A HREF="http://www.libgd.org/">
-Up to the <EM>LibGD Homepage</EM></A>
-<A NAME="notice"><H3>Credits and license terms</A></H3>
-<P>
-In order to resolve any possible confusion regarding the authorship
-of gd, the following copyright statement covers all of the authors
-who have required such a statement. <strong>If you are aware of any oversights
-in this copyright notice, please contact <A HREF="http://libgd.org/Contact">Pierre-A. Joye</A> who will be
-pleased to correct them.</strong>
-<pre>
-COPYRIGHT STATEMENT FOLLOWS THIS LINE
-</pre>
-<blockquote>
-
-Portions copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 by Cold Spring
-Harbor Laboratory. Funded under Grant P41-RR02188 by the National
-Institutes of Health.
-<P>
-Portions copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 by Boutell.Com, Inc.
-<p>
-Portions relating to GD2 format copyright 1999, 2000, 2001, 2002, 2003, 2004 Philip Warner.
-<p>
-Portions relating to PNG copyright 1999, 2000, 2001, 2002, 2003, 2004 Greg Roelofs.
-<p>
-Portions relating to gdttf.c copyright 1999, 2000, 2001, 2002, 2003, 2004 John Ellson (ellson@graphviz.org).
-<p>
-Portions relating to gdft.c copyright 2001, 2002, 2003, 2004 John Ellson (ellson@graphviz.org).
-<p>
-Portions copyright 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Pierre-Alain Joye (pierre@libgd.org).  
-
-<p>
-Portions relating to JPEG and to color quantization copyright 2000, 2001, 2002, 2003, 2004, Doug Becker and copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Thomas G. Lane.  This software is based 
-in part on the work of the Independent JPEG Group. See the file
-README-JPEG.TXT for more information.
-<p>
-Portions relating to GIF compression copyright 1989 by Jef
-Poskanzer and David Rowley, with modifications for thread safety
-by Thomas Boutell.
-<p>
-Portions relating to GIF decompression copyright 1990, 1991, 1993 
-by David Koblas, with modifications for thread safety by
-Thomas Boutell.
-<p>
-Portions relating to WBMP copyright 2000, 2001, 2002, 2003, 2004 Maurice Szmurlo and Johan Van 
-den Brande.
-<p>
-Portions relating to GIF animations copyright 2004 Jaakko Hyv&auml;tti (jaakko.hyvatti@iki.fi)
-<p>
-<strong>Permission has been granted to copy, distribute and modify gd in any
-context without fee, including a commercial application, provided that this notice
-is present in user-accessible supporting documentation.</strong>
-<p>
-This does not affect your ownership of the derived work itself, and the intent
-is to assure proper credit for the authors of gd, not to interfere
-with your productive use of gd. If you have questions, ask.
-"Derived works" includes all programs that utilize the library.
-Credit must be given in user-accessible documentation.
-<p>
-<strong>This software is provided "AS IS."</strong>
-The copyright holders disclaim all warranties, either express or implied,
-including but not limited to implied warranties of merchantability and
-fitness for a particular purpose, with respect to this code and accompanying
-documentation.
-<p>
-Although their code does not appear in the current release, the authors
-also wish to thank Hutchison Avenue Software Corporation for their
-prior contributions.
-</blockquote>
-<pre>
-END OF COPYRIGHT STATEMENT
-</pre>
-<A NAME="whatis"><H3>What is gd?</H3></A>
-<P>
-gd is a graphics library. It allows your code to quickly
-draw images complete with lines, arcs, text, multiple
-colors, cut and paste from other images, and flood fills, and
-write out the result as a PNG or JPEG file. This is particularly
-useful in World Wide Web applications, where PNG and JPEG are two
-of the formats accepted for inline images by most browsers.
-<P>
-gd is not a paint program.
-If you are looking for a paint program, you are looking in
-the wrong place. If you are not a programmer, you are looking
-in the wrong place, unless you are installing a required
-library in order to run an application.
-<P>
-gd does not provide for every possible desirable graphics
-operation. It is not necessary or desirable for gd to become
-a kitchen-sink graphics package, but version 2.0 does include
-most frequently requested features, including both truecolor and
-palette images, resampling (smooth resizing of truecolor images)
-and so forth.
-<P>
-<A NAME="gdother"><H3>What if I want to use another programming
-language?</h3></A>
-Not all of these tools are necessarily up to date and fully compatible
-with 2.0.33.
-<h4>PHP</h4>
-A variant of gd 2.x is included in PHP 4.3.0. It is also possible
-to patch PHP 4.2.3 for use with gd 2.0.33; see the
-<a href="http://www.libgd.org/">gd home page</a> for a link to
-that information. It would be a Good Idea to merge all of the things
-that are better in mainstream gd and all of the things that are
-better in PHP gd at some point in the near future. 
-<h4>Perl</h4>
-gd can also be used from Perl, courtesy of
-Lincoln Stein's
-<a href="http://stein.cshl.org/WWW/software/GD/">
-GD.pm</a> library, which uses gd as the basis for a set of
-Perl 5.x classes. Highly recommended.
-<h4>OCaml</h4>
-gd can be used from OCaml, thanks to
-<a href="http://gd4o.sourceforge.net/">Matt Gushee's GD4O project</a>.
-<h4>Tcl</h4>
-gd can be used from Tcl with John Ellson's
-<a href=http://www.graphviz.org/pub/>Gdtclft</a>
-dynamically loaded extension package.
-<h4>Pascal</h4>
-Pascal enthusiasts should look into the
-<a href="http://www.freepascal.org/">freepascal</a> project, a
-free Pascal compiler that includes gd support.
-<h4>REXX</h4>
-A 
-<a href="http://www.lightlink.com/hessling/RexxGd/index.html">gd interface 
-for the REXX language</a> is available.
-<h4>Any Language</h4>
-The "fly" interpreter performs gd operations specified in a text file.
-You can output the desired commands to a simple
-text file from whatever scripting language you prefer to use, then
-invoke the interpreter.
-<p>
-<ul>
-<li><a href="http://martin.gleeson.com/fly/">fly</a>, by Martin Gleeson
-</ul>
-<p>
-<A NAME="whatsnew2.0.34"><h3>What's new in version 2.0.34?</h3></a>
-<p>
-From 2.0.34 and later, please check the ISSUES and ChangeLog as well as 
-the releases announcements.
-<p>
-<A NAME="whatsnew2.0.33"><h3>What's new in version 2.0.33?</h3></a>
-<p>
-Version 2.0.33 restores compatibility with older releases
-of Freetype 2.x in addition to the latest release. Thanks to
-John Ellson and the graphviz project.
-<p>
-<A NAME="whatsnew2.0.32"><h3>What's new in version 2.0.32?</h3></a>
-<p>
-Version 2.0.32 restores correct detection of Unicode character sets
-for freetype fonts, which repairs a bug that prevented umlauts from
-displaying properly. Thanks to John Ellson and the graphviz project.
-Also, version 2.0.32 builds all test programs 
-smoothly in the absence of libpng. 
-<p>
-<A NAME="whatsnew2.0.31"><h3>What's new in version 2.0.31?</h3></a>
-<p>
-A minor type naming conflict prevented bgd.dll from compiling, and it
-was left out of the distribution as a result. This has been corrected.
-<p>
-<A NAME="whatsnew2.0.30"><h3>What's new in version 2.0.30?</h3></a>
-<p>
-2.0.29 did not compile correctly when freetype was not available.
-This has been corrected. Thanks to Alessandro Ranellucci.
-<p>
-<A NAME="whatsnew2.0.29"><h3>What's new in version 2.0.29?</h3></a>
-<p>
-<ul>
-<li>A 32-bit multiplication overflow vulnerability reported on
-the Bugtraq mailing list has been corrected, along with a number
-of similar issues. These bugs come into play only when attempting
-to deal with images with <i>extremely large</i> dimensions.
-The relevant functions now fail gracefully when such extreme
-parameters are specified. The code in question is also 
-correct for systems with larger bit depths. Thanks to Phil Knirsch,
-Alan Cox and infamous41md.
-Since exploits are theoretically possible, upgrading is recommended.
-<li>Support for the fontconfig library, when available. 
-When fontconfig is available and gdFTUseFontConfig(1) has been invoked
-or the gdFTEX_FONTCONFIG flag has been set for a particular call, fontconfig
-patterns can be used to fetch the best available font. 
-For instance, "arial:bold:italic" does the right thing (or as close as
-the available fonts permit). Also, standard 
-PostScript font names can be mapped to an appropriate font by 
-gdImageStringFTEx and relatives. 
-When fontconfig is available <tt>gdlib-config --features</tt> will list
-the GD_FONTCONFIG feature. For more information about fontconfig, see the
-<a href="http://freedesktop.org/software/fontconfig">fontconfig pages</a>.
-<p>
-The actual resolved font filename can be returned in the gdFTStringExtra
-structure as the fontpath element if the gdFTEX_RETURNFONTPATHNAME flag
-is set. Also, a 
-vector of character position advances can be retrieved if gdFTEX_XSHOW is set 
-in the flags element. .afm files (font metrics) are now used to adjust size 
-calculations
-when available. When fontconfig is not available, gd falls back to its
-usual behavior and requires a specific font file name. One can
-still fetch fonts by filename when gdFTUseFontConfig(1) is in effect, by
-setting the gdFTEX_FONTPATHNAME flag
-in the flag element of the gdFTStringExtra structure. Thanks to
-Dag Lem and John Ellson.
-<li>Additional freetype fixes: fixed width fonts are now the right
-size, horizontal advance calculations now better match the
-PostScript equivalent, and various compiler warning fixes. Also,
-a fix to the encoding table selection in the was made, addressing a problem
-with latin1 font encodings. Thanks to Dag Lem and John Ellson. 
-<li>Improved tolerance when reading JPEG files containing some garbage as well
-as valid image data.
-<li>Easier compilation on Windows: no errno.h in gd_gd2.c.
-<li>Support for creating optimized GIF animations has been added
- by Jaakko Hyv&auml;tti.  See
- <A HREF="#gdImageGifAnimAdd">gdImageGifAnimAdd</A>,
- <A HREF="#gdImageGifAnimAddCtx">gdImageGifAnimAddCtx</A>,
- <A HREF="#gdImageGifAnimAddPtr">gdImageGifAnimAddPtr</A>,
- <A HREF="#gdImageGifAnimBegin">gdImageGifAnimBegin</A>,
- <A HREF="#gdImageGifAnimBeginCtx">gdImageGifAnimBeginCtx</A>,
- <A HREF="#gdImageGifAnimBeginPtr">gdImageGifAnimBeginPtr</A>,
- <A HREF="#gdImageGifAnimEnd">gdImageGifAnimEnd</A>,
- <A HREF="#gdImageGifAnimEndCtx">gdImageGifAnimEndCtx</A>, and
- <A HREF="#gdImageGifAnimEndPtr">gdImageGifAnimEndPtr</A>.
-<li><A HREF="#gdImageOpenPolygon">gdImageOpenPolygon</A> has been
- added to allow consecutive line segments to be drawn without
- connecting the end points to form a closed polygon. Thanks to
-Jaakko Hyv&auml;tti.
-<li>Better alpha channel blending when the destination color
-contains an alpha channel. Also, quicker handling of the
-most common cases. Thanks to Frank Warmerdam.
-</ul>
-<P>
-<A NAME="whatsnew2.0.28"><H3>What's new in version 2.0.28?</H3></A>
-<P>
-<ul>
-<li>GIF support has been restored. See
-<a href="#gdImageGif">gdImageGif</a>, 
-<a href="#gdImageGifCtx">gdImageGifCtx</a>, 
-<a href="#gdImageGifPtr">gdImageGifPtr</a>, 
-<a href="#gdImageCreateFromGif">gdImageCreateFromGif</a>, 
-<a href="#gdImageCreateFromGifCtx">gdImageCreateFromGifCtx</a>, 
-and <a href="#gdImageCreateFromGifPtr">gdImageCreateFromGifPtr</a>.
-These functions are now thread-safe, similar to the PNG and JPEG
-manipulation functions.
-<li>The new <a href="#gdImageCreatePaletteFromTrueColor">gdImageCreatePaletteFromTrueColor</a> function is identical to <a href="#gdImageTrueColorToPalette">gdImageTrueColorToPalette</a>, except that it returns a new image rather than permanently modifying the original.
-</ul>
-<P>
-<A NAME="whatsnew2.0.27"><H3>What's new in version 2.0.27?</H3></A>
-<P>
-<ul>
-<li>In gd 2.0.26, there was potential for out of bounds fills, and therefore
-crashes, in the horizontalLine function used by gdImageFilledPolygon.
-Fixed by John Ellson.
-<li>The order of the points returned in the bounding rectangle by
-gdImageStringFT was incorrect in version 2.0.26. This has been
-corrected in version 2.0.27. Thanks to Riccardo Cohen for pointing
-this out, and to John Ellson for verifying and fixing it.
-</ul>
-<P>
-<A NAME="whatsnew2.0.26"><H3>What's new in version 2.0.26?</H3></A>
-<P>
-The following enhancements and fixes:
-<ul>
-<li>Drastically faster, less memory-intensive antialiased drawing, thanks to
-Pierre-Alain Joye. This code was imported from the PHP "fork"
-of gd. The API for antialiased drawing has not changed, however the
-implementation has been completely replaced.
-Antialiased line drawing does not support widths other
-than 1, however this did not work properly with the other
-implementation of antialiasing either. Support has been included
-for the "non-blending color" option introduced by the previous
-implementation of antialiased drawing.
-<li><code>gdlib-config</code>, which has been installed by 
-<code>make install</code> for some time now, has gained
-a <code>--features</code> option. This option produces a space-separated
-list of optional features with which the gd library was compiled.
-Typical usage looks like this:
-<pre>
-% gdlib-config --features
-GD_XPM GD_JPEG GD_FREETYPE GD_PNG GD_GIF
-</pre>
-Other <code>configure</code> scripts can conveniently define
-preprocessor symbols based on this list in order to conditionally
-compile code. For instance, if
-GD_PNG is not reported by --features, then gdImagePng is not
-included in the library.
-<p>
-Thanks to Lars Hecking and Lincoln Stein for their advice on
-implementing this feature. Any blame for the actual implementation
-is entirely due to me (TBB).
-<li>Fixes to the behavior of the bounding rectangle returned by
-gdImageStringFT and relatives when the string is rotated.
-See fontwheeltest.c. Thanks to John Ellson.
-<li>Previously, gdImageStringFT and friends accepted either 
-a full path to a font file, or the name of a font with no
-extension, in which case the GDFONTPATH environment variable
-and then the compiled-in DEFAULT_FONTPATH was searched. In addition,
-a font filename with an extension but no full path can now be
-automatically searched for in the same fashion. Thanks to John Ellson.
-
-<li>Fixes to freetype antialiased text against a transparent 
-background. See testtr.c. Thanks to John Ellson.
-
-<li>Support for named entities like &amp;amp; and hex-coded 
-entities such as &amp;#x6C34; in text 
-strings passed to gdImageStringFT and relatives, adding to the 
-previous support for decimal-coded entities like &amp;#197;. 
-These were extracted from entities.html (from the W3C) via
-the script entities.tcl, which is included for the curious and
-those with other entities they need support for.  Thanks to John Ellson.
-
-<li>Optimization: gdImageSetPixel no longer calls gdImageAlphaBlend 
-when either the source or the destination pixel is 100% transparent. 
-Thanks to John Ellson.
-
-<li>Optimization: gdImageLine is potentially faster now in the most 
-common cases.
-Thanks to John Ellson.
-<li>Documentation of the entities feature of gdImageStringFT.
-<li>autoconf/configure fixes. Thanks to many who pointed out an oversight
-in handling libpng flags.
-</ul>
-<P>
-<A NAME="whatsnew2.0.25"><H3>What's new in version 2.0.25?</H3></A>
-<P>
-Owing to an oversight while making changes to better accommodate the use
-of gd as a DLL, the <b>extern</b> qualifier was dropped from the 
-declarations of font pointers in 2.0.24. This has been corrected.
-Thanks to Richard ("OpenMacNews").
-<P>
-<A NAME="whatsnew2.0.24"><H3>What's new in version 2.0.24?</H3></A>
-<P>
-<b>Windows DLL now uses __stdcall calling convention.</b> Existing
-applications will require a recompile, using the new version of gd.h,
-in order to use this version of the DLL. However, Visual BASIC and other
-non-C programmers will now be able to use the DLL, which is an enormous
-benefit and justifies the one-time inconvenience to existing DLL users. 
-<p>
-The elaborate #ifdef test for older versions of Freetype without
-FT_ENCODING_MS_SYMBOL was needed in a second place also. Thanks to
-David R. Morrison.
-<p>
-An off-by-one error in gdImageToPalette caused transparency to be applied
-to the wrong pixels. Thanks to "Super Pikeman."
-<P>
-<A NAME="whatsnew2.0.23"><H3>What's new in version 2.0.23?</H3></A>
-<P>
-Output dpi specification option added to the
-<code>gdFTStringExtra</code> structure, thanks to
-Mark Shackelford. See <a href="#gdImageStringFTEx">gdImageStringFTEx</a>.
-<P>
-<A NAME="whatsnew2.0.22"><H3>What's new in version 2.0.22?</H3></A>
-<P>
-<ul>
-<li>Win32 DLL users: working with pointers exported by DLLs is 
-difficult and causes unexpected results. gd 2.0.22 exports new
-functions for retrieving the basic gd fonts:
-<a href="#gdFontGetTiny">gdFontGetTiny()</a>,
-<a href="#gdFontGetSmall">gdFontGetSmall()</a>,
-<a href="#gdFontGetMediumBold">gdFontGetMediumBold()</a>,
-<a href="#gdFontGetLarge">gdFontGetLarge()</a>, and
-<a href="#gdFontGetHuge">gdFontGetHuge()</a>. You may safely assign the
-return values from these functions to a local <code>gdFontPtr</code>.
-Direct use of <code>gdFontLarge</code>, etc. is strongly deprecated
-for users of <code>bgd.dll</code>; use these new functions instead.
-<li>Basic support for loading CMYK-colorspace JPEG images. They are
-of course converted to RGB which is a lossy process, however the
-results do look quite good and are certainly fine for thumbnails and
-web previews of DTP work.
-<li>"make" no longer fails on <code>circletexttest</code> if 
-PNG support is missing. 
-<li>Small performance improvements to gdImageCopyResampled; larger
-improvements are forthcoming.
-</ul>
-<P>
-<A NAME="whatsnew2.0.21"><H3>What's new in version 2.0.21?</H3></A>
-<P>
-<ul>
-<li>Version 2.0.21 adds a <code>gdImageCreateFrom*Ptr</code> family
-of functions which make it convenient to load an image in any
-GD-supported format directly from memory.
-<li>The new <code>gdNewDynamicCtxEx</code> function was added to
-support the easy implementation of the above functions and to
-correct a design problem which made life unpleasant for those passing
-in memory not originally allocated by gd to the 
-<code>gdNewDynamicCtx</code> function by provoding a way to specify
-that gd should never free or reallocate a particular block of memory.
-The <code>gdNewDynamicCtx</code> function and its relatives, although
-still exported for ABI compatibility, are now <b>deprecated</b> except 
-for internal use, in favor of <a href="#gdImageCreateFromPngPtr"><code>gdImageCreateFromPngPtr</code></a>
-and its relatives.
-<li>Version 2.0.21 includes a new patch from Ethan A. Merritt to
-correct a bug in the conditional compilation of support for
-symbol fonts in gdft.c. Symbol fonts should now work correctly.
-Thanks to Mr. Merritt.
-<li>Version 2.0.20 restores the <code>gdFreeFontCache</code> function,
-an undocumented function added in an earlier release which now simply
-calls <code>gdFontCacheShutdown</code> for backwards compatibility.
-This repairs build problems when compiling PHP against the latest gd.
-<li>Documentation improvements.
-</ul>
-<P>
-<A NAME="whatsnew2.0.20"><H3>What's new in version 2.0.20?</H3></A>
-<P>
-<ul>
-<li>Version 2.0.20 restores the <code>gdFreeFontCache</code> function,
-an undocumented function added in an earlier release which now simply
-calls <code>gdFontCacheShutdown</code> for backwards compatibility.
-This repairs build problems when compiling PHP against the latest gd.
-</ul>
-<P>
-<A NAME="whatsnew2.0.19"><H3>What's new in version 2.0.19?</H3></A>
-<P>
-<ul>
-<li>Version 2.0.19 restored <code>extern</code> declarations for the
-gd font pointers inadvertently removed in 2.0.18.
-</ul>
-<P>
-<A NAME="whatsnew2.0.18"><H3>What's new in version 2.0.18?</H3></A>
-<P>
-<ul>
-<li>A Win32 binary distribution of "bgd.dll," built with mingw32 and
-tested with win32 versions of the demo programs as console applications,
-is now available.
-<li>Semicolon rather than space used as the default separator of
-alternative font file paths in <a href="#gdImageStringFT">gdImageStringFT</a>,
-for better compatibility with Windows and other environments where
-spaces are common in paths.
-<li>The circletexttest demo no longer fails to compile when JPEG
-support happens to be absent.
-</ul>
-<P>
-<A NAME="whatsnew2.0.17"><H3>What's new in version 2.0.17?</H3></A>
-<P>
-Minor compilation and packaging problems with 2.0.16 were corrected.
-If 2.0.16 compiled without errors for you, then you don't need
-to upgrade to 2.0.17.
-<P>
-<A NAME="whatsnew2.0.16"><H3>What's new in version 2.0.16?</H3></A>
-<P>
-<ul>
-<li>Thread safety for freetype text output. Background: all gd functions
-were already thread safe, as long as only one thread manipulates each
-image -- except for gdImageStringFT and gdImageStringFTEx. This is because
-of a shared freetype font cache. Sharing the cache between images
-is worthwhile, so "configure" now detects pthreads and uses it to
-wrap freetype text output in a critical section if available. There is
-also critical section support under WIN32. Those who wish to be
-strictly thread-safe should call the new function
-<a href="#gdFontCacheSetup">gdFontCacheSetup</a> before allowing any
-thread to use freetype text calls. Otherwise this function is automatically
-invoked on the first use of freetype, with a very small but real chance
-of a race condition.
-<li><a href="#gdImageSquareToCircle">gdImageSquareToCircle</a> performs
-a "polar coordinate transform," returning a new image in which the
-X axis of the original has been remapped to theta (angle) and the
-Y axis of the original has been remapped to rho (distance from center).
-<li><a href="#gdImageStringFTCircle">gdImageStringFTCircle</a> wraps
-text in a circle around a specified center point. This function 
-takes advantage of <a href="#gdImageSquareToCircle">gdImageSquareToCircle</a>.
-The result is very smooth, although it takes some time to compute.
-Thanks to Steve Bassi for sponsoring this work.
-<li><a href="#gdImageSharpen">gdImageSharpen</a>, contributed by
-Paul Troughton. Thank you.
-<li>Christophe Thomas corrected gdft.c to include freetype header
-files in the way that is now mandatory in freetype 2.1.6 and above.
-<li>Gustavo Scotti fixed a memory leak in gdft.c.
-<li>Clipping rectangle respected in freetype text output. Thanks to Matt
-McNabb.
-<li>Paul den Dulk found a degenerate case that crashes
-gdImageToPalette. Fixed.
-<li>Optimization by Ilia Chipitsine to avoid wasting time with
-offscreen scanlines during polygon rasterization.
-<li>Optimized PNG saving by Phong Tran. Speeds up saves a 
-little bit. 
-<li>Bug in gdImageCopyResized fixed by Mao Morimoto.
-</ul>
-<P>
-<A NAME="whatsnew2.0.15"><H3>What's new in version 2.0.15?</H3></A>
-<P>
-<ul>
-<li>gd.c in 2.0.14 contained an instance of declaring variables
-after the first line of executable code appears. This is of course
-not allowed by ANSI C, although many compilers accept it. 
-My apologies. Thanks to Jeff Vendetti for reporting this quickly.
-</ul>
-<P>
-<A NAME="whatsnew2.0.14"><H3>What's new in version 2.0.14?</H3></A>
-<P>
-<ul>
-<li>2.0.13 was available for mere minutes due to a typo
-in the new bounds-checking code for antialiased line drawing. Fixed.
-<li>Not all platforms -- notably msys/mingw -- have an ssize_t type.
-We now call an int an int in gd_jpeg.c, with good results. 
-(Note: ssize_t is signed, unlike size_t, and it needs to be here.)
-</ul>
-<P>
-<A NAME="whatsnew2.0.13"><H3>What's new in version 2.0.13?</H3></A>
-<P>
-<ul>
-<li>The <code>main()</code> function of one of the test programs
-was accidentally included in the gd shared library, causing problems
-on some platforms. This has been corrected. Thanks to many people
-who pointed this out.
-<li>The antialiased drawing functions now have proper bounds
-checking. Thanks to Arne Jorgensen.
-<li>A void function returned a value in gd_png.c, causing warnings
-and, on some platforms, compilation errors but no reported runtime problems.
-Thanks to Kevin Smith, among others.
-<li>Autohinting was being forced ON for freetype text output. This is
-apparently meant only for testing freetype and does not look as good
-as the default behavior (FT_LOAD_DEFAULT). Thanks to Bob Ostermann.
-<li>penf.x is properly reset when newlines are encountered in freetype
-text output. Thanks to Christopher J. Grayce.
-</ul>
-<P>
-<A NAME="whatsnew2.0.12"><H3>What's new in version 2.0.12?</H3></A>
-<P>
-<ul>
-<li>Small but numerous code cleanups by Dr. Martin Zinser.
-<li><a href="#gdImageSetClip">gdImageSetClip</a> and
-<a href="#gdImageGetClip">gdImageGetClip</a> have been added. All
-drawing routines now stay within the specified clipping rectangle.
-Note that the <a href="#gdImageBoundsSafe">gdImageBoundsSafe</a> function
-now returns true only if the specified location is within the
-clipping rectangle. Of course, the default clipping area is the 
-entire image. The behavior of existing gd applications does not change.
-<li>Support for fast drawing of antialiased lines and polygons,
-by Bright Fulton and Frank Faubert. To learn more about this feature,
-read about the <a href="#gdImageSetAntiAliased">gdImageSetAntiAliased</a> 
-function, which is used to set the foreground color for antialiasing,
-as well as the <a href="#gdAntiAliased">gdAntiAliased</a> constant, which
-is passed to line- and polygon-drawing functions in place of a color.
-This code does not currently support an alpha channel component in the
-specified foreground color, or in the existing background image, 
-but <em>does</em> perform alpha blending against an opaque background.
-Also see the 
-<a href="#gdImageSetAntiAliasedDontBlend">gdImageSetAntiAliasedDontBlend</a> 
-function, which allows the specification of a special background
-color that should never be blended with the foreground.
-<li>Fixes to color mapping in <a href="#gdImageCopyMergeGray">gdImageCopyMergeGray</a>. Thanks to Philip Warner.
-<li><a href="#gdImageStringFTEx">gdImageStringFTEx</a> now supports
-explicit specification of the desired character mapping.
-This is useful when a font offers more than one of Unicode,
-Shift_JIS, and Big5. 
-<li>The PNG compression level can now be specified when writing PNG
-images. See the new <a href="#gdImagePngEx">gdImagePngEx</a>,
-<a href="#gdImagePngEx">gdImagePngEx</a>,
-<a href="#gdImagePngCtxEx">gdImagePngCtxEx</a>, and
-<a href="#gdImagePngPtrEx">gdImagePngPtrEx</a> functions.
-<li>The annotate utility builds without error in the absence of
-freetype, although of course it is not useful without freetype.
-<li>Thorben Kundinger fixed a bug relating to the use of palette-based
-images as brushes when drawing on truecolor images.
-<li>Michael Schwartz corrected a problem with his code for drawing
-thick lines.
-<li>Prior to 2.0.12, any alpha channel component in the
-<em>destination</em> image was ignored when drawing with
-alpha blending in effect (see 
-<a href="#gdImageAlphaBlending">gdImageAlphaBlending</a>). 2.0.12
-correctly preserves an appropriate proportion of the alpha component
-of the destination, just as it preserves an appropriate proportion
-of the red, green and blue components, depending on the opacity
-of the foreground. Thanks to Frank Warmerdam for pointing out the issue.
-<li>Memory leaks on failed attempts to load fonts
-in <a href="#gdImageStringFTEx">gdImageStringFTEx</a> were corrected.
-Thanks to Frank Faubert.
-<li>The impact of kerning is now correctly included in the calculation
-of the bounding box returned by the freetype text routines. This issue
-was pointed out by several individuals.
-<li>Color problems with the <code>gd2</code> file format routines
-were fixed by Steven Brown. These problems were due to the
-incorrect use of a signed integer.
-<li>Version 2.0.12 supports the <code>gd</code> file format correctly
-for truecolor images. Truecolor <code>gd</code> files created with
-earlier releases in the 2.0 series must be written again. The <code>gd</code>
-file format is used to quickly load an entire uncompressed image, typically 
-an existing background to which additional material will be added; it is not a 
-general purpose file format. More advanced capabilities are also available
-via the <code>gd2</code> format. Thanks to Andreas Pfaller for reporting 
-the problem. 
-<li>Signed vs. unsigned problem caused misbehavior when attempting to
-load a bad JPEG image. Thanks to Geert Jansen.
-<li>Existing truecolor PNG images with simple single-color transparency are 
-now loaded properly, thanks to Slaven Rezic.
-<li>The <a href="#gdImageTrueColorToPalette">gdImageTrueColorToPalette</a>
-function no longer attempts to preserve an alpha channel in the original.
-My attempt to do so resulted in significantly inferior output even if no
-alpha channel was present in the original. Thanks to Barend Gehrels for
-submitting a new adaptation of Tom Lane's jquant2.c which does a very
-high-quality job of palette conversion. Thanks also to Steven Brown, who
-submitted patches allowing a single 100% transparent color in the
-original truecolor image to be preserved. In practice, more complex 
-alpha channels in palettes are ill-supported and difficult to 
-allocate skillfully.
-</ul>
-<P>
-<A NAME="whatsnew2.0.11"><H3>What's new in version 2.0.11?</H3></A>
-<P>
-<ul>
-<li>Support for the "gd2" file format, which allows fast loading of all or
-only part of an existing image, has been properly debugged for use with
-truecolor images. (Palette images already worked properly, except for a
-bug when loading from a regular file with gdImageCreateFromGd2Part, which
-has also been fixed.) .gd2 files can be either compressed or uncompressed,
-and they allow useful tricks such as fast loading of a 500x500 pixel
-region of a 6000x3000 pixel image, without uncompressing <em>all</em> of the
-image. .gd2 is NOT a general purpose file format and should only be used
-where quick loading of a background image or subset of a larger image
-is required. For more information, see
-<a href="#gdImageGd2">gdImageGd2</a>, 
-<a href="#gdImageCreateFromGd2">gdImageCreateFromGd2</a>,
-and 
-<a href="#gdImageCreateFromGd2Part">gdImageCreateFromGd2Part</a>.
-<li>The gd2topng utility has been extended to support extraction of
-only part of an image from a .gd2 file. This is both a demonstration and 
-a practical tool.
-<li>Additional <code>configure</code> improvements by Lars Hecking.
-</ul>
-<P>
-<A NAME="whatsnew2.0.10"><H3>What's new in version 2.0.10?</H3></A>
-<P>
-<ul>
-<li>gdImageLine now clips to the edges of the image before drawing
-lines, which greatly improves performance when many lines extend
-outside or are entirely outside the actual image. Thanks to 
-Nick Atty for this code.
-<li>gdImageBoundsSafe is replaced with a macro when called internally;
-this improves the performance of gdImageSetPixel and gdImageGetPixel
-a little bit, and therefore everything else as well. Thanks to
-Nicky Atty for the idea.
-<li>Transparent indexes are handled properly with non-truecolor
-source images in gdImageCopy. Thanks to Frank Warmerdam.
-<li>floor() replaced with a cast to long in gdImageCopyResampled,
-for a roughly 35% performance boost. Thanks to John Buckman.
-<li>gdft.c builds correctly on WIN32 without patches.
-<li>Much faster gdImageCreateFromJpeg routines, thanks to Christian
-Aberger for more efficient pointer arithmetic.
-<li>gdtestft correctly builds without PNG tests if PNG support is not present.
-Thanks to Gabriele Verzeletti.
-</ul>
-<P>
-<A NAME="whatsnew2.0.9"><H3>What's new in version 2.0.9?</H3></A>
-<P>
-<ul>
-<li>Version 2.0.9 contains a fix to gdImageCopyResized which allows
-correct results when copying a palette-based image with a single
-transparent index into a truecolor image. Thanks to Thorben
-Kundinger.
-<li>More <code>configure</code> fixes from Lars Hecking. Thanks, Lars. 
-</ul>
-<P>
-<A NAME="whatsnew2.0.8"><H3>What's new in version 2.0.8?</H3></A>
-<P>
-<ul>
-<li>Version 2.0.8 contains additional fixes to the 'configure' script,
-allowing a clean out-of-the-box build on more systems.
-<li>Version 2.0.8 adds the new 
-<a href="#gdImageCopyRotated">gdImageCopyRotated</a> function, which
-can rotate any rectangular image region by an arbitrary number of degrees.
-</ul>
-<P>
-<A NAME="whatsnew2.0.7"><H3>What's new in version 2.0.7?</H3></A>
-<P>
-Version 2.0.7 corrects a problem which caused 'configure' to complain
-that the directory NONE was not found, in various places, causing
-the configuration process to stop. There are no code changes.
-<P>
-<A NAME="whatsnew2.0.6"><H3>What's new in version 2.0.6?</H3></A>
-<P>
-<ul>
-<li>
-Fixed a compilation problem with gdft.c. A declaration appeared
-after executable code, and gcc let it slide by, so it made it
-out the door. My apologies!
-<li>As penance, I have seen to it that the entire library
-now compiles cleanly with the <code>-Wall</code>, <code>-ansi</code>
-and <code>-pedantic</code> options enabled.
-</ul>
-<p>
-<A NAME="whatsnew2.0.5"><H3>What's new in version 2.0.5?</H3></A>
-<ul>
-<li>libgd 2.0.5 INSTALLS IN /usr/local/lib BY DEFAULT. IF YOU WANT
-IT TO INSTALL IN /usr/lib, YOU MUST SPECIFY THIS at
-<code>configure</code> time using this syntax:
-<p>
-<code>./configure --prefix=/usr</code> 
-<li>gd now uses GNU autoconf. This means that the provided
-<code>configure</code> script should be compatible with all standard
-GNU configure options and will figure out the correct settings for a
-much wider range of operating systems. Many, many thanks to
-Lars Hecking for taking care of this.
-<li>The <a href="#gdImageStringFTEx">gdImageStringFTEx</a> function
-is now included, thanks to Wez Furlong. My apologies to Wez for the
-unreasonable amount of time this patch has sat in my queue.
-<li>Additional fixes from Wez Furlong.
-<li>Arithmetic cleanup by Doug Claar.
-<li>Corrections to loading and saving of alpha channel
-information in PNG files, by Andrew Hull.
-<li>gdImageTrueColorToPalette does not contain
-unneeded test code.
-<li>gdImageCopyResized works properly again when copying
-from a non-truecolor source.
-</ul>
-<P>
-<A NAME="whatsnew2.0.4"><H3>What's new in version 2.0.4?</H3></A>
-The following contributions from John Ellson:
-<ul>
-<li>Various test programs now compile in the absence
-of PNG support
-<li>gdIOCtx correctly calls gdFree rather than free
-<li>Various cleanups to pass -Wall without warnings
-<li>Support for Adobe-style Type 1 fonts (.pfa and .pfb files)
-via freetype
-<li>gdImageColorResolve and gdImageColorResolveAlpha will not
-attempt to resolve a color request to the transparent color index
-(for palette-based images)
-<li>Improved font search path support
-<li>Antialiased freetype text on palette images works properly
-when more than one image is created in a single program lifetime
-with different color indexes
-<li>Better threshold for two-color "mono" images 
-<li>Memory leak fixes
-<li>Text rotation fix
-<li>More extensive default font path
-<li>fontwheeltest and fontsizetest test programs for freetype
-</ul>
-And the following additional fixes:
-<ul>
-<li><code>configure</code> now correctly detects and provides
-support for the Xpm library and its dependencies (Len Makin)
-</ul>
-<A NAME="whatsnew2.0.3"><H3>What's new in version 2.0.3?</H3></A>
-<ul>
-<li>The <code>configure</code> script has been extensively modified
-to work properly in tests with both Solaris and Linux. Other platforms
-should also work based on feedback received and integrated to date.
-<li>The <code>--prefix</code> option to <code>configure</code>
-works properly.
-<li>The <code>annotate</code> utility has been added. This is a
-very handy tool for adding freetype text to existing JPEGs. After
-<code>make install</code>, type <code>annotate -h</code> for more 
-information. Thanks to Joel Dubiner.
-</ul>
-<P>
-<A NAME="whatsnew2.0.2"><H3>What's new in version 2.0.2?</H3></A>
-<ul>
-<li>A "configure" script has been added. After wrestling with GNU
-autoconf for a while, I got tired of trying to make it detect libraries
-but accept their absence gracefully, and so on. Instead, I wrote a short
-Perl script which does the job and builds a reasonable Makefile. Those
-who find it doesn't detect their system's needs properly are welcome
-to contribute patches or the necessary commands.
-<li>Antialiased freetype text output now works properly in both
-truecolor and non-truecolor contexts! Hurrah! On a truecolor image
-it is possible, for instance, to draw antialiased text on an arbitrarily
-complex background with 50% alpha blending (transparency), and get the
-expected pretty results. Thanks to Joel Dubiner for his support of this work.
-<li><strong>By default, alpha blending is now done within the library.</strong>
-Also, by default, alpha channel is not saved with PNG images. This means
-that programmers who try loading a JPEG, scribbling some pretty antialiased
-text on it, and saving the JPEG again will now get the results they
-expected. It also means that, by default, users will not run afoul of
-the fact that many web browsers don't properly support full PNG alpha
-channel. 
-<li>Various submitted bug fixes have been incorporated.
-<li>Various other submitted changes have not been incorporated. Sorry.
-The interval between 2.0.1 and 2.0.2 was simply too long, and changes
-accumulated which were not mutually compatible. I'll do better in
-the future, especially with bug fixes.
-</ul> 
-<P><A NAME="whatsnew2.0.1"><H3>What's new in version 2.0.1?</H3></A>
-<ul>
-<li>Workaround for a bug in gcc, apparently found in gcc 2.7.2 and up.
-I reproduced and fixed it while using gcc 2.9.5.2. The bug occurred only
-when the -g option was in use. This problem caused gcc to spew
-internal error messages unrelated to the correctness of the code
-in gd_gd2.c. Howard Jones was first to report it.
-<li><a href="#gdImageFilledEllipse">gdImageFilledEllipse</a> documented
-and altered; no longer requires a superfluous style argument. Thanks to
-Francis James Franklin.
-<li>The Makefile now offers the correct syntax for
-optionally creating a static library. Thanks to Jean-Lous Regez,
-among others.
-<li>A nested comment, an attempt to return the value of a void function,
-and a potentially significant error in gdImageCopyResampled were fixed
-thanks to Joseph Shirley.
-<li>A bug preventing proper truecolor text rendering was fixed,
-thanks to Jason Gallagher.
-<li><a href="#gdImageStringFT">gdImageStringFT</a> (FreeType) should 
-now work better against a transparent or semitransparent background,
-and should act in a manner consistent with the most recent
-<a href="#gdImageAlphaBlending">gdImageAlphaBlending</a> setting.
-Antialiasing is now done via the alpha channel mechanism if the
-image is a truecolor image. 
-<li>Bugs in the output of gdImageArc and gdImageFilledArc were reported
-by Bruce Verderaime. A simple and correct but inefficient implementation
-has been substituted until fixes are contributed for the faster code,
-which is in gd_arc_f_buggy.c along with the test program that reproduces
-the bug(s).
-<li><a href="#gdImageFilledArc">gdImageFilledArc</a> now offers additional
-style options, which can be combined to produce various effects.  
-<li>Masahito Yamaga (ma@yama-ga.com) sent a patch to improve
-support for Japanese output via <a href="#gdImageStringFT">gdImageStringFT</a>. 
-He also added a new <code>readme.jpn</code> file.
-<li>Zillions of documentation fixes.
-</ul>
-<P><A NAME="whatsnew2.0"><H3>What's new in version 2.0?</H3></A>
-<ul>
-<li><strong>Support for truecolor images!</strong> Version 2.0 can
-load truecolor PNGs with no loss of color information, and almost
-no loss of alpha channel information. Version 2.0 can also load
-truecolor JPEGs with as little loss as possible; however, bear in
-mind that JPEG is a lossy format, so repeated load/save cycles
-always reduce image quality. This is not a bug. To create
-a truecolor image from scratch, call the new
-<a href="#gdImageCreateTrueColor">gdImageCreateTrueColor</a>
-function. The <a href="#gdImageCreate">gdImageCreate</a> function
-is still available to create palette images, and may also be
-referred to as <a href="#gdImageCreatePalette">gdImageCreatePalette</a>.
-<li><strong>Support for alpha channels!</strong> In addition to
-24 bits of color information for each pixel (eight bits of
-red, green, and blue respectively), version 2.0 supports
-7 bits of "alpha channel" information. This is used to determine
-exactly how transparent the pixel should be. There is also support
-for a full 7 bits of transparency for each individual palette index
-in a palette-based image. Please note that, as of this writing,
-only Macintosh Internet Explorer 5.x and Mozilla/Netscape 6.x
-display partial transparency properly.
-<li>The new <a href="#gdImageAlphaBlending">gdImageAlphaBlending</a>
-function allows for two different modes of drawing. In blending mode,
-the alpha channel component of the color supplied to all drawing
-functions, such as <a href="#gdImageSetPixel">gdImageSetPixel</a>,
-determines how much of the underlying color should be allowed to
-shine through. The resulting image is not transparent. In non-blending 
-mode, drawing color is copied literally with the alpha channel 
-information, resulting in a transparent image. Blending mode is
-not available when drawing on palette images. 
-<li>The <a href="#gdImageCopyResampled">gdImageCopyResampled</a>
-function provides "smooth" copying from a large image to a smaller
-one, using a weighted average of the pixels of the source area rather 
-than selecting one representative pixel. This function is identical
-to <a href="#gdImageCopyResized">gdImageCopyResized</a> when the
-destination image is a palette image.
-<li>The <a href="#gdImageTrueColorToPalette">gdImageTrueColorToPalette</a>
-function converts a truecolor image to a palette image. The code for
-this function was originally drawn from the Independent JPEG Group library
-code, which is excellent. The code has been modified to preserve as much
-alpha channel information as possible in the resulting palette, in addition 
-to preserving colors as well as possible. This does not work as well as
-might be hoped. It is usually best to simply produce a truecolor
-output image instead, which guarantees the highest output quality.
-<li>A very high degree of backwards compatibility with existing
-gd 1.x code has been maintained, at both the source code and binary
-level. <strong>Code which directly accesses the <code>pixels</code> array
-will fail only if it encounters an existing truecolor image</strong>, which may
-happen if the code attempts to open and modify an existing JPEG or 
-truecolor PNG. Such code should be modified to check the
-<code>trueColor</code> flag of the <code>gdImage</code> structure, and
-refer to the <code>tpixels</code> array instead when it is set.
-<li>gd is now compiled and installed as a shared library. However,
-gd still does not use autoconf, because I (TBB) have very limited
-patience with autoconf. These days, most Unix systems provide a fairly
-POSIX-standard environment, and the provided Makefile is likely to work well
-if users read it and follow the instructions at the top.
-<li>Support for line thickness was added by Michael Schwartz. My apologies
-to him for sitting on his patches for so long. See the new
-<a href="#gdImageSetThickness">gdImageSetThickness</a> function, which
-affects all standard gd functions that draw lines and curves. In addition,
-Michael added a convenient <a href="#gdImageEllipse">gdImageEllipse</a>
-function. 
-<li>The new <a href="#gdImageFilledArc">gdImageFilledArc</a> function
-provides a straightforward way to draw filled arcs. Also,
-<a href="#gdImageFilledEllipse">gdImageFilledEllipse</a> is a 
-convenient way to fill an ellipse without specifying starting
-and ending angles. Thanks go out to F J Franklin.
-<li>To put an end to the confusion, TrueType 1.x support has been
-removed in favor of TrueType 2.x support. The old
-gdImageStringTTF function simply invokes gdImageStringFT.
-<li>The specialized .gd and .gd2 file formats have been upgraded to support
-truecolor. New images written by the versions of these functions
-found in 2.0 will be rejected, with varying degrees of grace, by
-older versions of gd. THIS AFFECTS THE .GD and .GD2 FORMATS ONLY. IF YOU
-ARE CONFUSED BY THIS PARAGRAPH, IT PROBABLY DOESN'T APPLY TO ANYTHING
-YOU WILL EVER ENCOUNTER. Since these file formats are absolutely,
-positively *not* designed for distributing images, just for
-preprocessing them, this should not be a big problem. gd 2.0 should
-read old .gd and .gd2 files correctly.
-</ul>
-<P><A NAME="whatsnew1.8.4"><H3>What's new in version 1.8.4?</H3></A>
-<ul>
-<li>Add support for FreeType2  (John Ellson  ellson@graphviz.org)
-<li>Add support for finding in fonts in a builtin DEFAULT_FONTPATH,
-or in a path from the GDFONTPATH environment variable.
-<li>remove some unused symbols to reduce compiler warnings
-<li>bugfix in size comparisons in gdImageCompare
-<li>REXX now mentioned
-<li>All memory allocation functions are now wrapped within the
-library; gdFree is exported and recommended for freeing memory
-returned by the gdImage(Something)Ptr family of functions.
-</ul>
-<P><A NAME="whatsnew1.8.3"><H3>What's new in version 1.8.3?</H3></A>
-<ul>
-<li>WBMP output memory leak fixed
-<li><code>#include &lt;gd.h&gt;</code> corrected to <code>#include "gd.h"</code> in gd_wbmp.c 
-<li>Documented the fact that the source and output images shouldn't
-match in the WBMP test except for black and white source images
-</ul>
-<P>
-<A NAME="whatsnew1.8.2"><H3>What's new in version 1.8.2?</H3></A>
-<ul>
-<li>WBMP support debugged and improved by Johann Van den Brande
-<li>WBMP tests added to gdtest.c by Thomas Boutell
-<li>Use of platform-dependent 'install' command removed by Thomas Boutell
-<li>Comments added to Makefile warning users to juggle the order of the
-libraries if the linker complains; is there any portable way to do this
-automatically, short of using autoconf?
-<li>Documentation of <a href="#gdImageCreateFromXpm">gdImageCreateFromXpm</a>
-corrected
-<li>Updated links to fast-moving, always dodging libpng and zlib web sites
-</ul>
-<P><A NAME="whatsnew1.8.1"><H3>What's new in version 1.8.1?</H3></A>
-<ul>
-<li>Optional components no longer built by default (following the
-documentation)
-<li>JPEG code no longer requires inappropriate header files
-<li>Win32 patches from Joe Gregorio
-<li>16-bit font support for bdftogd, from Honza Pazdziora
-</ul>
-<P><A NAME="whatsnew1.8"><H3>What's new in version 1.8?</H3></A>
-<ul>
-<li>Support for JPEG output, courtesy of Doug Becker
-<li>A link to Michael Bradbery's Pascal wrapper
-<li>Support for WBMP output, courtesy of Maurice Szmurlo
-<li>gdImageColorClosestHWB function based on hue, whiteness, blackness,
-superior to the regular gdImageColorClosest function, courtesy 
-of Philip Warner
-<li>License clarification: yes, you can modify gd
-</ul>
-<h4>Additional JPEG Information</h4>
-Support for reading and writing JPEG-format images is courtesy
-of Doug Becker and the Independent JPEG Group / Thomas G. Lane.  You
-can get the latest version of the IJG JPEG software from <A
-HREF="ftp://ftp.uu.net/graphics/jpeg/">ftp://ftp.uu.net/graphics/jpeg/</A>
-(e.g., the <A
-HREF="ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz">jpegsrc.v6b.tar.gz</A>
-file).  You <strong>must</strong> use
-version 6b or later of the IJG JPEG software.  You might also consult
-the <A HREF="http://www.faqs.org/faqs/jpeg-faq/">JPEG FAQ</A> at
-<A HREF="http://www.faqs.org/faqs/jpeg-faq/">http://www.faqs.org/faqs/jpeg-faq/</A>.
-<P><A NAME="whatsnew1.7.3"><H3>What's new in version 1.7.3?</H3></A>
-Another attempt at Makefile fixes to permit
-linking with all libraries required on platforms with order-
-dependent linkers. Perhaps it will work this time.
-<P><A NAME="whatsnew1.7.2"><H3>What's new in version 1.7.2?</H3></A>
-An uninitialized-pointer bug in <code>gdtestttf.c</code> was corrected.
-This bug caused crashes at the end of each call to gdImageStringTTF on
-some platforms. Thanks to Wolfgang Haefelinger.
-<p>
-Documentation fixes. Thanks to Dohn Arms.
-<p>
-Makefile fixes to permit
-linking with all libraries required on platforms with order-
-dependent linkers.
-<P><A NAME="whatsnew1.7.1"><H3>What's new in version 1.7.1?</H3></A>
-A minor buglet in the Makefile was corrected, as well as an inaccurate
-error message in <code>gdtestttf.c</code>. Thanks to Masahito Yamaga.
-<P><A NAME="whatsnew1.7"><H3>What's new in version 1.7?</H3></A>
-Version 1.7 contains the following changes:
-<ul>
-<li>Japanese language support for the TrueType functions.
-Thanks to Masahito Yamaga.
-<li><code>autoconf</code> and <code>configure</code> have been removed, in favor of a 
-carefully designed Makefile which produces and properly installs
-the library and the binaries. System-dependent variables are
-at the top of the Makefile for easy modification. I'm sorry, 
-folks, but autoconf generated <strong>many, many confused email 
-messages</strong> from people who didn't have things where autoconf 
-expected to find them. I am not an autoconf/automake wizard, and 
-gd is a simple, very compact library which does not need to 
-be a shared library. I <strong>did</strong> make many improvements
-over the old gd 1.3 Makefile, which were directly inspired by the 
-autoconf version found in the 1.6 series (thanks to John Ellson).
-<li>Completely ANSI C compliant, according to the <code>-pedantic-errors</code>
-flag of gcc. Several pieces of not-quite-ANSI-C code were causing problems
-for those with non-gcc compilers.
-<li><code>gdttf.c</code> patched to allow the use of Windows symbol
-fonts, when present (thanks to Joseph Peppin). 
-<li><code>extern "C"</code> wrappers added to <code>gd.h</code> and the
-font header files for the convenience of C++ programmers. 
-<code>bdftogd</code> was also modified to automatically insert these
-wrappers into future font header files. Thanks to John Lindal.
-<li>Compiles correctly on platforms that don't define <code>SEEK_SET</code>.
-Thanks to Robert Bonomi.
-<li>Loads Xpm images via the 
-<a href="#gdImageCreateFromXpm"><code>gdImageCreateFromXpm</code></a>
-function, if the Xpm library is available. Thanks to Caolan McNamara.
-</ul>
-<P><A NAME="whatsnew1.6.3"><H3>What's new in version 1.6.3?</H3></A>
-Version 1.6.3 corrects a memory leak in gd_png.c. This leak caused
-a significant amount of memory to be allocated and not freed when
-writing a PNG image. 
-<P><A NAME="whatsnew1.6.2"><H3>What's new in version 1.6.2?</H3></A>
-Version 1.6.2 from John Ellson <ellson@graphviz.org> adds two new functions:
-<ul>
-<li>gdImageStringTTF - scalable, rotatable, anti-aliased, TrueType strings using
-the FreeType library, but only if libttf is found by configure.
-<strong>We do not provide TrueType fonts. Obtaining them
-is entirely up to you.</strong>
-<li>gdImageColorResolve - an efficient alternative for the
-common code fragment:
-<pre>
-
-      if ((color=gdImageColorExact(im,R,G,B)) < 0)
-          if ((color=gdImageColorAllocate(im,R,G,B)) < 0)
-              color=gdImageColorClosest(im,R,G,B);
-</pre>
-</ul>
-<p>
-Also in this release the build process has been converted to
-GNU autoconf/automake/libtool conventions so that both (or either)
-static and shared libraries can be built.
-<P><A NAME="whatsnew1.6.1"><H3>What's new in version 1.6.1?</H3></A>
-Version 1.6.1 incorporates superior PNG reading and writing code
-from Greg Roelofs, with minor modifications by Tom Boutell. 
-Specifically, I altered his code to read non-palette images
-(converting them to palette images badly, by dithering them),
-and to tolerate palette images with types of transparency that
-gd doesn't actually support (it just ignores the advanced
-transparency features). Any bugs in this area are therefore my 
-fault, not Greg's.
-<p>
-Unlike gd 1.6, users should have no trouble linking with
-gd 1.6.1 if they follow the instructions and install all of
-the pieces. However, <strong>If you get undefined symbol errors,
-be sure to check for older versions of libpng in your
-library directories!</strong>
-<P><A NAME="whatsnew1.6"><H3>What's new in version 1.6?</H3></A>
-Version 1.6 features the following changes:
-<p>
-<strong>Support for 8-bit palette PNG images has been added.
-Support for GIF has been removed.</strong> This step was taken
-to completely avoid the legal controversy regarding the LZW
-compression algorithm used in GIF. Unisys holds a patent which
-is relevant to LZW compression. PNG is a superior image format
-in any case. Now that PNG is supported by both Microsoft
-Internet Explorer and Netscape (in their recent releases),
-we highly recommend that GD users upgrade in order to get 
-well-compressed images in a format which is legally unemcumbered.
-
-<P><A NAME="whatsnew1.5"><H3>What's new in version 1.5?</H3></A>
-
-Version 1.5 featured the following changes:
-
-<dl>
-<dt><b>New GD2 format</b>
-<dd>      An improvement over the GD format, the GD2 format uses the zlib
-          compression library to compress the image in chunks. This results
-          in file sizes comparable to GIFs, with the ability to access parts
-          of large images without having to read the entire image into memory.
-<p>
-  This format also supports version numbers and rudimentary validity
-  checks, so it should be more 'supportable' than the previous GD format.
-<p>
-<dt><b>Re-arranged source files</b>
-<dd>      gd.c has been broken into constituant parts: io, gif, gd, gd2 and
-          graphics functions are now in separate files.
-<p>
-<dt><b>Extended I/O capabilities.</b>
-<dd>      The source/sink feature has been extended to support GD2 file formats (which
-          require seek/tell functions; seek must return 1 for success, 0 for failure), and to allow more general non-file I/O.
-<p>
-<dt><b>Better support for Lincoln Stein's Perl Module</b>
-<dd>      The new gdImage*Ptr function returns the chosen format stored in a block of memory.
-          This can be directly used by the GD perl module.
-<p>
-<dt><b>Added functions</b>
-<dd>gdImageCreateFromGd2Part - allows retrieval of part of an image (good for huge images, like maps),
-<br>gdImagePaletteCopy - Copies a palette from one image to another, doing it's best to match the colors in the target image to the colors in the source palette.
-<br>gdImageGd2, gdImageCreateFromGd2 - Support for new format
-<br>gdImageCopyMerge - Merges two images (useful to highlight part of an image)
-<br>gdImageCopyMergeGray - Similar to gdImageCopyMerge, but tries to preserve source image hue.
-<br>gdImagePngPtr, gdImageJpegPtr, gdImageWBMPPtr, gdImageGdPtr, gdImageGd2Ptr - return memory blocks for each type of image.
-<br>gdImageCreateFromPngCtx, gdImageCreateFromGdCtx, gdImageCreateFromGd2Ctx, gdImageCreateFromGd2PartCtx - Support for new I/O context.
-
-</dl>
-
-<b>NOTE:</b> In fairness to Thomas Boutell, any bug/problems with any of the above features should
-probably be reported to <a href=mailto:pjw@rhyme.com.au>Philip Warner</a>.
-
-<P><A NAME="whatsnew1.4"><H3>What's new in version 1.4?</H3></A>
-
-Version 1.4 features the following changes:
-<dl>
-<dt>Fixed polygon fill routine (again)
-<dd>Thanks to Kirsten Schulz, version 1.4 is able to fill
-numerous types of polygons that caused problems with
-previous releases, including version 1.3.
-<dt>Support for alternate data sources
-<dd>Programmers who wish to load a GIF from something other
-than a stdio FILE * stream can use the new
-<a href="#gdImageCreateFromPngSource">gdImageCreateFromPngSource</a> function.
-<dt>Support for alternate data destinations
-<dd>Programmers who wish to write a GIF to something other
-than a stdio FILE * stream can use the new
-<a href="#gdImagePngToSink">gdImagePngToSink</a> function.
-<dt>More tolerant when reading GIFs
-<dd>
-Version 1.4 does not crash when reading certain animated GIFs,
-although it still only reads the first frame. Version 1.4 also has
-overflow testing code to prevent crashes when reading
-damaged GIFs.
-</dl>
-<P><A NAME="whatsnew1.3"><H3>What's new in version 1.3?</H3></A>
-Version 1.3 features the following changes:
-<dl>
-<dt>Non-LZW-based GIF compression code
-<dd>
-Version 1.3 contained GIF compression code that uses simple Run Length
-Encoding instead of LZW compression, while still retaining compatibility
-with normal LZW-based GIF decoders (your browser will still like your GIFs).
-<strong>LZW compression is patented by Unisys. We are currently reevaluating
-the approach taken by gd 1.3. The current release of gd does not support
-this approach. We recommend that you use the current release, and generate
-PNG images.</strong> Thanks to 
-Hutchison Avenue Software Corporation for contributing
-the RLE GIF code.
-<dt>8-bit fonts, and 8-bit font support
-<dd>This improves support for European languages. Thanks are due
-to Honza Pazdziora <adelton@informatics.muni.cz> and also to
-Jan Pazdziora <adelton@fi.muni.cz>. Also see the provided bdftogd
-Perl script if you wish to convert fixed-width X11 fonts
-to gd fonts.
-<dt>16-bit font support (no fonts provided)
-<dd>Although no such fonts are provided in the distribution,
-fonts containing more than 256 characters should work if the
-gdImageString16 and gdImageStringUp16 routines are used.
-<dt>Improvements to the "webpng" example/utility
-<dd>The "webpng" utility is now a slightly more useful application. Thanks to
-Brian Dowling for this code.
-<dt>Corrections to the color resolution field of GIF output
-<dd>Thanks to Bruno Aureli.
-<dt>Fixed polygon fills
-<dd>A one-line patch for the infamous polygon fill bug, courtesy
-of Jim Mason. I believe this fix is sufficient. However, if you
-find a situation where polygon fills still fail to behave properly,
-please send code that demonstrates the problem, <em>and</em> a fix if
-you have one. Verifying the fix is important.
-<dt>Row-major, not column-major
-<dd>Internally, gd now represents the array of pixels as
-an array of rows of pixels, rather than an array of columns
-of pixels. This improves the performance of compression and
-decompression routines slightly, because horizontally adjacent
-pixels are now next to each other in memory. <strong>This should
-not affect properly written gd applications, but applications that
-directly manipulate the <code>pixels</code> array will require
-changes.</strong>
-</dl>
-<A NAME="required"><H3>What else do I need to use gd?</H3></A>
-<P>
-To use gd, you will need an ANSI C compiler. <strong>All popular
-Windows 95 and NT C compilers are ANSI C compliant.</strong> Any
-full-ANSI-standard C compiler should be adequate. <strong>The cc
-compiler released with SunOS 4.1.3 is not an ANSI C compiler.
-Most Unix users who do not already have gcc should get it.
-gcc is free, ANSI compliant and a de facto industry standard.
-Ask your ISP why it is missing.</strong>
-<P>
-As of version 1.6, you also need the zlib compression library,
-and the libpng library. As of version 1.6.2, you can draw text
-using antialiased TrueType fonts if you also have the libttf
-library installed, but this is not mandatory.
-zlib is available for a variety of platforms from
-<a href="http://www.freesoftware.com/pub/infozip/index.html">the zlib web site</a>.
-libpng is available for a variety of platforms from
-<a href="http://www.cdrom.com/pub/png/">the PNG web site</a>.
-
-<P>
-You will also want a PNG viewer, if you do not already have
-one for your system, since you will need a good way to check the
-results of your work. Netscape 4.04 and higher, and Microsoft
-Internet Explorer 4.0 or higher, both support PNG.
-<strong>Not every PNG-compatible viewer supports alpha channel
-transparency,</strong> which is why gd 2.0.2 and above do alpha
-blending in the library by default; it is possible to turn on the
-saving of alpha channel information to the file instead.
-<P>
-<A NAME="getgd"><H3>How do I get gd?</H3></A>
-<h4>Binaries (DLL for Windows programmers):</h4>
-<ul>
-<li><a href="http://www.libgd.org/Downloads">.ZIP File of DLL, Headers, Et Cetera</a>
-<p>
-</ul>
-<h4>Source Code:</h4>
-<ul>
-<li><a href="http://www.libgd.org/Downloads">Gzipped Tar File (Unix)</a>
-<li><a href="http://www.boutell.com/gd/http/gd-2.0.33.tar.gz">.ZIP File of SOURCE CODE (Windows)</a>
-</ul>
-<P>
-<A NAME="buildgd"><H3>How do I build gd?</H3></A>
-<blockquote>
-Win32 DLL users: if you are using MSVC, use the provided batch file
-<code>makemsvcimport.bat</code> to make a bgd.lib import library
-corresponding to the provided bgd.dll. Copy bgd.dll to your
-application directory, or to your Windows sytem directory. In the
-settings of your MSVC project, you <b>MUST</b> choose the
-"multithreaded DLL" library option under "code generation." 
-mingw32 and cygwin users can simply link with the provided libbgd.a 
-stub library in order to use the DLL.
-</blockquote>
-Building gd From the Source
-<p>
-In order to build gd, you must first unpack the archive you have
-downloaded. If you are not familiar with <code>tar</code> and
-<code>gunzip</code> (Unix) or <code>ZIP</code> (Windows), please
-consult with an experienced user of your system. Sorry, we cannot
-answer questions about basic Internet skills.
-<p>
-Unpacking the archive will produce a directory called "gd-2.0.33".
-<p>
-<h4>For Unix</h4>
-<code>cd</code> to the 2.0.33 directory and type:
-<p>
-<code>./configure</code>
-<P>
-<blockquote>
-<STRONG>NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
-<code>/usr/local/lib</code></strong> and the include files are
-installed in <code>/usr/local/include</code>. IF YOU ARE
-UPGRADING, you may wish to use:
-<pre>
-./configure --prefix=/usr
-</pre>
-Rather than just <code>./configure</code>, before typing
-<code>make</code> and <code>make install</code>.
-</blockquote>
-<p>
-If all goes well, this will create a Makefile. If all does not go well --
-for instance, if neither the the JPEG nor the PNG and ZLIB libraries
-are found -- you will need to install those libraries, then come back
-and run <code>configure</code> again. 
-<p>
-If necessary, make changes to the resulting Makefile. Then, 
-type "make". If there are no errors, follow this with "make install". 
-Because gd 2.0 and above installs as a shared library, it is necessary to 
-install the library properly before running gd-based programs.
-<p>
-If you get errors, type <code>./configure --help</code> for more
-information about the available options. In the unlikely event
-that the GNU autoconf-produced configure script does not work well
-for you, you may wish to try <code>configure.pl</code>, a
-simple Perl script with similar but less complete capabilities.
-If all else fails, try renaming <code>makefile.sample</code>
-to <code>Makefile</code>. However, <code>./configure</code> is
-almost always your best bet.
-<blockquote>
-<h4>For Windows</h4>
-Use the DLL version! See the paragraph at the beginning of this sectino.
-If you really want to compile it yourself for some strange reason, read on.
-<p>
-Create a project using your favorite programming environment.
-Copy all of the gd files to the project directory. Add <code>gd.c</code>
-to your project. Add other source files as appropriate. Learning the
-basic skills of creating projects with your chosen C environment
-is up to you. Alternatively, use the free <code>mingw32</code> 
-or <code>cygwin</code> tools, which may prove to be compatible
-with the provided <code>configure</code> script.
-</blockquote>
-<P>
-If you wish to test the library, type "make test" AFTER you have
-successfully executed "make install". This will build
-several test programs, including "gddemo". (Not all of these
-programs are expected to print completely successful messages,
-depending on the nature of the image formats with which some of
-the tests are tried; for instance, WBMP is a black and white
-format, so loss of color information is expected there.)
-Run gddemo to see some of the capabilities of gd. Run
-gdtestft to play with the freetype support, if you have built
-gd with it and have access to truetype fonts.
-<P>
-gddemo should execute without incident, creating the file
-demoout.png. (Note there is also a file named demoin.png,
-which is provided in the package as part of the demonstration.)
-<P>
-Display demoout.png in your PNG viewer. The image should
-be 128x128 pixels and should contain an image of the
-space shuttle with quite a lot of graphical elements drawn
-on top of it.
-<P>
-(If you are missing the demoin.png file, the other items
-should appear anyway.)
-<P>
-Look at demoin.png to see the original space shuttle
-image which was scaled and copied into the output image.
-<P>
-<A NAME="basics"><H3>gd basics: using gd in your program</H3></A>
-gd lets you create PNG or JPEG images on the fly. To use gd in your
-program, include the file gd.h, and link with the gd
-library and the other required libraries; the syntax for
-most Unix flavors is:
-<pre>
--lgd -lpng -lz -ljpeg -lfreetype -lm
-</pre>
-Assuming that all of these libraries are available.
-<P>
-If you want to use the provided simple fonts, include
-gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
-more impressive results, install FreeType 2.x and use the 
-<a href="#gdImageStringFT">gdImageStringFT</a>
-function. If you are not using the provided Makefile and/or a 
-library-based approach, be sure to include the source modules as well in your
-project. (They may be too large for 16-bit memory models,
-that is, 16-bit DOS and Windows.)
-<P>
-Here is a short example program. <strong>(For a more advanced example,
-see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
-it demonstrates additional features!)</strong>
-<P>
-<PRE>
-/* Bring in gd library functions */
-#include "gd.h"
-
-/* Bring in standard I/O so we can output the PNG to a file */
-#include &lt;stdio.h&gt;
-
-int main() {
-  /* Declare the image */
-  <A HREF="#gdImagePtr">gdImagePtr</A> im;
-  /* Declare output files */
-  FILE *pngout, *jpegout;
-  /* Declare color indexes */
-  int black;
-  int white;
-
-  /* Allocate the image: 64 pixels across by 64 pixels tall */
-  im = <A HREF="#gdImageCreate">gdImageCreate</A>(64, 64);
-
-  /* Allocate the color black (red, green and blue all minimum).
-    Since this is the first color in a new image, it will
-    be the background color. */
-  black = <A HREF="#gdImageColorAllocate">gdImageColorAllocate</A>(im, 0, 0, 0);  
-
-  /* Allocate the color white (red, green and blue all maximum). */
-  white = <A HREF="#gdImageColorAllocate">gdImageColorAllocate</A>(im, 255, 255, 255);  
-  
-  /* Draw a line from the upper left to the lower right,
-    using white color index. */
-  <A HREF="#gdImageLine">gdImageLine</A>(im, 0, 0, 63, 63, white);  
-
-  /* Open a file for writing. "wb" means "write binary", important
-    under MSDOS, harmless under Unix. */
-  pngout = fopen("test.png", "wb");
-
-  /* Do the same for a JPEG-format file. */
-  jpegout = fopen("test.jpg", "wb");
-
-  /* Output the image to the disk file in PNG format. */
-  <A HREF="#gdImagePng">gdImagePng</A>(im, pngout);
-
-  /* Output the same image in JPEG format, using the default
-    JPEG quality setting. */
-  <A HREF="#gdImageJpeg">gdImageJpeg</A>(im, jpegout, -1);
-
-  /* Close the files. */
-  fclose(pngout);
-  fclose(jpegout);
-
-  /* Destroy the image in memory. */
-  <A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-}
-</PRE>
-When executed, this program creates an image, allocates
-two colors (the first color allocated becomes the background
-color), draws a diagonal line (note that 0, 0 is the upper
-left corner), writes the image to PNG and JPEG files, and
-destroys the image.
-<P>
-The above example program should
-give you an idea of how the package works.
-gd provides many additional functions, which are listed
-in the following reference chapters, complete with code
-snippets demonstrating each. There is also an
-<A HREF="#index">alphabetical index</A>.
-<H3><A NAME="webpng">Webpng: a more powerful gd example</A></H3>
-Webpng is a simple utility program to manipulate PNGs from the
-command line. It is written for Unix and similar command-line
-systems, but should be easily adapted for other environments.
-Webpng allows you to set transparency and interlacing and
-output interesting information about the PNG in question.
-<P>
-webpng.c is provided in the distribution. Unix users can
-simply type "make webpng" to compile the program. Type
-"webpng" with no arguments to see the available options.
-<H2><A NAME="reference">Function and type reference</A></H2>
-<UL>
-<LI><A HREF="#types">Types</A></LI>
-<LI><A HREF="#creating">Image creation, destruction, loading and saving</A></LI>
-<LI><A HREF="#drawing">Drawing, styling, brushing, tiling and
-filling functions</A></LI>
-<LI><A HREF="#query">Query functions (not color-related)</A></LI>
-<LI><A HREF="#fonts">Font and text-handling functions</A></LI>
-<LI><A HREF="#colors">Color handling functions</A></LI>
-<LI><A HREF="#copying">Copying, resizing, rotating, deformation and filter
-functions</A></LI>
-<LI><A HREF="#misc">Miscellaneous Functions</A></LI>
-<LI><A HREF="#constants">Constants</A></LI>
-</UL>
-<H3><A NAME="types">Types</A></H3>
-<DL>
-<DT><A NAME="gdImage"><code>gdImage</code><strong>(TYPE)</strong></A>
-<DD>
-The data structure in which gd stores images. <A HREF="#gdImageCreate">
-gdImageCreate</A>, <a href="#gdImageCreateTrueColor">gdImageCreateTrueColor</a>
-and the various image file-loading functions return
-a pointer to this type, and the other functions expect to receive
-a pointer to this type as their first argument. It is reasonably safe to
-examine any of the members of this structure. It is also reasonably
-safe to modify individual pixels within the <code>pixels</code> 
-or <code>tpixels</code> arrays. If the <code>trueColor</code> flag
-is set, the <code>tpixels</code> array is valid; otherwise the
-<code>pixels</code> array is valid.
-<p>
-The <code>colorsTotal</code>, <code>red</code>, <code>green</code>,
-<code>blue</code>, <code>alpha</code> and <code>open</code> arrays
-manage the palette. They are valid only when the <code>trueColor</code>
-flag is not set. 
-The <code>transparent</code> value contains the palette index of the first
-transparent color as read-only information for backwards compatibility;
-gd 2.0 stores this information in the <code>alpha</code> array so that
-variable transparency can be supported for each palette entry. However,
-for truecolor images, <code>transparent</code> represents a single
-RGB color which is <strong>always 100% transparent</strong>, and this
-feature is generally supported by browsers which do not support 
-full alpha channels.
-<PRE>
-typedef struct {
-  /* Palette-based image pixels */
-  unsigned char ** pixels;
-  int sx;
-  int sy;
-  /* These are valid in palette images only. See also
-  /* 'alpha', which appears later in the structure to
-    preserve binary backwards compatibility */
-  int colorsTotal;
-  int red[gdMaxColors];
-  int green[gdMaxColors];
-  int blue[gdMaxColors]; 
-  int open[gdMaxColors];
-  /* For backwards compatibility, this is set to the
-    first palette entry with 100% transparency,
-    and is also set and reset by the 
-    gdImageColorTransparent function. Newer
-    applications can allocate palette entries
-    with any desired level of transparency; however,
-    bear in mind that many viewers, notably
-    many web browsers, fail to implement
-    full alpha channel for PNG and provide
-    support for full opacity or transparency only. */
-  int transparent;
-  int *polyInts;
-  int polyAllocated;
-  struct gdImageStruct *brush;
-  struct gdImageStruct *tile;  
-  int brushColorMap[gdMaxColors];
-  int tileColorMap[gdMaxColors];
-  int styleLength;
-  int stylePos;
-  int *style;
-  int interlace;
-  /* New in 2.0: alpha channel for palettes. Note that only
-    Macintosh Internet Explorer and (possibly) Netscape 6
-    really support multiple levels of transparency in
-    palettes, to my knowledge, as of 2/15/01. Most
-    common browsers will display 100% opaque and
-    100% transparent correctly, and do something 
-    unpredictable and/or undesirable for levels
-    in between. TBB */
-  int alpha[gdMaxColors]; 
-  /* Truecolor flag and pixels. New 2.0 fields appear here at the
-    end to minimize breakage of existing object code. */
-  int trueColor;
-  int ** tpixels;
-  /* Should alpha channel be copied, or applied, each time a
-    pixel is drawn? This applies to truecolor images only.
-    No attempt is made to alpha-blend in palette images,
-    even if semitransparent palette entries exist. 
-    To do that, build your image as a truecolor image,
-    then quantize down to 8 bits. */
-  int alphaBlendingFlag;
-  /* Should the alpha channel of the image be saved? This affects
-    PNG at the moment; other future formats may also
-    have that capability. JPEG doesn't. */
-  int saveAlphaFlag;
-} gdImage;
-</PRE>
-<p>
-The order of the structure members may appear confusing, but was chosen
-deliberately to increase backwards compatibility with existing gd 1.x-based
-binary code that references particular structure members.
-<DT><A NAME="gdImagePtr">gdImagePtr</A> <strong>(TYPE)</strong>
-<DD>
-A pointer to an image structure. <A HREF="#gdImageCreate">gdImageCreate</A>
-returns this type, and the other functions expect it as the first
-argument.
-<DT><A NAME="gdIoCtx">gdIOCtx</a> <strong>(TYPE)</strong>
-<DD>
-Most of the gd functions that read and write files, such as
-<a href="#gdImagePng">gdImagePng</a> and <a href="#gdImageCreateFromJpeg"></a>,
-also have variants that accept a gdIOCtx structure; see
-<a href="#gdImagePngCtx">gdImagePngCtx</a> and 
-<a href="#gdImageCreateFromJpegCtx">gdImageCreateFromJpegCtx</a>. Those who wish to provide
-their own custom routines to read and write images can populate a
-gdIOCtx structure with functions of their own devising to 
-to read and write data. For image reading, the only mandatory
-functions are getC and getBuf, which must return the number of
-characters actually read, or a negative value on error or EOF.
-These functions must read the number of characters requested 
-unless at the end of the file. For image writing, the only mandatory 
-functions are putC and putBuf, which return the number of 
-characters written; these functions must write the number of 
-characters requested except in the event of an error. The seek
-and tell functions are only required in conjunction with the
-<code>gd2</code> file format, which supports quick loading of
-partial images. The gd_free function will not be invoked when
-calling the standard Ctx functions; it is an implementation
-convenience when adding new data types to gd. For examples,
-see gd_png.c, gd_gd2.c, gd_jpeg.c, etc., all of which rely
-on gdIOCtx to implement the standard image read and write functions.
-
-<pre>
-typedef struct gdIOCtx
-{
-  int (*getC) (struct gdIOCtx *);
-  int (*getBuf) (struct gdIOCtx *, void *, int wanted);
-
-  void (*putC) (struct gdIOCtx *, int);
-  int (*putBuf) (struct gdIOCtx *, const void *, int wanted);
-
-  /* seek must return 1 on SUCCESS, 0 on FAILURE. Unlike fseek! */
-  int (*seek) (struct gdIOCtx *, const int);
-
-  long (*tell) (struct gdIOCtx *);
-
-  void (*gd_free) (struct gdIOCtx *);
-
-} gdIOCtx;
-</pre>
-
-
-<DT><A NAME="gdFont">gdFont</A> <strong>(TYPE)</strong>
-<DD>
-A font structure. Used to declare the characteristics of a font.
-Please see the files gdfontl.c and gdfontl.h for an example of the
-proper declaration of this structure. You can provide your
-own font data by providing such a structure and the associated
-pixel array. You can determine the width and height of a single
-character in a font by examining the w and h members of the
-structure. If you will not be creating your own fonts, you will
-not need to concern yourself with the rest of the components of this
-structure.
-<PRE>
-typedef struct {
-  /* # of characters in font */
-  int nchars;
-  /* First character is numbered... (usually 32 = space) */
-  int offset;
-  /* Character width and height */
-  int w;
-  int h;
-  /* Font data; array of characters, one row after another.
-    Easily included in code, also easily loaded from
-    data files. */
-  char *data;
-} gdFont;
-</PRE>
-<DT><A NAME="gdFontPtr">gdFontPtr</A> <strong>(TYPE)</strong>
-<DD>
-A pointer to a font structure. Text-output functions expect these
-as their second argument, following the <A HREF="#gdImagePtr">
-gdImagePtr</A> argument. Two such pointers are declared in the
-provided include files gdfonts.h and gdfontl.h.
-<DT><A NAME="gdPoint">gdPoint</A> <strong>(TYPE)</strong>
-<DD>
-Represents a point in the coordinate space of the image; used
-by <A HREF="#gdImagePolygon">gdImagePolygon</A>,
-<A HREF="#gdImageOpenPolygon">gdImageOpenPolygon</A> and
-<A HREF="#gdImageFilledPolygon">gdImageFilledPolygon</A>.
-<PRE>
-typedef struct {
-        int x, y;
-} gdPoint, *gdPointPtr;
-</PRE>
-<DT><A NAME="gdPointPtr">gdPointPtr</A> <strong>(TYPE)</strong>
-<DD>
-A pointer to a <A HREF="#gdPoint">gdPoint</A> structure; passed
-as an argument to <A HREF="#gdImagePolygon">gdImagePolygon</A>,
-<A HREF="#gdImageOpenPolygon">gdImageOpenPolygon</A>
-and <A HREF="#gdImageFilledPolygon">gdImageFilledPolygon</A>.
-</DL>
-<DT><A NAME="gdFTStringExtra">gdFTStringExtra</a> <strong>(TYPE)</strong>
-<DD>
-A structure used to pass additional parameters to the
-<a href="#gdImageStringFTEx">gdImageStringFTEx</a> function. See
-<a href="#gdImageStringFTEx">gdImageStringFTEx</a> for the
-structure definition.
-</DD>
-<DT><A NAME="gdFTStringExtraPtr">gdFTStringExtraPtr</a> <strong>(TYPE)</strong>
-<DD>
-A pointer to a structure used to pass additional parameters to the
-<a href="#gdImageStringFTEx">gdImageStringFTEx</a> function. See
-<a href="#gdImageStringFTEx">gdImageStringFTEx</a> for the
-structure definition.
-</DD>
-<DT><A NAME="gdSource">gdSource</A> <strong>(TYPE)</strong>
-<DD>
-<pre>
-typedef struct {
-        int (*source) (void *context, char *buffer, int len);
-        void *context;
-} gdSource, *gdSourcePtr;
-</pre>
-Represents a source from which a PNG can be read.
-Programmers who do not wish to read PNGs from a file can provide
-their own alternate input mechanism, using the
-<a href="#gdImageCreateFromPngSource">gdImageCreateFromPngSource</a> function.
-See the documentation of that function for an example of the
-proper use of this type.
-<DT><A NAME="gdSink">gdSink</A> <strong>(TYPE)</strong>
-<DD>
-<PRE>
-typedef struct {
-        int (*sink) (void *context, char *buffer, int len);
-        void *context;
-} gdSink, *gdSinkPtr;
-</PRE>
-Represents a "sink" (destination) to which a PNG can be written.
-Programmers who do not wish to write PNGs to a file can provide
-their own alternate output mechanism, using the
-<a href="#gdImagePngToSink">gdImagePngToSink</a> function.
-See the documentation of that function for an example of the
-proper use of this type.
-<H3><A NAME="creating">Image creation, destruction, loading and saving</A></H3>
-<DL>
-<DT><A NAME="gdImageCreate">gdImageCreate(sx, sy)</A>
-<strong>(FUNCTION)</strong>
-<DD>
-gdImageCreate is called to create palette-based images, with no
-more than 256 colors. Invoke gdImageCreate
-with the x and y dimensions of the desired image. gdImageCreate
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or
-NULL if unable to
-allocate the image. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-im = gdImageCreate(64, 64);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageCreateTrueColor">gdImageCreateTrueColor(sx, sy)</A>
-<strong>(FUNCTION)</strong>
-<DD>
-gdImageCreateTrueColor is called to create truecolor images, with 
-an essentially unlimited number of colors. Invoke gdImageCreateTrueColor
-with the x and y dimensions of the desired image. gdImageCreateTrueColor
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or
-NULL if unable to
-allocate the image. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<p>
-Truecolor images are always filled with black at creation time.
-There is no concept of a "background" color index.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-im = gdImageCreateTrueColor(64, 64);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageCreateFromJpeg">gdImageCreateFromJpeg(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<br>
-<A NAME="gdImageCreateFromJpegPtr">gdImageCreateFromJpegPtr(int size, void *data)</A>
-<strong>(FUNCTION)</strong>
-<br>
-<A NAME="gdImageCreateFromJpegCtx">gdImageCreateFromJpegCtx(gdIOCtx *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-<DD>
-gdImageCreateFromJpeg is called to load truecolor images from JPEG format files.
-Invoke gdImageCreateFromJpeg with an already opened pointer to a file
-containing the desired image.
-gdImageCreateFromJpeg
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new 
-truecolor image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain a JPEG image). gdImageCreateFromJpeg does <em>not</em>
-close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>. <strong>The
-returned image is always a truecolor image.</strong> 
-<p>
-If you already have the
-image file in memory, pass the size of the file and a pointer to the
-file's data to gdImageCreateFromJpegPtr, which is otherwise identical
-to gdImageCreateFromJpeg.
-<p>
-<PRE>
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-... inside a function ...
-FILE *in;
-in = fopen("myjpeg.jpg", "rb");
-im = gdImageCreateFromJpeg(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageCreateFromPng">gdImageCreateFromPng(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromPngPtr">gdImageCreateFromPngPtr(int size, void *data)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromPngCtx">gdImageCreateFromPngCtx(<a href=#gdioctx>gdIOCtx</a> *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-<DD>
-gdImageCreateFromPng is called to load images from PNG format files.
-Invoke gdImageCreateFromPng with an already opened pointer to a file
-containing the desired image.
-gdImageCreateFromPng
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain a PNG image). gdImageCreateFromPng does <em>not</em>
-close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<p>
-If you already have the
-image file in memory, pass the size of the file and a pointer to the
-file's data to gdImageCreateFromPngPtr, which is otherwise identical
-to gdImageCreateFromPng.
-<p>
-If the PNG image being loaded is a truecolor image, the resulting
-gdImagePtr will refer to a truecolor image. If the PNG image
-being loaded is a palette or grayscale image, the resulting
-gdImagePtr will refer to a palette image. gd retains only 8 bits
-of resolution for each of the red, green and blue channels, and
-only 7 bits of resolution for the alpha channel. The former
-restriction affects only a handful of very rare 48-bit color
-and 16-bit grayscale PNG images. The second restriction affects
-all semitransparent PNG images, but the difference is essentially
-invisible to the eye. 7 bits of alpha channel resolution is,
-in practice, quite a lot.
-<PRE>
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-... inside a function ...
-FILE *in;
-in = fopen("mypng.png", "rb");
-im = gdImageCreateFromPng(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageCreateFromPngSource">gdImageCreateFromPngSource(gdSourcePtr in)</A>
-<strong>(FUNCTION)</strong>
-<dd>
-<b>Deprecated</b> in favor of
-<a href="#gdImageCreateFromPngCtx">gdImageCreateFromPngCtx</a>. Should
-not be used in new applications.
-<p>
-gdImageCreateFromPngSource is called to load a PNG from
-a data source other than a file. Usage is very similar to
-the <a href="#gdImageCreateFromPng">gdImageCreateFromPng</a> function,
-except that the programmer provides a custom data source.
-<p>
-The programmer must write an input function which accepts
-a context pointer, a buffer, and a number of bytes to be
-read as arguments. This function must read the number of
-bytes requested, unless the end of the file has been reached,
-in which case the function should return zero, or an error
-has occurred, in which case the function should return
-<code>-1</code>. The programmer then creates a
-<a href="#gdSource">gdSource</a> structure and sets
-the <code>source</code> pointer to the input function and
-the context pointer to any value which is useful to the
-programmer.
-<p>
-The example below
-implements <a href="#gdImageCreateFromPng">gdImageCreateFromPng</a>
-by creating a custom data source and invoking gdImageCreateFromPngSource.
-<pre>
-static int freadWrapper(void *context, char *buf, int len);
-
-gdImagePtr gdImageCreateFromPng(FILE *in)
-{
-        gdSource s;
-        s.source = freadWrapper;
-        s.context = in;
-        return gdImageCreateFromPngSource(&s);
-}
-
-static int freadWrapper(void *context, char *buf, int len)
-{
-        int got = fread(buf, 1, len, (FILE *) context);
-        return got;
-}
-</pre>
-<DT><A NAME="gdImageCreateFromGif">gdImageCreateFromGif(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromGifPtr">gdImageCreateFromGifPtr(int size, void *data)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromGifCtx">gdImageCreateFromGifCtx(<a href=#gdioctx>gdIOCtx</a> *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-<DD>
-gdImageCreateFromGif is called to load images from GIF format files.
-Invoke gdImageCreateFromGif with an already opened pointer to a file
-containing the desired image.
-gdImageCreateFromGif
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain a GIF image). gdImageCreateFromGif does <em>not</em>
-close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<p>
-If you already have the
-image file in memory, pass the size of the file and a pointer to the
-file's data to gdImageCreateFromGifPtr, which is otherwise identical
-to gdImageCreateFromGif.
-<PRE>
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-... inside a function ...
-FILE *in;
-in = fopen("mygif.gif", "rb");
-im = gdImageCreateFromGif(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageCreateFromGd">gdImageCreateFromGd(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<br><DT><A NAME="gdImageCreateFromGdPtr">gdImageCreateFromGdPtr(int size, void *data)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromGdCtx">gdImageCreateFromGdCtx(<a href=#gdioctx>gdIOCtx</a> *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-<DD>
-gdImageCreateFromGd is called to load images from gd format files.
-Invoke gdImageCreateFromGd
-with an already opened pointer to a file containing the desired image
-in the <A HREF="#gdformat">gd file format</A>, which is specific to
-gd and intended for very fast loading. (It is <em>not</em> intended for
-compression; for compression, use PNG or JPEG.)
-<p>
-If you already have the
-image file in memory, pass the size of the file and a pointer to the
-file's data to gdImageCreateFromGdPtr, which is otherwise identical
-to gdImageCreateFromGd.
-<p>
-gdImageCreateFromGd
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain a gd format image). gdImageCreateFromGd does <em>not</em>
-close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-FILE *in;
-in = fopen("mygd.gd", "rb");
-im = gdImageCreateFromGd(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-
-<DT><A NAME="gdImageCreateFromGd2">gdImageCreateFromGd2(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<br><A NAME="gdImageCreateFromGd2Ptr">gdImageCreateFromGd2Ptr(int size, void *data)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromGd2Ctx">gdImageCreateFromGd2Ctx(<a href=#gdioctx>gdIOCtx</a> *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-
-<DD>
-gdImageCreateFromGd2 is called to load images from gd2 format files.
-Invoke gdImageCreateFromGd2
-with an already opened pointer to a file containing the desired image
-in the <A HREF="#gdformat">gd2 file format</A>, which is specific to
-gd2 and intended for fast loading of parts of large images. 
-(It is a compressed format, but generally not as good as maximum
-compression of the entire image would be.) 
-<p>
-If you already have the
-image file in memory, pass the size of the file and a pointer to the
-file's data to gdImageCreateFromGd2Ptr, which is otherwise identical
-to gdImageCreateFromGd2.
-<p>
-gdImageCreateFromGd2
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain a gd format image). gdImageCreateFromGd2 does <em>not</em>
-close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-FILE *in;
-in = fopen("mygd.gd2", "rb");
-im = gdImageCreateFromGd2(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-
-<DT><A NAME="gdImageCreateFromGd2Part">gdImageCreateFromGd2Part(FILE *in, int srcX, int srcY, int w, int h)</A>
-<strong>(FUNCTION)</strong>
-<br><A NAME="gdImageCreateFromGd2PartPtr">gdImageCreateFromGd2PartPtr(int size, void *data, int srcX, int srcY, int w, int h)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromGd2PartCtx">gdImageCreateFromGd2PartCtx(<a href=#gdioctx>gdIOCtx</a> *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-
-<DD>
-gdImageCreateFromGd2Part is called to load parts of images from <A HREF="#gdformat">gd2 format files</a>.
-Invoked in the same way as <a href=#gdImageCreateFromGd2>gdImageCreateFromGd2</a>,
-but with extra parameters
-indicating the source (x, y) and width/height of the desired image.
-gdImageCreateFromGd2Part returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the
-new image, or NULL if unable to load the image.
-The image must eventually be destroyed using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<p>
-If you already have the image file in memory, you may use
-gdImageCreateFromGd2PartPtr. Pass the size of the image file,
-in bytes, as the first argument and the pointer to the image file data
-as the second argument.
-<p>
-<DT><A NAME="gdImageCreateFromWBMP">gdImageCreateFromWBMP(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromWBMPPtr">gdImageCreateFromWBMPPtr(int size, void *data)</A>
-<strong>(FUNCTION)</strong>
-<BR><A NAME="gdImageCreateFromWBMPCtx">gdImageCreateFromWBMPCtx(<a href=#gdioctx>gdIOCtx</a> *in)</A>
-<strong>(FUNCTION)</strong>
-<p>
-<DD>
-gdImageCreateFromWBMP is called to load images from WBMP format files.
-Invoke gdImageCreateFromWBMP with an already opened pointer to a file
-containing the desired image.
-gdImageCreateFromWBMP
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain a PNG image). gdImageCreateFromWBMP does <em>not</em>
-close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<p>
-If you already have the
-image file in memory, pass the size of the file and a pointer to the
-file's data to gdImageCreateFromWBMPPtr, which is otherwise identical
-to gdImageCreateFromWBMP.
-<PRE>
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-... inside a function ...
-FILE *in;
-in = fopen("mywbmp.wbmp", "rb");
-im = gdImageCreateFromWBMP(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<p>
-<DT><A NAME="gdImageCreateFromXbm">gdImageCreateFromXbm(FILE *in)</A>
-<strong>(FUNCTION)</strong>
-<DD>
-gdImageCreateFromXbm is called to load images from X bitmap format
-files. Invoke gdImageCreateFromXbm
-with an already opened pointer to a file containing the desired image.
-gdImageCreateFromXbm
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain an X bitmap format image). gdImageCreateFromXbm does
-<em>not</em> close the file. You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-FILE *in;
-in = fopen("myxbm.xbm", "rb");
-im = gdImageCreateFromXbm(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageCreateFromXpm">gdImageCreateFromXpm(char *filename)</A>
-<strong>(FUNCTION)</strong>
-<DD>
-gdImageCreateFromXbm is called to load images from XPM X Window System
-color bitmap format files. This function is available only if HAVE_XPM
-is selected in the Makefile and the Xpm library is linked with the
-application. Unlike most gd file functions, the Xpm functions require
-filenames, not file pointers. 
-gdImageCreateFromXpm
-returns a <A HREF="#gdImagePtr">gdImagePtr</A> to the new image, or NULL
-if unable to load the image (most often because the file is corrupt or
-does not contain an XPM bitmap format image). You can inspect the sx and sy members of the
-image to determine its size. The image must eventually be destroyed
-using <A HREF="#gdImageDestroy">gdImageDestroy()</A>.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-FILE *in;
-in = fopen("myxpm.xpm", "rb");
-im = gdImageCreateFromXpm(in);
-fclose(in);
-/* ... Use the image ... */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageDestroy">gdImageDestroy(gdImagePtr im)</A> <STRONG>(FUNCTION)</STRONG>
-<DD>gdImageDestroy is used to free the memory associated with
-an image. It is important to invoke gdImageDestroy before
-exiting your program or assigning a new image to
-a <A HREF="#gdImagePtr">gdImagePtr</A> variable.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-im = <A HREF="#gdImageCreate">gdImageCreate</A>(10, 10);
-/* ... Use the image ... */
-/* Now destroy it */
-<A HREF="#gdImageDestroy">gdImageDestroy</A>(im);
-</PRE>
-<DT><A NAME="gdImageJpeg">
-void gdImageJpeg(gdImagePtr im, FILE *out, int quality)</A>
-<STRONG>(FUNCTION)</STRONG><BR>
-<a name="gdImageJpegCtx">void gdImageJpegCtx(gdImagePtr im, gdIOCtx *out, int quality)</A>
-<STRONG>(FUNCTION)</STRONG><BR>
-<DD>
-gdImageJpeg outputs the specified image to the specified
-file in JPEG format. The file must be open for writing. Under MSDOS
-and all versions of Windows, it is important to use "wb" as opposed
-to simply "w" as the mode when opening the file, and under Unix there
-is no penalty for doing so. gdImageJpeg does <em>not</em>
-close the file; your code must do so.
-<P>
-If quality is negative, the default IJG JPEG quality value (which
-should yield a good general quality / size tradeoff for most
-situations) is used.  Otherwise, for practical purposes, quality
-should be a value in the range 0-95, higher quality values usually
-implying both higher quality and larger image sizes.
-<P>
-If you have set image interlacing using
-<A HREF="#gdImageInterlace">gdImageInterlace</A>, this function will
-interpret that to mean you wish to output a progressive JPEG.  Some
-programs (e.g., Web browsers) can display progressive JPEGs
-incrementally; this can be useful when browsing over a relatively slow
-communications link, for example.  Progressive JPEGs can also be
-slightly smaller than sequential (non-progressive) JPEGs.
-<PRE>
-... inside a function ...
-<A HREF="#gdImagePtr">gdImagePtr</A> im;
-int black, white;
-FILE *out;
-/* Create the image */
-im = <A HREF="#gdImageCreate">gdImageCreate</A>(100, 100);
-/* Allocate background */
-white = <A HREF="#gdImageColorAllocate">gdImageColorAllocate</A>(im, 255, 255, 255);
-/* Allocate drawing color */
-black = <A HREF="#gdImageColorAllocate">gdImageColorAllocate</A>(im, 0, 0, 0);
-/* Draw rectangle */
-<A HREF="#gdImageRectangle">gdImageRectangle</A>(im, 0, 0, 99, 99, black);
-/* Open output file in binary mode */