Adding upstream version 4.22.0.upstream/4.22.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 75 insertions, 0 deletions

diff --git a/upstream/debian-unstable/man1/lispmtopgm.1 b/upstream/debian-unstable/man1/lispmtopgm.1
new file mode 100644
index 00000000..3ab97a01
--- /dev/null
+++ b/upstream/debian-unstable/man1/lispmtopgm.1
@@ -0,0 +1,75 @@
+\
+.\" This man page was generated by the Netpbm tool 'makeman' from HTML source.
+.\" Do not hand-hack it!  If you have bug fixes or improvements, please find
+.\" the corresponding HTML page on the Netpbm website, generate a patch
+.\" against that, and send it to the Netpbm maintainer.
+.TH "Lispmtopgm User Manual" 1 "06 March 1990" "netpbm documentation"
+
+.SH NAME
+lispmtopgm - convert a Lisp Machine bitmap file to PGM
+
+.UN synopsis
+.SH SYNOPSIS
+
+\fBlispmtopgm\fP
+[\fIlispmfile\fP]
+
+.UN description
+.SH DESCRIPTION
+.PP
+This program is part of
+.BR "Netpbm" (1)\c
+\&.
+.PP
+\fBlistpmfile\fP reads a Lisp Machine bitmap as input and
+produces a PGM image as output.
+.PP
+This is the file format written by the tv:write-bit-array-file
+function on TI Explorer and Symbolics lisp machines.
+.PP
+Multi-plane bitmaps on lisp machines are color; but the Lispm image
+file format does not include a color map, so we must treat it as a
+monochrome instead and produce PGM.  This is unfortunate.
+
+.UN options
+.SH OPTIONS
+.PP
+There are no command line options defined specifically
+for \fBlispmtopgm\fP, but it recognizes the options common to all
+programs based on libnetpbm (See 
+.UR index.html#commonoptions
+ Common Options
+.UE
+\&.)
+
+.UN seealso
+.SH SEE ALSO
+.BR "pgmtolispm" (1)\c
+\&,
+.BR "pgm" (1)\c
+\&
+
+.UN limitations
+.SH LIMITATIONS
+
+The Lispm bitmap file format is a bit quirky;  Usually the image in the file
+has its width rounded up to the next higher multiple of 32, but not always.
+If the width is not a multiple of 32, we don't deal with it properly, but 
+because of the Lispm microcode, such arrays are probably not image data 
+anyway.
+.PP
+Also, the Lispm code for saving bitmaps has a bug, in that if you
+are writing a bitmap which is not mod32 across, the file may be up to
+7 bits too short!  They round down instead of up, and we don't handle
+this bug gracefully.
+
+.UN author
+.SH AUTHOR
+.PP
+Copyright (C) 1991 by Jamie Zawinski and Jef Poskanzer.
+.SH DOCUMENT SOURCE
+This manual page was generated by the Netpbm tool 'makeman' from HTML
+source.  The master documentation is at
+.IP
+.B http://netpbm.sourceforge.net/doc/lispmtopgm.html
+.PP
\ No newline at end of file