summaryrefslogtreecommitdiffstats
path: root/upstream/mageia-cauldron/man1/pamchannel.1
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/mageia-cauldron/man1/pamchannel.1')
-rw-r--r--upstream/mageia-cauldron/man1/pamchannel.196
1 files changed, 96 insertions, 0 deletions
diff --git a/upstream/mageia-cauldron/man1/pamchannel.1 b/upstream/mageia-cauldron/man1/pamchannel.1
new file mode 100644
index 00000000..efc36a39
--- /dev/null
+++ b/upstream/mageia-cauldron/man1/pamchannel.1
@@ -0,0 +1,96 @@
+\
+.\" 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 "Pamchannel User Manual" 0 "10 January 2006" "netpbm documentation"
+
+.SH NAME
+pamchannel - extract channels from a PAM image
+
+.UN synopsis
+.SH SYNOPSIS
+
+\fBpamchannel\fP
+[\fB-infile=\fP\fIinfile\fP]
+[\fB-tupletype=\fP\fItupletype\fP]
+[\fIchannum\fP ...]
+.PP
+Minimum unique abbreviation of option is acceptable. You may use double
+hyphens instead of single hyphen to denote options. You may use white
+space in place of the equals sign to separate an option name from its value.
+
+.UN description
+.SH DESCRIPTION
+.PP
+This program is part of
+.BR "Netpbm" (1)\c
+\&.
+.PP
+\fBpamchannel\fP reads a Netpbm image as input and produces a
+PAM image as output, consisting of the indicated channels (planes) of
+the input.
+.PP
+Each \fIchannum\fP argument is the number of a channel of the input,
+with the first channel being zero. The channels in the output are in the
+order of these arguments.
+.PP
+The output is the same dimensions as the input, except that the depth
+is the number of \fIchannum\fP arguments you supply. The tuple type
+is a null string unless you specify the \fB-tupletype\fP option.
+.PP
+This program works on multi-image streams, producing a
+corresponding output stream. But before Netpbm 10.32 (February 2006),
+it ignored every image after the first.
+.PP
+\fBpamstack\fP does the opposite of \fBpamchannel\fP: It takes multiple
+PAM or PNM images as input and stacks their planes (channels) on top of
+one another to yield a single PAM.
+
+.UN options
+.SH OPTIONS
+.PP
+In addition to the options common to all programs based on libnetpbm
+(most notably \fB-quiet\fP, see
+.UR index.html#commonoptions
+ Common Options
+.UE
+\&), \fBpamchannel\fP recognizes the following
+command line options:
+
+
+
+.TP
+\fB-infile\fP \fIinfile\fP
+This specifies the input file, which defaults to Standard Input. You
+may specify \fB-\fP to select Standard Input explicitly.
+.sp
+This is a little unconventional for Netpbm programs, which usually
+have the input file specification as an argument. For \fBpamchannel\fP,
+the arguments are channel numbers.
+
+.TP
+\fB-tupletype\fP \fItupletype\fP
+This specified 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" (1)\c
+\&
+.BR "pamstack" (1)\c
+\&
+
+.UN history
+.SH HISTORY
+.PP
+\fBpamchannel\fP was new, along with the PAM format, in Netpbm
+9.7 (August 2000).
+.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/pamchannel.html
+.PP \ No newline at end of file