Initial revision

git-svn-id: http://svn.ghostscript.com/ghostpcl/trunk/ghostpcl@246 06663e23-700e-0410-b217-a244a6096597

7 files changed, 687 insertions, 0 deletions

diff --git a/gs/man/ansi2knr.1 b/gs/man/ansi2knr.1
new file mode 100644
index 000000000..f9ee5a631
--- /dev/null
+++ b/gs/man/ansi2knr.1
@@ -0,0 +1,36 @@
+.TH ANSI2KNR 1 "19 Jan 1996"
+.SH NAME
+ansi2knr \- convert ANSI C to Kernighan & Ritchie C
+.SH SYNOPSIS
+.I ansi2knr
+[--varargs] input_file [output_file]
+.SH DESCRIPTION
+If no output_file is supplied, output goes to stdout.
+.br
+There are no error messages.
+.sp
+.I ansi2knr
+recognizes function definitions by seeing a non-keyword identifier at the left
+margin, followed by a left parenthesis, with a right parenthesis as the last
+character on the line, and with a left brace as the first token on the
+following line (ignoring possible intervening comments).  It will recognize a
+multi-line header provided that no intervening line ends with a left or right
+brace or a semicolon.  These algorithms ignore whitespace and comments, except
+that the function name must be the first thing on the line.
+.sp
+The following constructs will confuse it:
+.br
+     - Any other construct that starts at the left margin and follows the
+above syntax (such as a macro or function call).
+.br
+     - Some macros that tinker with the syntax of the function header.
+.sp
+The --varargs switch is obsolete, and is recognized only for
+backwards compatibility.  The present version of
+.I ansi2knr
+will always attempt to convert a ... argument to va_alist and va_dcl.
+.SH AUTHOR
+L. Peter Deutsch <ghost@aladdin.com> wrote the original ansi2knr and
+continues to maintain the current version; most of the code in the current
+version is his work.  ansi2knr also includes contributions by Francois
+Pinard <pinard@iro.umontreal.ca> and Jim Avera <jima@netcom.com>.
diff --git a/gs/man/gs.1 b/gs/man/gs.1
new file mode 100644
index 000000000..e464a55ce
--- /dev/null
+++ b/gs/man/gs.1
@@ -0,0 +1,406 @@
+'\" t
+.\"- -*- nroff -*- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.\"
+.\"This file describes version 5.13 of Aladdin Ghostscript.
+.\"
+.\"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.de TQ
+.br
+.ns
+.TP \\$1
+..
+.TH GS 1 "27 April 1998"
+.SH NAME 
+gs \- Aladdin Ghostscript interpreter/previewer
+.SH SYNOPSIS
+.B gs
+[
+.I options
+] [
+.I files
+] ...
+.br
+.SH DESCRIPTION
+Ghostscript is an implementation of Adobe Systems'
+PostScript (tm) and Portable Document Format (PDF) languages.
+.I Gs
+reads
+.I files
+in sequence and executes them as Ghostscript programs.
+After doing this, it reads further input from the standard input stream
+(normally the keyboard).  Each line is interpreted separately.
+To exit from the interpreter, enter the `quit' command.
+The interpreter also exits gracefully if it encounters end-of-file.
+Typing the interrupt character (e.g. Control-C) is also safe.
+.PP
+The interpreter recognizes several switches described below, which may appear
+anywhere in the command line and apply to all files thereafter.
+.PP
+You can get a help message by invoking Ghostscript with the
+.B \-h
+or
+.B \-?
+option.  This message also lists the available devices.
+.PP
+Ghostscript may be built with multiple output devices.  Ghostscript
+normally opens the first one and directs output to it.  To use device xyz
+as the initial output device, include the switch
+.nf
+	\-sDEVICE=xyz
+.fi
+in the command line.  Note that this switch must precede the first .ps
+file, and only its first invocation has any effect.  For example, for
+printer output in a normal configuration that includes an Epson printer
+driver, you might use the shell command
+.nf
+	gs \-sDEVICE=epson myfile.ps
+.fi
+instead of just
+.nf
+	gs myfile.ps
+.fi
+Alternatively, you can type
+.nf
+	(epson) selectdevice
+	(myfile.ps) run
+.fi
+All output then goes to the printer instead of the display until further
+notice.  You can switch devices at any time by using the selectdevice
+procedure, e.g.,
+.nf
+	(vga) selectdevice
+.fi
+or
+.nf
+	(epson) selectdevice
+.fi
+As yet a third alternative, you can define an environment variable
+GS_DEVICE as the desired default device name.  The order of precedence for
+these alternatives, highest to lowest, is:
+.nf
+	selectdevice
+	(command line)
+	GS_DEVICE
+	(first device in build list)
+.fi
+.PP
+To select the density on a printer, use
+.nf
+	gs \-sDEVICE=<device> \-r<xres>x<yres>
+.fi
+For example, on a 9-pin Epson-compatible printer, you can get the
+lowest-density (fastest) mode with
+.nf
+	gs \-sDEVICE=epson \-r60x72
+.fi
+and the highest-density mode with
+.nf
+	gs \-sDEVICE=epson \-r240x72.
+.fi
+.PP
+If you select a printer as the output device, Ghostscript also allows you
+to control where the device sends its output.  Normally, output goes
+directly to a scratch file on Unix systems.
+To send the output to a series of files foo1.xyz,
+foo2.xyz, ..., use the switch
+.nf
+	\-sOutputFile=foo%d.xyz
+.fi
+The %d is a printf format specification; you can use
+other formats like %02d.  Each file will receive one page of output.
+Alternatively, to send the output to a single file foo.xyz, with all
+the pages concatenated, use the switch
+.nf
+	\-sOutputFile=foo.xyz
+.fi
+.PP
+On Unix systems, you can send the output directly to a pipe.  For
+example, to pipe the output to the command `lpr' (which, on many Unix
+systems, is the command that spools output for a printer), use the
+switch
+.nf
+	\-sOutputFile=\\|lpr
+.fi
+You can also send output to stdout for piping with the switch
+.nf
+	\-sOutputFile=\-
+.fi
+In this case you must also use the \-q switch, to prevent Ghostscript from
+writing messages to stdout.
+.PP
+To find out what devices are available, type
+.nf
+	devicenames ==
+.fi
+after starting up Ghostscript.
+Alternatively, you can use the \-h or \-? switch in the command line;
+the help message also lists the available devices.
+.PP
+To select a different paper size, use the command line switch
+.nf
+        -sPAPERSIZE=a_known_paper_size
+.fi
+e.g.,
+.nf
+        -sPAPERSIZE=a4
+.fi
+or
+.nf
+        -sPAPERSIZE=legal
+.fi
+As of this printing, the known paper sizes, defined in gs_statd.ps, are:
+.TS
+tab(>);
+l l l l l.
+.sp
+PAPERSIZE>X">Y">X cm>Y cm
+_
+11x17>11">17">27.94>43.18
+a0>33.0556">46.7778">83.9611>118.816
+a10>1.02778">1.45833">2.61056>3.70417
+a1>23.3889">33.0556">59.4078>83.9611
+a2>16.5278">23.3889">41.9806>59.4078
+a3>11.6944">16.5278">29.7039>41.9806
+a4>8.26389">11.6944">20.9903>29.7039
+a5>5.84722">8.26389">14.8519>20.9903
+a6>4.125">5.84722">10.4775>14.8519
+a7>2.91667">4.125">7.40833>10.4775
+a8>2.05556">2.91667">5.22111>7.40833
+a9>1.45833">2.05556">3.70417>5.22111
+archA>9">12">22.86>30.48
+archB>12">18">30.48>45.72
+archC>18">24">45.72>60.96
+archD>24">36">60.96>91.44
+archE>36">48">91.44>121.92
+b0>39.3889">55.6667">100.048>141.393
+b1>27.8333">39.3889">70.6967>100.048
+b2>19.6944">27.8333">50.0239>70.6967
+b3>13.9167">19.6944">35.3483>50.0239
+b4>9.84722">13.9167">25.0119>35.3483
+b5>6.95833">9.84722">17.6742>25.0119
+flsa>8.5">13">21.59>33.02
+flse>8.5">13">21.59>33.02
+halfletter>5.5">8.5">13.97>21.59
+ledger>17">11">43.18>27.94
+legal>8.5">14">21.59>35.56
+letter>8.5">11">21.59>27.94
+note>7.5">10">19.05>25.4
+.TE
+.SH "INITIALIZATION FILES"
+When looking for the initialization files (gs_*.ps), the files related
+to fonts, or the file for the `run' operator, Ghostscript first tries
+opening the file with the name as given (i.e., using the current
+working directory if none is specified).  If this fails, and the file
+name doesn't specify an explicit directory or drive (i.e., doesn't
+begin with `/' on Unix systems), Ghostscript will try directories in the
+following order:
+.TP
+1.
+The directory/ies specified by the \-I switch(es) in the command
+line (see below), if any;
+.TP
+2.
+The directory/ies specified by the GS_LIB environment variable,
+if any;
+.TP
+3.
+The directory/ies specified by the GS_LIB_DEFAULT macro in the
+Ghostscript makefile (which has been set to
+"/usr/local/share/ghostscript/M.N:/usr/local/share/ghostscript/fonts"
+where M.N is the Ghostscript version number).
+.PP
+Each of these (GS_LIB_DEFAULT, GS_LIB, and \-I parameter) may be either
+a single directory, or a list of directories separated by a `:'.
+.SH X RESOURCES
+Ghostscript looks for the following resources under the program name
+`Ghostscript':
+.TP
+.B borderWidth
+The border width in pixels (default = 1).
+.TP
+.B borderColor
+The name of the border color (default = black).
+.TP
+.B geometry 
+The window size and placement, WxH+X+Y (default is NULL).
+.TP
+.B xResolution 
+The number of x pixels per inch (default is computed from WidthOfScreen
+and WidthMMOfScreen).
+.TP
+.B yResolution
+The number of y pixels per inch (default is computed from
+HeightOfScreen and HeightMMOfScreen).
+.TP
+.B useBackingPixmap
+Determines whether backing store is to be used for saving display window
+(default = true).
+.PP
+See the file `use.txt' for a more complete list of resources.
+.PP
+To set these resources, put them in a file (such as ~/.Xresources) in the
+following form:
+.sp
+.nf
+	Ghostscript*geometry:	612x792\-0+0
+	Ghostscript*xResolution: 72
+	Ghostscript*yResolution: 72
+.fi
+.PP
+Then load the defaults into the X server:
+.sp
+.nf
+	% xrdb \-merge ~/.Xresources
+.fi
+.SH OPTIONS
+.TP
+.BI \-\- " filename arg1 ..."
+Takes the next argument as a file name as usual, but takes all
+remaining arguments (even if they have the syntactic form of switches)
+and defines the name ARGUMENTS in userdict (not systemdict) as an
+array of those strings, 
+.I before
+running the file.  When Ghostscript
+finishes executing the file, it exits back to the shell.
+.TP
+.BI \-D name = token
+.TQ
+.BI \-d name = token
+Define a name in systemdict with the given definition.  The token must
+be exactly one token (as defined by the `token' operator) and must not
+contain any whitespace.
+.TP
+.BI \-D name
+.TQ
+.BI \-d name 
+Define a name in systemdict with value=null.
+.TP
+.BI \-S name = string
+.TQ
+.BI \-s name = string
+Define a name in systemdict with a given string as value.  This is
+different from \-d.  For example, \-dname=35 is equivalent to the
+program fragment
+.br
+			/name 35 def 
+.br
+whereas 
+\-s name=35 is equivalent to
+.br
+			/name (35) def
+.TP
+.B \-q
+Quiet startup \- suppress normal startup messages, and also do the
+equivalent of \-dQUIET.
+.TP
+.BI \-g number1 x number2
+Equivalent to
+.BI \-dDEVICEWIDTH= number1 
+and
+.BI \-dDEVICEHEIGHT= number2 .
+This is for the benefit of devices (such as X11 windows)
+that require (or allow) width and height to be specified.
+.TP
+.BI \-r number
+.TQ
+.BI \-r number1 x number2
+Equivalent to
+.BI \-dDEVICEXRESOLUTION= number1 
+and
+.BI \-dDEVICEYRESOLUTION= number2 .
+This is for the benefit of devices (such as printers)
+that support multiple X and Y resolutions.
+(If only one number is given, it is used for both X and Y resolutions.)
+.TP
+.BI \-I directories
+Adds the designated list of directories at the head of the
+search path for library files.
+.TP
+.B \-
+This is not really a switch.  It indicates to Ghostscript that the
+standard input is coming from a file or a pipe.  Ghostscript reads
+from stdin until reaching end-of-file, executing it like any other
+file, and then continues processing the command line.  At the end of
+the command line, Ghostscript exits rather than going into its
+interactive mode.
+.PP
+Note that gs_init.ps makes systemdict read-only, so the values of names
+defined with \-D/d/S/s cannot be changed (although, of course, they can be
+superseded by definitions in userdict or other dictionaries.)
+.SH "SPECIAL NAMES"
+.TP
+.B \-dDISKFONTS
+Causes individual character outlines to be loaded from the disk
+the first time they are encountered.  (Normally Ghostscript loads all the
+character outlines when it loads a font.)  This may allow loading more
+fonts into RAM, at the expense of slower rendering.
+.TP
+.B \-dNOCACHE
+Disables character caching.  Only useful for debugging.
+.TP
+.B \-dNOBIND
+Disables the `bind' operator.  Only useful for debugging.
+.TP
+.B \-dNODISPLAY
+Suppresses the normal initialization of the output device.
+This may be useful when debugging.
+.TP
+.B \-dNOPAUSE
+Disables the prompt and pause at the end of each page.
+This may be desirable for applications where another program is
+`driving' Ghostscript.
+.TP
+.B \-dNOPLATFONTS
+Disables the use of fonts supplied by the underlying platform
+(e.g. X Windows).  This may be needed if the platform
+fonts look undesirably different from the scalable fonts.
+.TP
+.B \-dSAFER
+Disables the deletefile and renamefile operators, and the
+ability to open files in any mode other than read-only.  This may be
+desirable for spoolers or other sensitive environments.
+.TP
+.B \-dWRITESYSTEMDICT
+Leaves systemdict writable.  This is necessary when running
+special utility programs such as font2c and pcharstr, which must bypass
+normal PostScript access protection.
+.TP
+.BI \-sDEVICE= device
+Selects an alternate initial output device, as described above.
+.TP
+.BI \-sOutputFile= filename
+Selects an alternate output file (or pipe) for the initial output
+device, as described above.
+.SH FILES
+.TP 
+.B /usr/local/share/ghostscript/M.N/*
+Startup-files, utilities, and basic font definitions.
+.TP 
+.B /usr/local/share/ghostscript/fonts/*
+Additional font definitions.
+.TP
+.B /usr/local/share/ghostscript/M.N/examples/*
+Demo Ghostscript files.
+.TP
+.B /usr/local/share/ghostscript/M.N/doc/*
+Assorted document files.
+.SH ENVIRONMENT
+.TP
+.B GS_OPTIONS
+String of options to be processed before the command line options.
+.TP
+.B GS_DEVICE
+Used to define the device used.
+.TP
+.B GS_FONTPATH
+Path names used to search for fonts
+.TP
+.B GS_LIB
+Path names for initialization files and fonts
+.TP
+.B  TEMP
+Where temporary files are made
+.SH "SEE ALSO"
+The various Ghostscript document files (above).
+.SH BUGS
+See the network news group `comp.lang.postscript'.
diff --git a/gs/man/pdf2dsc.1 b/gs/man/pdf2dsc.1
new file mode 100644
index 000000000..2003b0b78
--- /dev/null
+++ b/gs/man/pdf2dsc.1
@@ -0,0 +1,52 @@
+.\" pdf2dsc.1: short documentation for pdf2dsc
+.\" Yves Arrouye <arrouye@debian.org>
+.TH PDF2DSC 1 "25 July 1996" "Ghostscript 4" "Ghostscript Tools"
+.SH NAME 
+.B pdf2dsc
+\- generate a PS page list of a PDF document
+.SH SYNOPSIS
+.B pdf2dsc
+.I pdffile
+[
+.I dscfile
+]
+.SH DESCRIPTION
+.B pdf2dsc
+reads a Portable Document Format (PDF) document 
+.I pdffile
+and creates a PostScript document
+.I dscfile
+that conforms to Adobe's Document Structuring Conventions (DSC)
+requirements.
+This new document simply tells Ghostscript to read the PDF file and to
+display pages one at a time.
+.PP
+The generated document can then be viewed with any PostScript viewer
+based on Ghostscript, like
+.BR ghostview (1)
+or
+.BR GSView ,
+which will let the user browse through the pages of the PDF document
+in any order.
+.PP
+If the output document name
+.I dscfile
+is not given on the command line, the name used is
+.I pdffile
+with any extension removed, followed by a
+.B .dsc
+extension.
+.SH CAVEATS
+The DSC document uses Ghostscript-specific procedures.
+In addition, the original PDF document must be accessible when the
+DSC document is read.
+.PP
+You need the
+.B pdf2dsc.ps
+file (originally by Russell Lang) that comes with Ghostscript releases
+3.53 and higher and a corresponding Ghostscript interpreter.
+.SH DOCUMENTATION
+Yves Arrouye <arrouye@debian.org>
+.SH SEE ALSO
+.BR gs (1),
+.BR ghostview (1)
diff --git a/gs/man/pdf2ps.1 b/gs/man/pdf2ps.1
new file mode 100644
index 000000000..a95169c53
--- /dev/null
+++ b/gs/man/pdf2ps.1
@@ -0,0 +1,21 @@
+.\"- -*- nroff -*- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.\"
+.\"This file describes version 5.03 of Aladdin pdf2ps.
+.\"
+.\"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.de TQ
+.br
+.ns
+.TP \\$1
+..
+.TH pdf2ps 1 "10 November 1997"
+.SH NAME 
+pdf2ps \- Aladdin Ghostscript PDF to PostScript translator
+.SH SYNOPSIS
+.B pdf2ps input.pdf output.ps
+.br
+.SH DESCRIPTION
+pdf2ps converts the Adobe Portable Document Format (PDF) file input.pdf to
+Level 2 PostScript in output.ps.  pdf2ps uses gs(1).  See
+/usr/local/lib/ghostscript/M.N/doc/use.txt for more details,
+where M.N is the Ghostscript version number.
diff --git a/gs/man/ps2ascii.1 b/gs/man/ps2ascii.1
new file mode 100644
index 000000000..eb0993456
--- /dev/null
+++ b/gs/man/ps2ascii.1
@@ -0,0 +1,37 @@
+.\"- -*- nroff -*- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.\"
+.\"This file describes version 4.0 of Aladdin ps2ascii.
+.\"
+.\"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.de TQ
+.br
+.ns
+.TP \\$1
+..
+.TH ps2ascii 1 "20 June 1996"
+.SH NAME 
+ps2ascii \- Aladdin Ghostscript PostScript or PDF to ASCII translator
+.SH SYNOPSIS
+.B ps2ascii [input.ps [output.txt]]
+.br
+.B ps2ascii input.pdf [output.txt]
+.br
+.SH DESCRIPTION
+
+ps2ascii extracts ASCII text from PostScript or PDF, using gs(1). If the
+pathname "input.ps" is not specified, PostScript is read from standard input;
+PDF input must come from an explicitly-named file, not standard input.  If the
+pathname "output.txt" is not specified, the ASCII text is written to standard
+output.
+
+ps2ascii doesn't look at font encoding, and isn't very good at dealing with
+kerning, so for dealing with PostScript (but not currently PDF), you might
+consider pstotext(1).
+
+.SH SEE ALSO
+
+.B pstotext(1)
+
+.SH AUTHOR OF DOCUMENTATION
+
+.B Paul McJones <mcjones@pa.dec.com>
diff --git a/gs/man/ps2epsi.1 b/gs/man/ps2epsi.1
new file mode 100644
index 000000000..a0f5b9270
--- /dev/null
+++ b/gs/man/ps2epsi.1
@@ -0,0 +1,100 @@
+.TH ps2epsi 1 "September 1, 1997"
+.SH NAME
+ps2epsi \- generate conforming postscript
+
+.SH SYNOPSIS
+.B ps2epsi 
+.I infile.ps
+[
+.I outfile.ps
+]    (Unix)
+.br
+.B ps2epsi
+.I infile.ps outfile.epi
+        (MS-DOS)
+
+.SH DESCRIPTION
+.B ps2epsi 
+is a utility, based on
+.I Ghostscript,
+which takes as input a postscript 
+file and generates a new output file which conforms to Adobe's
+.I Encapsulated  Postscript Interchange
+or EPSI format.  This is a
+special form of encapsulated  postscript (EPS) which adds a bitmap
+version of the final displayed page (in  the form of postscript
+comments) to the beginning of the file. This bitmap  can be used by
+programs which understand EPSI (usually word processors or  DTP
+programs) to give a preview version of the postscript on screen. The
+displayed quality is often not very good (eg. low resolution, no
+colours),  but the final printed version uses the real postscript,
+and thus has the normal postscript quality. 
+
+.SH OPTIONS
+None.
+
+.SH UNIX USAGE
+Using the supplied shell script, the command is:
+.br
+	ps2epsi
+.I infile.ps
+[ 
+.I outfile.epsi
+]
+.br
+where
+.I infile.ps
+is the input file and
+.I outfile.epsi
+is the output EPSI file. If the output filename is omitted, it will
+be generated from the input filename.
+If a standard extension (.ps, .cps, .eps or .epsf) is 
+used, it will be replaced with the output extension .epsi.
+
+.SH MSDOS USAGE
+Using the supplied batch file, the command is simply:
+.br
+	ps2epsi
+.I infile.ps outfile.epi
+.br
+where
+.I infile.ps
+is the original postscript file, and
+.I outfile.epi
+is the name of the output file.
+
+.SH LIMITATIONS
+Successful encapsulation of arbitrary postscript files cannot be
+guaranteed, as there are certain restrictions in what is permitted in
+a postscript file for it to be properly encapsulated.
+.B ps2epsi
+does a little extra work to try to help encapsulation, and it automatically
+calculates the bounding box (required for all encapsulated postscript
+files), so, most of the time, it does a pretty good job. There are
+bound to be cases, however, where the encapsulation will not work,
+because of the content of the original postscript file.
+
+.SH FRAMEMAKER
+The
+.I Framemaker
+DTP system is one application which understands EPSI
+files, and
+.B ps2epsi
+has been tested on a number of postscript diagrams
+from a variety of sources, using Framemaker 3.0 on a Sun.
+.I Framemaker
+on other platforms should be able to use these files,
+although I have not been able to test this.
+
+.SH FILES
+.nf
+ps2epsi.bat	- MSDOS batch file
+ps2epsi		- Unix shell script
+ps2epsi.ps	- the Ghostscript program which does the work
+.fi
+
+.SH "SEE ALSO"
+gs(1)
+
+.SH AUTHOR
+George Cameron <george@bio-medical-physics.aberdeen.ac.uk>
diff --git a/gs/man/ps2pdf.1 b/gs/man/ps2pdf.1
new file mode 100644
index 000000000..ee9597528
--- /dev/null
+++ b/gs/man/ps2pdf.1
@@ -0,0 +1,35 @@
+.\"- -*- nroff -*- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.\"
+.\"This file describes version 4.0 of Aladdin ps2pdf.
+.\"
+.\"- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+.de TQ
+.br
+.ns
+.TP \\$1
+..
+.TH ps2pdf 1 "19 June 1996"
+.SH NAME 
+ps2pdf \- Aladdin Ghostscript PostScript to PDF translator
+.SH SYNOPSIS
+.B ps2pdf input.ps output.pdf
+.br
+.SH DESCRIPTION
+
+ps2pdf converts the PostScript file input.ps to the Adobe Portable
+Document Format (PDF) in output.pdf.  ps2pdf uses gs(1).  See
+/usr/local/lib/ghostscript/M.N/doc/use.doc for more details,
+where M.N is the Ghostscript version number.
+
+Currently ps2pdf does a reasonable job on filled/stroked graphics, on bitmap
+images, and on text in the 14 built-in PDF fonts in the intersection of
+Windows and ISO Latin-1 encodings.  It converts all other text in the
+PostScript file to bitmaps in the PDF file (although it does only write the
+bitmap for each character once per page, and only on pages where the
+character is actually used).  It does not compress the output at all, except
+for character bitmaps: it can't use LZW because of Unisys' patent claims,
+and it doesn't yet use other compression methods for images.
+
+.SH AUTHOR OF DOCUMENTATION
+
+.B L. Peter Deutsch <ghost@aladdin.com>