1 files changed, 108 insertions, 0 deletions
diff --git a/upstream/opensuse-leap-15-6/man1/pamstack.1 b/upstream/opensuse-leap-15-6/man1/pamstack.1
new file mode 100644
index 00000000..c05ae513
--- /dev/null
+++ b/upstream/opensuse-leap-15-6/man1/pamstack.1
@@ -0,0 +1,108 @@
+\
+.\" 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 "Pamstack User Manual" 0 "10 January 2006" "netpbm documentation"
+
+.UN name
+.SH NAME
+
+pamstack - stack planes of multiple PAM images into one PAM image
+
+.UN synopsis
+.SH SYNOPSIS
+
+\fBpamstack\fP
+[\fB-tupletype \fP\fItupletype\fP]
+[\fIinputfilespec\fP ...]
+.PP
+All options may be abbreviated to the shortest unique prefix.  You
+may use two hyphens instead of one.  You may separate an option from
+its value with a space instead of \fB=\fP.
+
+.UN description
+.SH DESCRIPTION
+.PP
+This program is part of
+.BR "Netpbm" (1)\c
+\&.
+.PP
+\fBpamstack\fP reads multiple PAM or PNM images as input and
+produces a PAM image as output, consisting of all the planes
+(channels) of the inputs, stacked in the order specified.
+.PP
+For any one (but not more) of the input files, you may specify
+"-" to mean Standard Input.  If you specify no arguments at all,
+the input is one file: Standard Input.
+.PP
+The output is the same dimensions as the inputs, except that the
+depth is the sum of the depths of the inputs.  It has the same maxval.
+\fBpamstack\fP fails if the inputs are not all the same width, height,
+and maxval.  The tuple type is a null string unless you specify the
+\fB-tupletype\fP option.
+.PP
+\fBpamstack\fP works with multi-image streams.  It stacks the 1st
+image in all the streams into one output image (the first one in the
+output stream), then stacks the 2nd image in all the streams into the
+2nd image in the output stream, and so on, until one of the streams
+runs dry.  It's like a matrix operation.
+.PP
+Before Netpbm 10.32 (February 2006), \fBpamstack\fP ignored all but
+the first image in each input stream.
+.PP
+\fBpamchannel\fP does the opposite of \fBpamstack\fP:  It extracts
+individual planes from a single PAM.
+.PP
+Use
+.BR "pamtopnm" (1)\c
+\& to convert a suitable PAM
+image to a more traditional PNM (PBM, PGM, or PPM) image.  (But there's
+no need to do that if you're going to feed it to a modern Netpbm program --
+they all take suitable PAM input directly).
+.PP
+One example of using \fBpamstack\fP is that some Netpbm programs
+accept as input a PAM that represents graphic image with transparency
+information.  Taking a color image for example, this would be a PAM
+with tuple type "RGB_ALPHA".  In Netpbm, such images were
+traditionally represented as two images - a PPM for the color and a
+PGM for the transparency.  To convert a PPM/PGM pair into
+PAM(RGB_ALPHA) input that newer programs require, do something like
+this:
+
+.nf
+\f(CW
+$ pamstack -tupletype=RGB_ALPHA myimage.ppm myalpha.pgm | \e
+      pamtouil >myimage.uil
+\fP
+.fi
+
+.UN options
+.SH OPTIONS
+
+
+
+.TP
+\fB-tupletype \fP\fItupletype\fP
+This specifies the tuple type name to be recorded in the output.  You may
+use any string up to 255 characters.  Some programs recognize some names.
+If you omit this option, the default tuple type name is null.
+
+
+.UN seealso
+.SH SEE ALSO
+.BR "pam" (5)\c
+\&
+.BR "pamchannel" (1)\c
+\&
+
+.UN history
+.SH HISTORY
+.PP
+\fBpamstack\fP was new in Netpbm 10.0 (June 2002).
+.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/pamstack.html
+.PP
+\ No newline at end of file