summary refs log tree commit diff
path: root/pamtopnm.html
blob: 67657ae71d2ddb86e0023e63694d40ce03993946 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML><HEAD><TITLE>Pamtopnm User Manual</TITLE></HEAD>
<BODY>
<H1>pamtopnm</H1>
Updated: 03 August 2000
<BR>
<A HREF="#index">Table Of Contents</A>

<H2 id="name">NAME</H2>

pamtopnm - convert PAM image to PBM, PGM, or PPM

<H2 id="synopsis">SYNOPSIS</H2>

<B>pamtopnm</B>

[<B>-assume</B>]

[<I>pnmfile</I>]

<P>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.

<H2 id="description">DESCRIPTION</H2>

<p>This program is part of <a href="index.html">Netpbm</a>.

<p><b>pamtopnm</b> reads a PAM image as input and produces an
equivalent PBM, PGM, or PPM (i.e. PNM) image, whichever is most
appropriate, as output.

<P><B>pamtopnm</B> assumes the PAM image represents the information
required for a PBM, PGM, or PPM image if its tuple type is
&quot;BLACKANDWHITE&quot;, &quot;GRAYSCALE&quot;, or &quot;RGB&quot;
and its depth and maxval are appropriate.  If this is not the case,
<B>pamtopnm</B> fails.

<P>However, you can override the tuple type requirement with the
<B>-assume</B> option.

<P>As with any Netpbm program that reads PAM images, <B>pamtopnm</B>
also reads PNM images as if they were PAM.  In that case,
<B>pamtopnm</B>'s functions reduces to simply copying the input to the
output.  But this can be useful in a program that doesn't know whether
its input is PAM or PNM but needs to feed it to a program that only
recognizes PNM.

<H2 id="options">OPTIONS</H2>

<DL COMPACT>
<DT><B>-assume</B>

<DD>When you specify <B>-assume</B>, you tell <B>pamtopnm</B> that you
personally vouch for the fact that the tuples contain the same data as
belongs in the channels of a PBM, PGM, or PPM file.  The depth must
still conform, though, so to truly force a conversion, you may have to
run the input through <B>pamchannel</B> first.  But be careful with
<B>-assume</B>.  When you -assume, you make an -ass of u and me.

</DL>

<H2 id="seealso">SEE ALSO</H2>

<B><A HREF="pbmtopgm.html">pbmtopgm</A></B>,
<B><A HREF="pamditherbw.html">pamditherbw</A></B>,
<B><A HREF="pgmtoppm.html">pgmtoppm</A></B>,
<B><A HREF="ppmtopgm.html">ppmtopgm</A></B>,
<B><A HREF="pam.html">pam</A></B>,
<B><A HREF="pnm.html">pnm</A></B>,
<B><A HREF="pbm.html">pbm</A></B>,
<B><A HREF="pgm.html">pgm</A></B>,
<B><A HREF="ppm.html">ppm</A></B>


<h2 id="history">HISTORY</h2>

<p><b>pamtopnm</b> was new, along with the PAM format, in Netpbm
9.7 (August 2000).

<HR>
<A NAME="index">&nbsp;</A>
<H2>Table Of Contents</H2>
<UL>
<LI><A HREF="#synopsis">SYNOPSIS</A>
<LI><A HREF="#description">DESCRIPTION</A>
<LI><A HREF="#options">OPTIONS</A>
<LI><A HREF="#seealso">SEE ALSO</A>
<LI><A HREF="#history">HISTORY</A>
</UL>
</BODY>
</HTML>