| 1 |
\ |
| 2 |
.\" This man page was generated by the Netpbm tool 'makeman' from HTML source. |
| 3 |
.\" Do not hand-hack it! If you have bug fixes or improvements, please find |
| 4 |
.\" the corresponding HTML page on the Netpbm website, generate a patch |
| 5 |
.\" against that, and send it to the Netpbm maintainer. |
| 6 |
.TH "Ppmtogif User Manual" 1 "" "netpbm documentation" |
| 7 |
|
| 8 |
.SH NAME |
| 9 |
|
| 10 |
ppmtogif - replaced by pamtogif |
| 11 |
|
| 12 |
.SH DESCRIPTION |
| 13 |
.PP |
| 14 |
This program is part of |
| 15 |
.BR "Netpbm" (1)\c |
| 16 |
\&. |
| 17 |
.PP |
| 18 |
\fBppmtogif\fP was replaced in Netpbm 10.37 (December 2006) by |
| 19 |
.BR "pamtogif" (1)\c |
| 20 |
\&. |
| 21 |
.PP |
| 22 |
\fBpamtogif\fP is mostly backward compatible with \fBppmtogif\fP. |
| 23 |
.PP |
| 24 |
One way \fBpamtogif\fP is not backward compatible with \fBppmtogif\fP |
| 25 |
is that to specify a transparency (alpha) mask with \fBppmtogif\fP, you |
| 26 |
supply the transparency as a separate pseudo-PGM image and use the |
| 27 |
\fB-alpha\fP option, whereas with \fBpamtogif\fP, you supply an input |
| 28 |
image that has the transparency integrated into it, and there is no |
| 29 |
\fB-alpha\fP option. |
| 30 |
.PP |
| 31 |
Another more obscure way \fBpamtogif\fP is not backward compatible is |
| 32 |
the \fB-map\fP option. You use this option to specify what colors you want |
| 33 |
in the GIF image, because a GIF image can have at most 256 colors and your |
| 34 |
input image might have more than that. In \fBpamtogif\fP, the map image |
| 35 |
must be the same depth as the input image, but in \fBppmtogif\fP it need |
| 36 |
not. |
| 37 |
.PP |
| 38 |
\fBppmtogif\fP still exists as a separate program for backward |
| 39 |
compatibility, but it runs \fBpamtogif\fP to do the essential work. The |
| 40 |
compatibility \fBppmtogif\fP interprets an \fB-alpha\fP option by reading |
| 41 |
the transparency image and combining it with the input image, then feeding |
| 42 |
\fBpamtogif\fP the combined image it expects. If you use the \fB-map\fP |
| 43 |
option, the compatibility \fBppmtogif\fP also uses \fBpnmremap\fP on your |
| 44 |
input to make it the same depth as your map file. Other than that, the |
| 45 |
compatibility \fBppmtogif\fP just passes input and options directly to |
| 46 |
\fBpamtogif\fP. |
| 47 |
.PP |
| 48 |
You should not make any new use of \fBppmtogif\fP and if you modify an |
| 49 |
existing use, you should upgrade to \fBpamtogif\fP. But note that if you |
| 50 |
write a program that might have to be used with old Netpbm, \fBppmtogif\fP is |
| 51 |
the only way to do that. |
| 52 |
.PP |
| 53 |
Unless you use the \fB-alpha\fP or \fB-map\fP option, you can simply |
| 54 |
change the name of the program. If you use \fB-alpha\fP, here is how to |
| 55 |
upgrade: |
| 56 |
|
| 57 |
.nf |
| 58 |
\f(CW |
| 59 |
$ ppmtogif -alpha=myalpha.pgm myinput.ppm >myoutput.gif |
| 60 |
\fP |
| 61 |
|
| 62 |
.fi |
| 63 |
|
| 64 |
becomes |
| 65 |
|
| 66 |
.nf |
| 67 |
\f(CW |
| 68 |
$ pamstack -tupletype=RGB_ALPHA myinput.ppm myalpha.pgm | \e |
| 69 |
pamtogif >myoutput.gif |
| 70 |
\fP |
| 71 |
|
| 72 |
.fi |
| 73 |
|
| 74 |
|
| 75 |
.SH Original Ppmtogif |
| 76 |
.PP |
| 77 |
If you are using Netpbm before 10.37, \fBpamtogif\fP doesn't exist, |
| 78 |
so you use \fBppmtogif\fP. You can use the \fBpamtogif\fP manual |
| 79 |
for \fBppmtogif\fP, with the following exceptions. |
| 80 |
.PP |
| 81 |
The current documentation of \fBpamtogif\fP documents all versions |
| 82 |
of that program. Use the information for Version 10.37 only. |
| 83 |
.PP |
| 84 |
\fBppmtogif\fP before Netpbm 10.31 does not accept PAM input at all. |
| 85 |
.PP |
| 86 |
\fBppmtogif\fP does not accept PAM input with transparency information |
| 87 |
in it. Instead, \fBppmtogif\fP has an \fB-alpha\fP option. |
| 88 |
.PP |
| 89 |
The syntax of the option is \fB-alpha=\fP\fIpgmfile\fP. |
| 90 |
\fBppmtogif\fP treats the contents of the named PGM file the same as |
| 91 |
\fBpamtogif\fP treats the alpha plane of a PAM. The PGM image must |
| 92 |
have the same dimensions as the input file. But unlike the PAM case, |
| 93 |
the alpha image need not have the same maxval as the input. |
| 94 |
\fBppmtogif\fP interprets the alpha file using the alpha file's |
| 95 |
maxval. |
| 96 |
.PP |
| 97 |
You cannot specify both \fB-transparent\fP and \fB-alpha\fP. |
| 98 |
.SH DOCUMENT SOURCE |
| 99 |
This manual page was generated by the Netpbm tool 'makeman' from HTML |
| 100 |
source. The master documentation is at |
| 101 |
.IP |
| 102 |
.B http://netpbm.sourceforge.net/doc/ppmtogif.html |
| 103 |
.PP |