summary refs log tree commit diff
path: root/ppmtogif.html
blob: 513133a45c63cb77791f9a8ad4cb872539ab457a (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
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.3//EN">
<html><head><title>Ppmtogif User Manual</title></head>
<body>
<h1>ppmtogif</h1>

<h2>NAME</h2>

ppmtogif - replaced by pamtogif

<h2>DESCRIPTION</h2>

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

<p><b>ppmtogif</b> was replaced in Netpbm 10.37 (December 2006) by
<b><a href="pamtogif.html">pamtogif</a></b>.

<p><b>pamtogif</b> is mostly backward compatible with <b>ppmtogif</b>.

<p>One way <b>pamtogif</b> is not backward compatible with <b>ppmtogif</b>
is that to specify a transparency (alpha) mask with <b>ppmtogif</b>, you
supply the transparency as a separate pseudo-PGM image and use the
<b>-alpha</b> option, whereas with <b>pamtogif</b>, you supply an input
image that has the transparency integrated into it, and there is no
<b>-alpha</b> option.

<p><b>ppmtogif</b> still exists as a separate program for backward 
compatibility, but it runs <b>pamtogif</b> to do the essential work.
The compatibility <b>ppmtogif</b> interprets an <b>-alpha</b> option
by reading the transparency image and combining it with the input
image, then feeding <b>pamtogif</b> the combined image it expects.
Other than that, the compatibility <b>ppmtogif</b> just passes input and
options directly to <b>pamtogif</b>.

<p>You should not make any new use of <b>ppmtogif</b> and if you modify an
existing use, you should upgrade to <b>pamtogif</b>.  But note that if you
write a program that might have to be used with old Netpbm, <b>ppmtogif</b> is
the only way to do that.

<p>Unless you use the <b>-alpha</b> option, you can simply change the name
of the program.  If you use <b>-alpha</b>, here is how to upgrade:

<pre>
<kbd>
  $ ppmtogif -alpha=myalpha.pgm myinput.ppm &gt;myoutput.gif
</kbd>
</pre>

becomes

<pre>
<kbd>
  $ pamstack -tupletype=RGB_ALPHA myinput.ppm myalpha.pgm |  \
      pamtogif &gt;myoutput.gif
</kbd>
</pre>


<h2>Original Ppmtogif</h2>

<p>If you are using Netpbm before 10.37, <b>pamtogif</b> doesn't exist,
so you use <b>ppmtogif</b>.  You can use the <b>pamtogif</b> manual
for <b>ppmtogif</b>, with the following exceptions.

<p>The current documentation of <b>pamtogif</b> documents all versions
of that program.  Use the information for Version 10.37 only.

<p><b>ppmtogif</b> before Netpbm 10.31 does not accept PAM input at all.

<p><b>ppmtogif</b> does not accept PAM input with transparency information
in it.  Instead, <b>ppmtogif</b> has an <b>-alpha</b> option.

<p>The syntax of the option is <b>-alpha=</b><i>pgmfile</i>.
<b>ppmtogif</b> treats the contents of the named PGM file the same as
<b>pamtogif</b> treats the alpha plane of a PAM.  The PGM image must
have the same dimensions as the input file.  But unlike the PAM case,
the alpha image need not have the same maxval as the input.
<b>ppmtogif</b> interprets the alpha file using the alpha file's
maxval.

<p>You cannot specify both <b>-transparent</b> and <b>-alpha</b>.


</body>
</html>