README.html in rmagick-1.7.4 vs README.html in rmagick-1.8.0
- old
+ new
@@ -1,124 +1,110 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
- <title>RMagick 1.7.4 README</title>
+ <title>RMagick 1.8.0 README</title>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="GENERATOR" content="BlueCloth">
</head>
<body>
-<p>RMagick 1.7.4</p>
+<h1>RMagick 1.8.0 README</h1>
-<pre><code>README
+<h2>04/30/05</h2>
+<h2>Table Of Contents</h2>
- 04/02/05
+<ul>
+<li><a href="#intro">Introduction</a></li>
+<li><a href="#contact">Contact Information</a></li>
+<li><a href="#prereq">Prerequisites</a></li>
+<li><a href="#tips">Tips for installing and configuring ImageMagick and GraphicsMagick</a></li>
+<li><a href="#install">Installing RMagick</a>
+<ul>
+<li><a href="#options">Configuration options</a></li>
+<li><a href="#scripts">Running the configure and make scripts</a></li>
+</ul></li>
+<li><a href="#uhoh">Things that can go wrong</a></li>
+<li><a href="#upgrade">Upgrading</a></li>
+<li><a href="#uninstall">Uninstalling</a></li>
+<li><a href="#samples">More samples</a></li>
+<li><a href="#undoc">Undocumented features</a></li>
+<li><a href="#issues">Known issues</a></li>
+<li><a href="#bugs">Reporting bugs</a></li>
+<li><a href="#credits">Credits</a></li>
+<li><a href="#license">License</a></li>
+</ul>
+<h2 id="intro">Introduction</h2>
-Table of Contents
-
-* Introduction <#introduction>
-* Contact information <#contact_information>
-* Prerequisites <#prerequisites>
-* Tips for installing and configuring ImageMagick and GraphicsMagick
- <#tips>
-* Installing RMagick <#installing_rmagick>
- o Configuration options <#configuration_options>
- o Running the configure and make scripts <#running>
-* Things that can go wrong <#things_that_can_go_wrong>
-* Upgrading <#upgrading>
-* Uninstalling <#uninstalling>
-* More samples <#more_samples>
-* Undocumented features <#undocumented_features>
-* Known issues <#known_issues>
-* Reporting bugs <#reporting_bugs>
-* Credits <#credits>
-* License <#license>
-
-
-Introduction
-</code></pre>
-
<p>RMagick is an interface between the Ruby programming language and the
ImageMagick and GraphicsMagick image processing libraries.</p>
-<pre><code>Contact Information
-</code></pre>
+<h2 id="contact">Contact Information</h2>
-<p><em>Author:</em> Tim Hunter
-<em>Email:</em> rmagick@rubyforge.org <mailto:rmagick@rubyforge.org>
-<em>RubyForge:</em> RMagick <a href="http://rubyforge.org/projects/rmagick">http://rubyforge.org/projects/rmagick</a></p>
+<p><strong>Author:</strong> Tim Hunter</p>
-<pre><code>Prerequisites
-</code></pre>
+<p><strong>Email:</strong> <a href="mailto:rmagick@rubyforge.org">rmagick@rubyforge.org</a></p>
-<p><em>O/S</em>
- Linux, Sun Solaris, Cygwin, FreeBSD, MS Windows 98 and later.
-<em>Ruby</em>
- Ruby 1.6.7 or later. You can get Ruby from www.ruby-lang.org
- <a href="http://www.ruby-lang.org">http://www.ruby-lang.org</a></p>
+<p><strong>RubyForge:</strong> <a href="http://rubyforge.org/projects/rmagick/">http://rubyforge.org/projects/rmagick/</a></p>
-<p>One of</p>
+<h2 id="prereq">Prerequisites</h2>
-<p><em>ImageMagick</em>
- ImageMagick 6.0.0 or later. You can get ImageMagick from
- www.imagemagick.org <a href="http://www.imagemagick.org">http://www.imagemagick.org</a>.
-<em>GraphicsMagick</em>
- GraphicsMagick is a friendly fork of ImageMagick 5.5.1. You can get
- GraphicsMagick from www.graphicsmagick.org
- <a href="http://www.graphicsmagick.org">http://www.graphicsmagick.org</a>.</p>
+<p><strong>O/S:</strong> Linux, Sun Solaris, Cygwin, FreeBSD, MS Windows 98 and later.</p>
-<p>You only need one of ImageMagick or GraphicsMagick. RMagick works
-equally well with both. Some RMagick methods may not be supported in one
-or the other library.</p>
+<p><strong>Ruby</strong> 1.6.7 or later. You can get Ruby from <a href="http://www.ruby-lang.org">http://www.ruby-lang.org</a>.</p>
-<pre><code>Tips for installing and configuring ImageMagick and GraphicsMagick
-</code></pre>
+<p>Either <strong>ImageMagick</strong> 6.0.0 or later, or any release of
+<strong>GraphicsMagick</strong>. GraphicsMagick is a friendly fork of ImageMagick
+5.5.1. You can get ImageMagick from <a href="http://www.imagemagick.org">http://www.imagemagick.org</a>. You
+can get GraphicsMagick from <a href="http://www.graphicsmagick.org">http://www.graphicsmagick.org</a>. ImageMagick
+and GraphicsMagick have slightly different capabilities. Please consult
+their web sites if you have questions.</p>
-<p>if you are installing RMagick by compiling the source code, I /strongly/
+<h2 id="tips">Tips for installing and configuring ImageMagick and GraphicsMagick</h2>
+
+<p>If you are installing RMagick by compiling the source code, I strongly
encourage you to install the latest version of ImageMagick or
-GraphicsMagick /from source/. If you have never installed ImageMagick or
+GraphicsMagick <em>from source</em>. If you have never installed ImageMagick or
GraphicsMagick before, I also strongly encourage you to read the
-README.txt file as many times as is necessary for you to understand how
-to configure it. ImageMagick and GraphicsMagick are large and
-complicated programs and can be difficult to configure. Follow these
-tips to minimize the amount of time you'll spend and your frustration level.</p>
+README.txt file as many times as is necessary for you to understand how to
+configure it. ImageMagick and GraphicsMagick are large and complicated
+programs and can be difficult to configure. Follow these tips to minimize
+the amount of time you'll spend and your frustration level.</p>
-<p>Do /not/ simply type ./configure and expect the defaults to be correct
-for you. Since you are installing ImageMagick/GraphicsMagick to use with
-Ruby, consider whether you want to skip ImageMagick's/GraphicMagicks'
-support for Perl and C++ by using the --without-perl and
---without-magick-plus-plus options. Doing so will speed up the
-installation process and save some disk space. You will almost certainly
-want to specify the --enable-shared and --disable-static options.</p>
+<p><em>Do not</em> simply type <code>./configure</code> and expect the defaults to be correct
+for you. Since you are installing ImageMagick/GraphicsMagick to use with
+Ruby, consider whether you want to skip ImageMagick's/GraphicMagick's
+support for Perl and C++ by using the <code>--without-perl</code> and
+<code>--without-magick-plus-plus</code> options. Doing so will speed up the
+installation process and save some disk space. You will almost certainly
+want to specify the <code>--enable-shared</code> and <code>--disable-static</code> options.</p>
<p>Determine which image formats you are interested in using and make sure
-that you have installed the libraries that ImageMagick/GraphicsMagick
-uses to process these formats. ImageMagick and GraphicsMagick use
-additional libraries to support some image formats. If you do not
-install those libraries you cannot read and write those image formats.
-You will need to configure ImageMagick/GraphicsMagick to support the
-JPG, PNG, TIFF, and WMF formats in order to execute all the RMagick
-sample programs. See ImageMagick's or GraphicMagick's README.txt file
-for more information.</p>
+that you have installed the libraries that ImageMagick/GraphicsMagick uses
+to process these formats. ImageMagick and GraphicsMagick use additional
+libraries to support some image formats. If you do not install those
+libraries you cannot read and write those image formats. You will need to
+configure ImageMagick/GraphicsMagick to support the JPG, PNG, TIFF, and
+WMF formats in order to execute all the RMagick sample programs. See
+ImageMagick's or GraphicMagick's README.txt file for more information.</p>
<p>Once you have determined the configuration options you need, run the
-configure script. When it completes, read the summary output to see if
-configuration worked the way you expected. Here's an example of the
-summary output from ImageMagick's configure script. Notice that the
+configure script. When it completes, read the summary output to see if
+configuration worked the way you expected. Here's an example of the
+summary output from ImageMagick's configure script. Notice that the
result of each option is listed in the "Configured value" column.</p>
-<h2> Option Value</h2>
-
-<p>Shared libraries --enable-shared=yes yes
+<pre><code> Option Value
+-------------------------------------------------------------------------
+Shared libraries --enable-shared=yes yes
Static libraries --enable-static=no no
Module support --with-modules=yes yes
GNU ld --with-gnu-ld=yes yes
LZW support --enable-lzw=yes yes
-Quantum depth --with-quantum-depth=8 8</p>
+Quantum depth --with-quantum-depth=8 8
-<p>Delegate Configuration:
+Delegate Configuration:
BZLIB --with-bzlib=yes yes
DPS --with-dps=yes yes
FlashPIX --with-fpx=yes no
FreeType 2.0 --with-ttf=yes yes
Ghostscript None gs (7.07.2)
@@ -135,290 +121,298 @@
TIFF --with-tiff=yes yes
Windows fonts --with-windows-font-dir=/mnt/windows/windows/fonts /mnt/windows/windows/fonts/
WMF --with-wmf=yes yes
X11 --with-x= yes
XML --with-xml=yes yes
-ZLIB --with-zlib=yes yes</p>
+ZLIB --with-zlib=yes yes
-<p>X11 Configuration:
+X11 Configuration:
X_CFLAGS = -I/usr/X11R6/include
- X<em>PRE</em>LIBS = -lSM -lICE
+ X_PRE_LIBS = -lSM -lICE
X_LIBS = -L/usr/X11R6/lib
- X<em>EXTRA</em>LIBS =</p>
+ X_EXTRA_LIBS =
+</code></pre>
<p>If the results are not what you wanted, install any missing libraries,
choose new or different options, or whatever it takes, erase the
-config.cache file, and re-run configure. Repeat as often as necessary
-before moving to the <code>make' and</code>make install' steps.</p>
+config.cache file, and re-run <code>configure</code>. Repeat as often as necessary
+before moving to the <code>make</code> and <code>make install</code> steps.</p>
<p>Detailed information about all of ImageMagick's and GraphicsMagick's
configuration options may be found in their README.txt and INSTALL.txt
files.</p>
-<pre><code> Windows Metafile Format
-</code></pre>
+<h4>Windows Metafile Format</h4>
<p>As noted in the ImageMagick and GraphicsMagick README.txt files, to
-support images in the Windows Metafile format,
-ImageMagick/GraphicsMagick requires an additional library. Without this
-library some of the RMagick sample programs will not work. ImageMagick
-and GraphicsMagick require libwmf 0.2.5, 0.2.7, or 0.2.2 to support the
-WMF format. (Avoid libwmf 0.2.6!)</p>
+support images in the Windows Metafile format, ImageMagick/GraphicsMagick
+requires an additional library. Without this library some of the RMagick
+sample programs will not work. ImageMagick and GraphicsMagick require
+libwmf 0.2.5, 0.2.7, or 0.2.2 to support the WMF format. (Avoid libwmf
+0.2.6!)</p>
-<pre><code>Installing RMagick
-</code></pre>
+<h2 id="install">Installing RMagick</h2>
<p>Installing RMagick is much simpler than installing ImageMagick or
-GraphicsMagick. Note that the /make/ step runs all the example programs.
-This process both builds the example images used in the documentation
-and validates your RMagick installation. This step can take 5-15 minutes
+GraphicsMagick. Note that the make step runs all the example programs.
+This process both builds the example images used in the documentation and
+validates your RMagick installation. This step can take 5-15 minutes
depending on the speed of your computer.</p>
-<pre><code> Configuration options
-</code></pre>
+<h4 id="options">Configuration Options</h4>
-<p>Type |./configure --help| to see a list of configuration options. In
+<p>Type <code>./configure --help</code> to see a list of configuration options. In
addition to the regular options, there are a few RMagick-specific options:</p>
-<p>--with-doc-dir=directory
- Specify the directory to install the RMagick documentation. By
- default this is $prefix/share/RMagick, where $prefix is the prefix
- specified by --prefix. For example, to install the documentation in
- /home/user/RMagick, specify:</p>
+<ul>
+<li><p>--with-doc-dir=<em>directory</em></p>
-<p>./configure --with-doc-dir=/home/user/RMagick</p>
+<blockquote>
+ <p>Specify the directory to install the RMagick documentation.
+ By default this is $prefix/share/RMagick, where $prefix is the
+ prefix specified by --prefix. For example, to install the
+ documentation in /home/user/RMagick, specify:</p>
+
+ <p><code>./configure --with-doc-dir=/home/user/RMagick</code></p>
+</blockquote></li>
+<li><p>--enable-allow-example-errors</p>
-<p>--enable-allow-example-errors
- Normally the documentation installation terminates if 5 examples
- fail. If you use this option, the installation does not check for
- failing examples and will always complete. This option is useful if
- you're having trouble installing RMagick and you want to see all the
- failing examples.
---with-graphics-magick
- If you have both ImageMagick and GraphicsMagick installed, this
- option will force RMagick to be configured with GraphicsMagick.
---with-so-dir=directory
- The directory for ruby extensions.
---with-ruby-path=directory
- The path to set the !# line in Ruby scripts. The default is
- |$prefix/bin/ruby|.
---with-ruby-prog=name
- The name of the Ruby executable. The default is |ruby|.
---with-make-prog=name
- The name of the |make| program.
---with-rbconfig=path
- The path to the rbconfig.rb file to use. The default is Ruby's rbconfig.</p>
+<blockquote>
+ <p>Normally the documentation installation terminates if 5 examples fail.
+ If you use this option, the installation does not check for failing
+ examples and will always complete. This option is useful if you're having
+ trouble installing RMagick and you want to see all the failing examples.</p>
+</blockquote></li>
+<li><p>--with-graphics-magick</p>
-<pre><code> Running the |configure| and |make| scripts
-</code></pre>
+<blockquote>
+ <p>If you have both ImageMagick and GraphicsMagick installed, this option will
+ force RMagick to be configured with GraphicsMagick.</p>
+</blockquote></li>
+<li><p>--with-so-dir=<em>directory</em></p>
-<p>De-compress the RMagick-1.7.4.tar.gz archive and enter the
-top directory. Then type:</p>
+<blockquote>
+ <p>The directory for ruby extensions.</p>
+</blockquote></li>
+<li><p>--with-ruby-path=<em>directory</em></p>
-<pre><code>$ ./configure <configuration options>
-$ make
-</code></pre>
+<blockquote>
+ <p>The path to set the !# line in Ruby scripts. The default is $prefix/bin/ruby.</p>
+</blockquote></li>
+<li><p>--with-ruby-prog=<em>name</em></p>
-<p>($ su)
- $ make install
- (optionally)
- $ make clean</p>
+<blockquote>
+ <p>The name of the Ruby executable. The default is <code>ruby</code>.</p>
+</blockquote></li>
+<li><p>--with-make-prog=<em>name</em></p>
-<pre><code>Things that can go wrong
-</code></pre>
+<blockquote>
+ <p>The name of the <code>make</code> program.</p>
+</blockquote></li>
+<li><p>--with-rbconfig=<em>directory</em></p>
-<p><em>Cannot open shared object file</em></p>
+<blockquote>
+ <p>The directory of the rbconfig.rb file to use. The default is Ruby's
+ rbconfig.</p>
+</blockquote></li>
+</ul>
-<pre><code>When |make| is running the examples, if you get a message like this:
-</code></pre>
+<h4 id="scripts">Running the <code>configure</code> and <code>make</code> scripts</h4>
-<p>/home/you/RMagick-1.7.4/lib/RMagick.rb:11:in 'require': libMagick.so.0:
- cannot open shared object file: No such file or directory -
- /home/you/RMagick-1.7.4/ext/RMagick/RMagick.so (LoadError)</p>
+<p>De-compress the RMagick-1.8.0.tar.gz archive and enter the top
+directory. Then type:</p>
-<pre><code>you probably do not have the directory in which the ImageMagick or
-GraphicsMagick library is installed in your load path. An easy way
-to fix this is to define the directory in the LD_LIBRARY_PATH
-environment variable. For example, suppose you installed the
-GraphicsMagick library libGraphicsMagick.so in /usr/local/lib. (By
-default this is where it is installed.) Create the LD_LIBRARY_PATH
-variable like this:
+<pre><code>$ ./configure <configuration options>
+$ make
+($ su)
+$ make install
+(optionally)
+$ make clean
</code></pre>
-<p>export LD<em>LIBRARY</em>PATH=/usr/local/lib</p>
+<h2 id="uhoh">Things that can go wrong</h2>
-<pre><code>On Linux, see |ld(1)| and |ld.so(8)| for more information. On other
-operating systems, see the documentation for the dynamic loading
-facility.
-</code></pre>
+<h4>Cannot open shared object file</h4>
-<p><em>No such file or directory - "/tmp/rmagick6872.6"</em></p>
+<p>When make is running the examples, if you get a message like this:</p>
-<pre><code>When |make| is running the examples, if you get a message like this:
+<pre><code>/home/you/RMagick-1.8.0/lib/RMagick.rb:11:in `require': libMagick.so.0:
+ cannot open shared object file: No such file or directory -
+ /home/you/RMagick-1.8.0/ext/RMagick/RMagick.so (LoadError)
</code></pre>
-<p>hook /home/me/src/RMagick-1.7.4/./post-setup.rb failed:
-No such file or directory - "/tmp/rmagick6872.6"</p>
+<p>you probably do not have the directory in which the ImageMagick or GraphicsMagick
+library is installed in your load path. An easy way to fix this is to define the
+directory in the LD<em>LIBRARY</em>PATH environment variable. For example, suppose you
+installed the GraphicsMagick library libGraphicsMagick.so in /usr/local/lib.
+(By default this is where it is installed.) Create the LD<em>LIBRARY</em>PATH variable
+like this:</p>
-<pre><code>you probably do not have a temporary directory environment variable
-set. Set the TMPDIR environment variable to your temporary
-directory. For example:
+<pre><code>export LD_LIBRARY_PATH=/usr/local/lib
</code></pre>
-<p>export TMPDIR=/home/me/tmp</p>
+<p>On Linux, see <code>ld(1)</code> and <code>ld.so(8)</code> for more information. On other operating
+systems, see the documentation for the dynamic loading facility.</p>
-<pre><code>Upgrading
+<h4>No such file or directory - "/tmp/rmagick6872.6"</h4>
+
+<p>When make is running the examples, if you get a message like this:</p>
+
+<pre><code>hook /home/me/src/RMagick-1.8.0/./post-setup.rb failed:
+No such file or directory - "/tmp/rmagick6872.6"
</code></pre>
-<p>If you upgrade to a newer release of ImageMagick or GraphicsMagick, make
-sure you're using a release of RMagick that supports that release.
-Usually I put out a new release of RMagick with every new release of
-ImageMagick. It's safe to install a newer release of RMagick over an
-earlier release.</p>
+<p>you probably do not have a temporary directory environment variable set. Set
+the TMPDIR environment variable to your temporary directory. For example:</p>
-<pre><code>Uninstalling
+<pre><code>export TMPDIR=/home/me/tmp
</code></pre>
-<p>The 'uninstall' target will uninstall RMagick completely:</p>
+<h2 id="upgrade">Upgrading</h2>
-<pre><code>|make uninstall|
+<p>If you upgrade to a newer release of ImageMagick or GraphicsMagick, make sure
+you're using a release of RMagick that supports that release. Usually I put out
+a new release of RMagick with every new release of ImageMagick. It's safe to
+install a newer release of RMagick over an earlier release.</p>
+<h2 id="uninstall">Uninstalling</h2>
-More samples
+<p>The <code>uninstall</code> target will uninstall RMagick completely:</p>
+
+<pre><code>make uninstall
</code></pre>
+<h2 id="samples">More samples</h2>
+
<p>You can find more sample RMagick programs in the /example directory.
These programs are not installed in the RMagick documentation tree.</p>
-<pre><code>Undocumented features
-</code></pre>
+<h2 id="undoc">Undocumented features</h2>
<p>This release includes an extra feature that isn't in the documentation.
The Magick module defines two methods that control ImageMagick's logging
-function. This function is not officially documented by ImageMagick, so
-I have decided not to add them to RMagick's documentation. However, you
-may find them helpful for debugging your application. (Caveat: these two
-methods may change behavior or be removed without advance notice! You
-are on your own!)</p>
+function. This function is not officially documented by ImageMagick, so I
+have decided not to add them to RMagick's documentation. However, you may
+find them helpful for debugging your application. (Caveat: these two
+methods may change behavior or be removed without advance notice! You are
+on your own!)</p>
-<p>/Magick::set<em>log</em>event_mask(event [,...]) -> Magick/</p>
+<h5>Magick::set_log_event_mask(event [,...])</h5>
-<p>The arguments are one or more "event domains". The set<em>log</em>event_mask
-method recognizes these event domains: "all", "annotate", "blob",
-"cache", "coder", "configure", "deprecate", "draw", "locale", "none",
-"resource", "transform", "user", and "x11". ImageMagick events that
-match the mask are logged. The default domain is "none". For example,</p>
+<p>The arguments are one or more "event domains". The set<em>log</em>event_mask
+method recognizes these event domains: "all", "annotate", "blob", "cache",
+"coder", "configure", "deprecate", "draw", "locale", "none", "resource",
+"transform", "user", and "x11". ImageMagick events that match the mask
+are logged. The default domain is "none". For example,</p>
-<pre><code> Magick::set_log_event_mask("render")
+<pre><code> Magick::set_log_event_mask("render")
</code></pre>
-<p>Logging is controlled by the log.mgk file, which may be found in the
-same directory as the delegates.mgk files. (See ImageMagick's README.txt
+<p>Logging is controlled by the log.mgk file, which may be found in the same
+directory as the delegates.mgk files. (See ImageMagick's README.txt
file.) The purpose of the entries in this file is undocumented, so your
-guess is as good as mine. Also, the meaning of the event domains and
+guess is as good as mine. Also, the meaning of the event domains and
exactly what events are logged are undocumented.</p>
-<p>/Magick::set<em>log</em>format(format) -> Magick/</p>
+<h5>Magick::set_log_format(format)</h5>
-<p>The default log format is described in the log.mgk file. This method
-allows you to redefine the format at run-time. The format argument is a
-string similar to an fprintf format string. Each line in the log has the
-format described by the format string. Characters that are not control
-characters are printed as-is. The control characters are:</p>
+<p>The default log format is described in the log.mgk file. This method
+allows you to redefine the format at run-time. The format argument is a
+string similar to an fprintf format string. Each line in the log has the
+format described by the format string. Characters that are not control
+characters are printed as-is. The control characters are:</p>
-<pre><code> %t - the current time
- %r - the elapsed time
- %u - the user time
- %p - the pid (process id)
- %m - the name of the ImageMagick source file that contains the
- function that generated the event
- %f - the name of the ImageMagick function that generated the
- event
- %l - the line number in the source file
- %d - the event domain (one of the event mask strings listed above)
- %e - the event name
+<pre><code> %t - the current time
+ %r - the elapsed time
+ %u - the user time
+ %p - the pid (process id)
+ %m - the name of the ImageMagick source file that contains the
+ function that generated the event
+ %f - the name of the ImageMagick function that generated the event
+ %l - the line number in the source file
+ %d - the event domain (one of the event mask strings listed above)
+ %e - the event name
</code></pre>
<p>For example, the default log format is:</p>
-<pre><code> Magick::set_log_format("%t %r %u %p %m/%f/%l/%d:\n %e")
-
-
-Known issues
+<pre><code> Magick::set_log_format("%t %r %u %p %m/%f/%l/%d:\n %e")
</code></pre>
+<h2 id="issues">Known issues</h2>
+
<ol>
-<li>gcc 3.2, during the "install.rb setup" step, issues the warning:</li>
-</ol>
+<li><p>gcc 3.2, during the "install.rb setup" step, issues the following warning.
+This does not indicate a problem.</p>
-<p>cc1: warning: changing search order for system directory "/usr/local/include"
-cc1: warning: as it has already been specified as a non-system directory</p>
+<p><code>cc1: warning: changing search order for system directory "/usr/local/include"</code> <br>
+<code>cc1: warning: as it has already been specified as a non-system directory</code></p></li>
+<li><p>With older releases of ImageMagick you may see this warning. It does not
+indicate a problem.</p>
-<pre><code> This does not indicate a problem.
-</code></pre>
-
-<ol>
-<li>With older releases of ImageMagick you may see the warning:</li>
+<p><code>/usr/include/sys/ipc.h:25:3: warning: #warning "Files using this header must
+be compiled with _SVID_SOURCE or _XOPEN_SOURCE"</code></p></li>
</ol>
-<p>/usr/include/sys/ipc.h:25:3: warning: #warning "Files using this header must be compiled with <em>SVID</em>SOURCE or <em>XOPEN</em>SOURCE"</p>
+<h2 id="bugs">Reporting bugs</h2>
-<pre><code> This is harmless.
-
-
-Reporting bugs
-</code></pre>
-
<p>Please report bugs in RMagick, its documentation, or its installation
-programs to me via the bug tracker on the RMagick project page
-<a href="http://rubyforge.org/projects/rmagick/">http://rubyforge.org/projects/rmagick/</a> at RubyForge. However, I cannot
-help with Ruby installation and configuration or ImageMagick or
-GraphicsMagick installation and configuration. Please report problems
-with that software to their respective authors or distributors.</p>
+programs to me via the bug tracker on the <a href="http://rubyforge.org/projects/rmagick">RMagick project page at
+RubyForge</a>. However, I can't help
+with Ruby installation and configuration or ImageMagick or GraphicsMagick
+installation and configuration. Please report problems with that software
+to their respective authors or distributors.</p>
-<pre><code>Credits
-</code></pre>
+<h2 id="credits">Credits</h2>
<p>Thanks to</p>
-<pre><code>* Akinori MUSHA, for his work making RMagick available on FreeBSD.
-* Tom Payne, for reporting bugs, sending me the Ruby 1.8.0 patches,
- and for the Gentoo ebuild.
-* Bob Friesenhahn, for GraphicsMagick. Also for his help with the
- RMagick installation and many other things.
-* Simple Systems, for hosting the RMagick documentation online.
-* Mike Williams, for the RMagick Debian package
-* ImageMagick Studio LLC, for ImageMagick and for hosting the
- RMagick documentation.
-* Kaspar Schiess, for the MS Windows gem.
+<ul>
+<li>Akinori MUSHA, for his work making RMagick available on FreeBSD.</li>
+<li>Tom Payne, for reporting bugs, sending me the Ruby 1.8.0 patches, and for the Gentoo ebuild.</li>
+<li>Bob Friesenhahn, for GraphicsMagick. Also for his help with the RMagick installation and many other things.</li>
+<li>Simple Systems, for hosting the RMagick documentation online.</li>
+<li>Mike Williams, for the RMagick Debian package</li>
+<li>ImageMagick Studio LLC, for ImageMagick and for hosting the RMagick documentation.</li>
+<li>Kaspar Schiess, for the MS Windows gem.</li>
+<li>Jeremy Hinegardner, for the amd64 patch.</li>
+</ul>
+<h2 id="license">License</h2>
-License
-</code></pre>
+<blockquote>
+ <p>Copyright © 2005 by Timothy P. Hunter</p>
+
+ <p>Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:</p>
+
+ <p>The above copyright notice and this permission notice shall be included in
+ all copies or substantial portions of the Software.</p>
+
+ <p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+ THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.</p>
+</blockquote>
-<p>Copyright © 2004 by Timothy P. Hunter</p>
+<div align="center">
+<a href="http://www.opensource.org/docs/definition.php">
+<img src="http://opensource.org/trademarks/osi-certified/web/osi-certified-90x75.gif"
+border="0" width="90" height="75">
+</a>
+</div>
-<p>Permission is hereby granted, free of charge, to any person obtaining a
-copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:</p>
+<hr/>
-<p>The above copyright notice and this permission notice shall be included
-in all copies or substantial portions of the Software.</p>
-
-<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
-
-<p><a href="http://www.opensource.org/docs/definition.php">http://www.opensource.org/docs/definition.php</a></p>
-
-<p>*This software is OSI Certified Open Source Software.
-OSI Certified is a certification mark of the Open Source Initiative.*</p>
+<p><em>
+This file is marked up using <a href="http://daringfireball.net/projects/markdown">Markdown</a>.
+The HTML version was produced with <a href="http://bluecloth.rubyforge.org">BlueCloth</a>.
+</em></p>
</body>
</html>