The Ghostscript support module has been tested with the
  Ghostscript 3.53 and 4.03 ports from Aminet, with amiga driver
  & no ixemul.library: Aladdin Ghostscript is Copyright
  (C) 1989, 1995 Aladdin Enterprises. All rights reserved.

  Recommended is V5.01, Ghostscript 2.6.1 may work, if you don't
  use PNG as output file format.

  At first, Ghostscript must have been successfully installed,
  and working (test it via command line access).

  For enabling Ghostscript support, you either have to supply
  an AmigaDOS search path to a directory, where the executable
  "gs000" is stored (default), or explicitely specify path and/or
  name of the program by the controlpad entry GS_PATH (see below).

  But as mentioned before, Ghostscript has to be installed and set-up first.


  Setting-up Ghostscript
  ~~~~~~~~~~~~~~~~~~~~~~
  Since the documentation of some Ghostscript versions is anything-but-not-
  very-verbose I decided, to shortly explain here, what steps to
  perform to successfully install Ghostscript on your system:

      - unpack Ghostscript to where you wish it to be located at
        (e.g. "Work:Ghostscript/")
      - make an assign "Ghostscript:" to that Ghostscript directory
        (e.g. put the line "Assign Ghostscript: Work:Ghostscript"
         into your "S:User-Startup")
      - assign PSFonts: to your postscript font directory (anywhere)
        (e.g. put the line "Assign PSFonts: Work:Ghostscript/Fonts"
         into your "S:User-Startup", if that font directory already
         does exist there)
      - create some environment variables in ENV: _and_ ENVARC: which have
        to look as follows (respecting upper and lowercase):

           Variable          Content        Remark

           GS_FONTPATH                      *NOT* to be created (do delete)
           GS_LIB            PSFonts:
           GS_OPTIONS                       create, but leave *EMPTY* (blank)
           GS_DEVICE         amiga

      - create a file "PSFonts:FONTMAP" with at least the following lines:


% fontmap aka Fontmap
% ----------------------------------------------------------------
/Times-Roman                    (ptmr.gsf)      ;
/Times-Italic                   (ptmri.gsf)     ;
/Times-Bold                     (ptmb.gsf)      ;
/Times-BoldItalic               (ptmbi.gsf)     ;


    The single ps fonts are assigned via the FONTMAP. For fonts used by ps
    files there must be an entry to allow interpretation of these files, but
    basically each font can easily substituted by an other.

    It does not matter, which font files are assigned for which fontname;
    in general entries within the FONTMAP file at "PSFonts:" just have to
    go conformeous with the following scheme:

          /Fontname             (Filename)      ;

    for example

          /Helvetica            (Helvet.pfb)    ;

    This means that the corresponding files must actually exist.
    But one also may substitute fonts symbolically by other fonts
    (to be understood like an alias or replacement font as known
    from Windows (TM) for "Arial" and "Helvetica") like for example:

          /Helvetica_Bold       /Helvetica      ;


  Remarks
  ~~~~~~~
   - if special versions for specific CPUs do crash, then try versions
     for "smaller" CPUs (e.g. 68000 version instead of 040+FPU version).
   - please note, that setting DPI to higher values does not necessarily
     increase image quality, but memory usage (default is DPI=72).
     Same is to mention for the output colordepth:
     256 colors give better results, when you've to perform dithering.
   - files to be recognized must either have the standard Postscript (TM)
     header (containing '%!PS-Adobe' in it) or have the file extension
     ".ps" and begin with '%' (containing instructions for GhostScript).
   - PDF files are also supported (extension ".pdf" and beginning with '%'),
     but having the correct and needed fonts installed is more critical
     for these. Had not enough fonts to successfully test loading of any
     of these.
   - error output of Ghostscript still is directed to stdio/Output(),
     so problems may be visible transparently