> "I swear by my life and my love of it that I will never live for the sake of another man, nor ask another man to live for mine"

> John Galt in Atlas Shrugged, by Ayn Rand

Contents

- Author
- Availability
- WWW
- Mailing List
- Memory Requirements
- UNIX Compilation
- Delegates
- How to Compile
- VMS Compilation
- NT Compilation
- Macintosh Compilation
- Animation
- 16-BIT Imaging
- 64-BIT Machines
- MIFF Image Format
- Copyright

Author

  The author is magick@wizards.dupont.com. This software is NOT shareware. However, I am interested in who might be using it. Please consider sending me a picture postcard of the area where you live. Send postcards to

          John Cristy
          P.O. Box 40
          Landenberg, PA  19350
          USA

  I'm also interested in receiving coins or stamps from around the world for my collection.

Back to Contents

Availability

  ImageMagick, version 4.2.9, is available on ftp.wizards.dupont.com. ImageMagick client executables are available for some platforms. Macintosh, NT, VMS, and Linux source and binaries are also available.

I want ImageMagick to be of high quality, so if you encounter a problem I will investigate. However, be sure you are using the most recent version from ftp.wizards.dupont.com, or a mirror site, before submitting any bug reports or suggestions.

Back to Contents

WWW

  The official ImageMagick WWW page is at www.wizards.dupont.com.

  To use display as your external image viewer, edit the global mailcap file or your personal mailcap file .mailcap (located in your home directory) and put this entry:

          image/*; display %s

Back to Contents

Mailing List

  There is a mailing list for discussions and bug reports about ImageMagick. To subscribe send the message

          subscribe magick

to majordomo@wizards.dupont.com. You will receive a welcome message which tells you how to post messages to the list magick@wizards.dupont.com.

Back to Contents

Memory Requirements

  You should allocate sufficient swap space on your system before running ImageMagick; otherwise, you may experience random server or application crashes. Anything less than 80 megabytes of swap space is likely to cause random crashes.

  On many systems, you will find that 80 megabytes is insufficient and you will have to allocate more swap space. You should also have at least 32 megabytes of real memory although 64 megabytes or more is recommended.

Back to Contents

UNIX Compilation

  Type:

          gzip -dc ImageMagick-4.2.9.tar.gz | tar xvf -
          cd ImageMagick-4.2.9

  If you do not have `gunzip`, it is available on prep.ai.mit.edu.

There are currently two mechanisms available to create makefiles to build ImageMagick:

- GNU configure:

This option is easiest to use and is recommended when ImageMagick is to be installed outside of the X11 distribution or working imake configuration files are not available. Use of `configure` enables automated configuration, building, and installation of PerlMagick.

If you are willing to accept configure's default options, type:

          ./configure

and watch the configure script output to verify that it finds everything that you think it should. If it does not, then adjust your environment so that it does.

If you are not happy with configure's choice of compiler, compilation flags, or libraries, you can give `configure` initial values for variables by setting them in the environment. Using a Bourne-compatible shell, you can do that on the command line like this:

        CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env` program, you can do it like this

        env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

The configure variables you should be aware of are:

            CC          Name of C compiler (e.g. 'cc -Xa') to use
            CFLAGS      Compiler flags (e.g. '-g -O2') to compile with
            CPPFLAGS    Include paths (-I/somedir) to look for header files
            LDFLAGS     Library paths (-L/somedir) to look for libraries
                        Systems that support the notion of a library
                        run-path may additionally require -R/somedir or
                        '-rpath /somedir' in order to find shared libraries
                        at run time.
            LIBS        Extra libraries (-lsomelib) required to link

Any variable (e.g. CPPFLAGS or LDFLAGS) which requires a directory path must specify an absolute path rather than a relative path.

By default, `make install` will install the package's files in `/usr/local/bin`, `/usr/local/man`, etc. You can specify an installation prefix other than `/usr/local` by giving configure the option `--prefix=PATH`.

Configure can usually find the X include and library files automatically, but if it doesn't, you can use the configure options `--x-includes=DIR` and `--x-libraries=DIR` to specify their locations.

The configure script provides a number of ImageMagick specific options. When disabling an option --disable-something is equivalent to specifying --enable-something=no and --without-something is equivalent to --with-something=no. The configure options are as follows (execute `configure --help` to see all options).

          --enable-shared      build shared libraries (default is no)
          --enable-static      build static libraries (default is yes)
          --enable-lzw         enable LZW support (default is no)
          --enable-16bit-pixel enable 16 bit pixels (default is no)
          --enable-socks       enable use of SOCKS 5 library and 'rftp'
          --with-perl          enable build/install of PerlMagick (default is yes)
          --with-bzlib         enable BZlib (default is yes)
          --with-dps           enable Display Postscript (default is yes)
          --with-fpx           enable FlashPIX (default is yes)
          --with-hdf           enable HDF (default is yes)
          --with-jbig          enable JBIG (default is yes)
          --with-jpeg          enable JPEG (default is yes)
          --with-png           enable PNG (default is yes)
          --with-tiff          enable TIFF (default is yes)
          --with-ttf           enable TrueType (default is yes)
          --with-zlib          enable Zlib (default is yes)
          --with-x             use the X Window System

ImageMagick options represent either features to be enabled or packages to be included in the build. When a feature is enabled (via --enable-something), it enables code already present in ImageMagick. When a package is enabled (via --with-something), the configure script will search for it, and if is is properly installed and ready to use (headers and built libraries are found by compiler) it will be included in the build. The configure script is delivered with all features disabled and all packages enabled. In general, the only reason to disable a package is if a package exists but it is unsuitable for the build (perhaps an old versionor not compiled with the right compilation flags).

Several configure options require special note:

- `--disable-shared`: the shared libraries is not built. Shared libraries are valuable because they are shared across more than one invocation of an ImageMagick or PerlMagick client. In addition, the clients take much less disk space and shared libraries are required in order for PERL to dynamically load the PerlMagick extension.

ImageMagick built with delegates (see Delegates below) can pose additional challenges. You can build all the delegates statically and link them into the ImageMagick shared library (i.e. `libMagick.so`) or alternatively you can build the delegates as shared libraries (some systems already have delegates installed as shared libraries). Shared libraries compilation flags differ from vendor to vendor (gcc's is `-fPIC`). However, you must compile all shared library source with the same flag (for gcc use `-fPIC` rather than `-fpic`).

- `--disable-static`: static archive libraries (with extension `.a`) are not built. If you are building shared libraries, there is little value to building static libraries. Reasons to build static libraries include: 1) they can be easier to debug; 2) the clients do not have external dependencies (i.e. `libMagick.so`); 3) building PIC versions of the delegate libraries may take additional expertise and effort; 4) you are unable to build shared libraries.

- `--without-frozenpaths`: By default, the configure script will determine the location of all delegates (external programs) and incorporate the full paths within the `delegates.mgk` file. This is the default because it is assumed that the installer's environment is appropriately configured and that the operation of ImageMagick should not be subject to the end-user's environment. However, if it is desireable to allow the end user to define their own environment or possible that the end user's environment does not match the installer's environment (e.g. for binary distributions), `--without-frozenpaths` may be specified so that only the delegate's name is included in the delegates.mgk file.

- `--without-perl`: By default, PerlMagick is conveniently compiled and installed in one step. When `--without-perl` is specified, you must first install ImageMagick, change to the PerlMagick subdirectory, build, and finally install PerlMagick. Note, PerlMagick is configured even if `--without-perl` is specified. If `--enable-shared` is not specified, a new PERL interpreter (PerlMagick) is built which is statically linked against the PerlMagick extension. This new interpreter is installed alongside your existing PERL interpreter. If `--enable-shared` is specified, the PerlMagick extension is built as a dynamically loadable object which is loaded into your current PERL interpreter at run-time. Use of dynamically-loaded extensions is preferable over statically linked extensions so `--enable-shared` should be specified if possible. If the argument `--with-perl=/path/to/perl` is supplied, then `/path/to/perl` will be taken as the PERL interpreter to use.

- `--without-x`: By default, ImageMagick will use X11 libraries if they are available. When `--without-x` is specified, use of X11 is disabled. The display, animate, and import programs are not built or installed. The remaining programs have reduced functionality such as no access to X11 fonts (consider using Postscript or TrueType fonts instead).

Building under Cygwin:

ImageMagick may be built under the Windows NT/'9X Cygwin Unix-emulation environment which may be downloaded from Cygnus. Pre-compiled X11R6.4 libraries for Cygwin are available from NASA. Use the same procedure as for Unix except that building DLLs is not yet supported so do not specify `--enable-shared` option to configure.

Dealing with configuration failures:

While configure is designed to ease installation of ImageMagick, it often discovers problems that would otherwise be encountered later when compiling ImageMagick. The configure script tests for headers and libraries by executing the compiler (CC) with the specified compilation flags (CFLAGS), pre-processor flags (CPPFLAGS), and linker flags (LDFLAGS). Any errors are logged to the file `config.log`. If configure fails to discover a header or library please review this log file to determine why, however, please be aware that *errors in the config.log are normal* because configure works by trying something and seeing if it fails. An error in `config.log` is only a problem if the test should have worked on your system.. After taking corrective action, be sure to remove the `config.cache` file before running configure so that configure will re-inspect the environment rather than using cached values.

Common causes of configure falures are: 1) a delegate header is not in the header include path (CPPFLAGS -I option); 2) a delegate library is not in the linker search/run path (LDFLAGS -L/-R option); 3) a delegate library is missing a function (old version?); 4) compilation environment is faulty.

If all reasonable corrective actions have been tried and the problem appears to be due to a flaw in the configure script, please send a bug report to the configure script maintainer (currently bfriesenb@simple.dallas.tx.us). All bug reports should contain the operating system type (as reported by `uname -a`) and the compiler/compiler-version. A copy of the configure script output and/or the `config.log` file may be valuable in order to find the problem. If you send a `config.log`, please also send a script of the configure output and a description of what you expected to see (and why) so the failure you are observing can be identified and resolved.

- X11 Imake:

Use this option if working imake configuration files are available, the package is to be installed where ever imake installs things (usually the X11 distribution directory), and you don't mind editing a configuration file. Use of this scheme requires a seperate step to install PerlMagick (see the README file in the PerlMagick subdirectory).

Edit `Magick.tmpl` and set the variables to suit your local environment. Now type:

           ./confingure
           xmkmf
           make Makefiles

or just

           ./confingure
           xmkmf -a

If you are using X11R6 imake. Here, GNU configure is used to initialize the `delegates/delegates.mgk` file.

Note, ImageMagick requires an ANSI compiler. If the compile fails, first check to ensure your compile is ANSI compatible. If it fails for some other reason, try

          cd magick
          make -k
          cd ..
          make -k

  To confirm your build of the ImageMagick distribution was successful, type:

          display

  If the program faults make sure that you may have inadvertingly linked to an older version of the libMagick library. In this case type

          cd ImageMagick/magick
          make install
          cd ..
          make

If the image colors are not correct use this command

          display -visual default

  You can find other example images in the images directory.

For additional information, see the manual pages for these ImageMagick utilities

  display
  convert
  montage
  identify
  animate
  import
  mogrify
  combine

  Also read the ImageMagick Frequently Asked Questions This is a required reading. Most of the questions I get via electronic mail are answered in this document.

  Place display X application defaults in /usr/lib/X11/app-defaults/Display. Use the appropriate name for other clients (e.g. Animate, Montage, etc). To execute display from as a menu item of any window manager (olwm, mwm, twm, etc), use

        display logo:Untitled

Back to Contents

Delegates

  To further enhance the capabilities of ImageMagick, you may want to get these programs or libraries:

Background Texture

  ImageMagick requires a background texture for the TILE format and for the -texture option of montage. You can use your own or get samples or get additional samples from KPT.

BZLIB

  ImageMagick requires the BZLIB library to read or write Zip compressed MIFF images.

RALCGM

  ImageMagick requires ralcgm to read Computer Graphic Metafile images (may not compile under linux). You also need Ghostscript (see below).

TransFig

  ImageMagick requires fig2dev to read TransFig images.

GET

  ImageMagick requires GET to read images specified with a World Wide Web (WWW) uniform resource locator (URL). Note: do not confuse this get program with SCCS get program. If you do not have a HTTP server, you can use xtp, available in the ImageMagick distribution, for URL's whose protocol is FTP.

FPX

  ImageMagick requires the FlashPix SDK to read and write the FPX image format.

FreeType

  ImageMagick requires the FreeType software, version 1.1 or above, to annotate with TrueType fonts.

HDF

  ImageMagick requires the NCSA HDF library to read and write the HDF image format.

HTML2PS

  ImageMagick requires html2ps to read HyperText Markup Language (html) documents.

JBIG

  ImageMagick requires the JBIG-Kit software to read and write the JBIG image format.

JPEG

  ImageMagick requires the Independent JPEG Group's software to read and write the JPEG image format.
  Apply the lossless JPEG patch to Independent JPEG Group's source distribution to read lossless jpeg-encoded DICOM images:

Concerning iterative JPEG compression: see Kinoshita and Yamamuro, Journal of Imaging Science and Technology, Image Quality with Reiterative JPEG Compression, Volume 39, Number 4, July 1995, 306-312 who claim that (1) the iterative factor of the repetitive JPEG operation had no influence on image quality, and (2) the first compression determined base image quality.

MPEG

  ImageMagick requires the MPEG encoder / decoder to read or write the MPEG image format.

PNG

  ImageMagick requires the PNG library, version 1.0 or above, to read the PNG image format.

Postscript

  ImageMagick requires Ghostscript software to read the PostScript or the Portable Document format. It is used to annotate an image when an X server is not available. See the FreeType library above for another means to annotate an image. Note, Ghostscript must support the ppmraw device (type gs -h to verify). If Ghostscript is unavailable, the Display Postscript extension is used to rasterize a Postscript document (assuming you define HasDPS). The DPS extension is less robust than Ghostscript in that it will only rasterize one page of a multi-page document.

RA_PPM

  ImageMagick requires ra_ppm from Greg Ward's Radiance software to read the Radiance image format (may not compile under linux).

RAWTORLE

  ImageMagick requires rawtorle from the Utah Raster Toolkit to write the RLE image format (may not compile under linux)..

SANE

  ImageMagick requires scanimage to import images from a scanner device.

TIFF

  ImageMagick requires Sam Leffler's TIFF software to read and write the TIFF image format. It in turn optionally requires the JPEG and ZLIB libraries.

WMF

  ImageMagick requires wmftogif to read Windows Meta File images.

X Server

  ImageMagick requires an X server for display and animate to work properly. This free X server is available for Windows and Macintosh.

ZLIB

  ImageMagick requires the ZLIB library to read or write PNG or ZLIB compressed MIFF images.

Back to Contents

How to Compile

  The following procedure describes how to build ImageMagick extension libraries in subdirectories of the ImageMagick directory. An alternative to these procedures is to install one or more of these under your system's regular include/lib directory (e.g. the directory specified by `--prefix` to configure or `/usr/local`). This allows the libraries to be shared by other packages. When using the configure script, the two schemes may be mixed. Also, please note that when the configure option `--enable-shared` is not disabled, these procedures must be supplemented with whatever compilation flags are required on your system to generate PIC code. In the case of gcc, this usually means that `-fPIC` must be added to the compiler options (i.e. CFLAGS) when building each delegate library.
  To display images in the HDF, JPEG, PNG, TIFF or TTF format, get the respective archives and build ImageMagick as follows:

HDF

          cd ImageMagick
          gunzip -c HDF4.1r2.tar.gz | tar xvf -
          mv HDF4.1r2 hdf
          cd hdf
          configure
          make -k hdf-libnofortran
          cd ..

JBIG

          cd ImageMagick
          gunzip -c jbigkit-1.0.tar.gz | tar xvof -
          mv jbig-kit jbig
          cd jbig
          make
          cd ..

JPEG

          cd ImageMagick
          gunzip -c jpegsrc.v6b.tar.gz | tar xvof -
          mv jpeg-6b jpeg
          cd jpeg
          configure
          make
          cd ..

PNG

          cd ImageMagick
          gunzip -c libpng-1.0.3.tar.gz | tar xvf -
          mv libpng-1.0.3 png
          cd png
          make
          cd ..

TIFF

          cd ImageMagick
          gunzip -c tiff-v3.4beta037.tar.Z | tar xvof -
          mv tiff-v3.4beta037 tiff
          cd tiff
          ./configure
          make
          cd ..

TTF

          cd ImageMagick
          gunzip -c freetype-1.1.tar.gz | tar xvof -
          mv freetype-1.1 ttf
          cd ttf
          ./configure -disable-shared
          make
          cd ..

ZLIB

          cd ImageMagick
          gunzip -c zlib-1.1.3.tar.gz | tar xvf -
          mv zlib-1.1.3.tar.gz zlib
          cd zlib
          make
          cd ..

  If your computer system supports shared libraries you must type

          make install

  Finally, perform the following:

          cd ImageMagick
          edit Magick.tmpl and define Has???? as instructed
          xmkmf
          make Makefiles
          make clean
          make

  If prefer to use `configure` rather than Imake:

          configure
          make clean
          make -k

  If the compile fails due to a function redefinition it may be that either `jpeg/jconfig.h` or `mpeg/mpeg.h` is redefining `const`. Fix this problem and try again.

  You can now convert or display images in the JPEG, TIFF, PNG, etc. image formats.
  If you have HDF, JBIG, JPEG, PNG, and TIFF sources installed as directed above, you can also type

          Install sun

  Substitute the appropriate machine type (aix, hpux, sgi, etc).

Back to Contents

VMS Compilation

  You might want to check the values of certain program definitions before compiling. Verify the definitions in `delegates.mgk` to suit your local requirements. Next, type:

            unzip ImageMagick-4.2.9.zip
            set default [.imagemagick]
            @make
            set display/create/node=node_name::

  where node_name is the DECNET X server to contact.
Finally type:

            display

  Alternatively, get a zipped distribution (with JPEG, PNG, TIFF, and TTF) from ftp.wizards.dupont.com.
  The VMS JPEG, PNG, TIFF, and TTF source libraries are available on axp.psl.ku.dk in [anonymous.decwindows.lib].
  Thanks to pmoreau@cenaath.cena.dgac.fr for supplying invaluable help as well as the VMS versions of the JPEG, PNG, TIFF, and TTF libraries.

Back to Contents

NT Compilation

  The NT distribution contains MetroWerks Codewarrior Professional projects and a Visual C++ workspace (thanks to Bill Radcliffe) for compilation. For those who do not have access to CodeWarrior or Visual C++, the binaries for the command line utilities are enclosed.
  If you have an NT X server like Exceed you will also need to include

        SET DISPLAY=local-ip-address:0.0

  in the System Control panel (NT) or `Autoexec.bat` (Win95). `Autoexec.bat` requires that you restart your computer. See Technical Window System and OSF/Motif WWW Sites for a list of commercial and free X server software. Without an X server you can still display or animate to, or import from, a remote X server. Convert, mogrify, montage, combine, and identify, will work with or without an X server directly from the command prompt.
  To view any image in a Microsoft window, type

        convert image.ext win:

  Import works if you have at least one X window open. Alternatively, type

        convert x:root image.gif

  Make sure `gswin32` (Ghostscript) is in your execution path (see `Autoexec.bat`), otherwise, you will be unable to convert or view a Postscript document.

  Make sure `iexplore` (Internet Explorer) is in your execution path (see `Autoexec.bat`), otherwise, you will be unable to browse the ImageMagick documentation.

  To compile the source with Codewarrior, start with `Magick/Magick.mcp` and then `animate.mcp`, `convert.mcp`, etc.. The Visual C++ workspace is `ImageMagick.dsw`.

  And yes, the NT executables will work under Windows 95.

Back to Contents

Macintosh Compilation

  The Macintosh Macintosh distribution contains MetroWerks Codewarrior Professional projects for compilation. For those who do not have access to CodeWarrior, the binaries for the command line utilities are enclosed. I had to comment the inline intrinsic functions in `math.h` in order to compile. If you have a better solution, let me know. Display, animate, and import currently do not work on the Macintosh.

  I'm looking for a volunteer to get Display and animate to work on the Macintosh. I also need a volunteer is needed to write a simple Mac program to call the libMagick routines and display an image in a window.

Back to Contents

Animation

  To prevent color flashing on visuals that have colormaps, animate(1) creates a single colormap from the image sequence. This can be rather time consuming. You can speed this operation up by reducing the colors in the image before you animate them. Use mogrify to color reduce the images:

          mogrify +map -colors 256 scenes/dna.[0-9]*

Alternatively, you can use a Standard Colormap; or a static, direct, or true color visual. You can define a Standard Colormap with xstdcmap(1). For example, to use the "best" Standard Colormap, type:

          xstdcmap -best
          animate -map best scenes/dna.[0-9]*

  or to use a true color visual:

          animate -visual truecolor scenes/dna.[0-9]*

  Image filenames can appear in any order on the command line if the scene keyword is specified in the MIFF image. Otherwise the images display in the order they appear on the command line. A scene is specified when converting from another image format to MIFF by using the "scene" option with any filter. Be sure to choose a scene number other than zero. For example, to convert a TIFF image to a MIFF image as scene #2, type:

          convert -scene 2 image.tiff image.miff

Back to Contents

16-BIT Imaging

  By default, ImageMagick uses a color depth of 8 bits (e.g. [0..255] for each of red, green, blue, and transparency components). Any 16-bit image is scaled immediately to 8-bits before any image viewing or processing occurs. If you want to work directly with 16-bit images (e.g. [0..100535]), edit `Magick.tmpl` and define `QuantumLeap` or use `-enable-16bit` with configure. Next, type:

        make clean
        make

In 16-bit mode expect to use about 33% more memory on the average. Also expect some processing to be slower than in 8-bit mode (e.g. Oil Painting, Segment, etc).

In general, 16-bit mode is only useful if you have 16-bit images that you want to manipulate and save the transformed image back to a 16-bit image format (e.g. PNG, VIFF).

Back to Contents

64-BIT Machines

  Each pixel, within ImageMagick, is represented by the `RunlengthPacket` structure found in `magick/image.h`. Only 8 bits are required for each color component and 16 bits for the colormap index for a total of 6 bytes. If `QuantumLeap` is defined (see 16-BIT IMAGING above), the color component size increases to 16 bits for a total of 10 bytes. Some 64-bit machines pad the structure which can cause a significant waste of memory. For the cray, change the `RunlengthPacket` structure to this

        typedef struct _RunlengthPacket
        {
          unsigned char
            red : QuantumDepth,
            green : QuantumDepth,
            blue : QuantumDepth,
            length : QuantumDepth;

          unsigned short
            index : 16;
        } RunlengthPacket;

before compiling.

I'm not sure if this will work on other 64-bit machines that pad. If you know a better solution, please send me E-mail. Note, that the Dec Alpha apparently does not pad the structure so ImageMagick should be fine on this particular 64-bit machine.

Back to Contents

MIFF Image Format

  MIFF is an image format which I developed. I like it because

1. It is machine independent. It can be read on virtually any computer. No byte swapping is necessary.
2. It has a text header. Most image formats are coded in binary and you cannot easily tell attributes about the image. Use more(1) on MIFF image files and the attributes are displayed in text form.
3. It can handle runlength-encoded images. Although most scanned images do not benefit from runlength-encoding, most computer-generated images do. Images of mostly uniform colors have a high compression ratio and therefore take up less memory and disk space.
4. It allows a scene number to be specified. This allows you to specify an animation sequence out-of-order on the command line. The correct order is determined by the scene number of each image.
5. MIFF computes a digital signature for images. This is useful for comparing images. If two image files have the same signature, they are identical images.
6. There is a montage keyword allowing an image to act as a visual image directory. See display(1) for more details.

  One way to get an image into MIFF format is to use convert or read it from an X window using the import program. Alternatively, type the necessary header information in a file with a text editor. Next, dump the binary bytes into another file. Finally, type

          cat header binary_image | display -write image.miff -

  For example, suppose you have a raw red, green, blue image file on disk that is 640 by 480. The header file would look like this:

          id=ImageMagick columns=640 rows=480 :

  The image file would have red, green, blue tuples (rgbrgbrgb...). Refer to the display manual page for more details.

Back to Contents

Copyright

  Copyright 1999 E. I. du Pont de Nemours and Company

  Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files ("ImageMagick"), to deal in ImageMagick without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of ImageMagick, and to permit persons to whom the ImageMagick is furnished to do so, subject to the following conditions:

  The above copyright notice and this permission notice shall be included in all copies or substantial portions of ImageMagick.

  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 E. I. du Pont de Nemours and Company 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 ImageMagick or the use or other dealings in ImageMagick.

  Except as contained in this notice, the name of the E. I. du Pont de Nemours and Company shall not be used in advertising or otherwise to promote the sale, use or other dealings in ImageMagick without prior written authorization from the E. I. du Pont de Nemours and Company.

Image manipulation software that works like magic.