1Pamtotga User Manual(0) Pamtotga User Manual(0)
2
3
4
6 pamtotga - convert a Netpbm image to a TrueVision Targa file
7
8
10 pamtotga [-mono|-cmap|-rgb] [-norle] [-name=name [pamfile]
11
12 All options can be abbreviated to their shortest unique prefix. You
13 may use two hyphens instead of one to designate an option. You may use
14 either white space or equals signs between an option name and its
15 value.
16
17
19 This program is part of Netpbm(1).
20
21 pamtotga reads a PBM, PGM, PPM, or PAM image as input and produces a
22 TrueVision Targa file as output. The PAM image may be either a
23 BLACKANDWHITE, GRAYSCALE, RGB, or RGB_ALPHA image.
24
25 To create a TGA image with transparency (i.e. with a transparency
26 mask), use RGB_ALPHA PAM input. Some Netpbm programs that generate
27 images with transparency masks generate them in that format. For
28 another way to create the proper input stream, see pamstack(1).
29
30 It is unclear that anything except pamtotga knows about TGAs with
31 transparency. The history behind this feature of pamtotga is not
32 clear. The format pamtotga produces is simply the same as an ordinary
33 RGB TGA image except with a 4th plane added for transparency. The Pix‐
34 elSize field of the TGA header specifies 32 bits instead of 24 and the
35 raster has an extra byte added to each pixel, at the tail end. The
36 value of that byte has the same meaning as in a PAM image with maxval
37 255.
38
39
41 -cmap Make output Targa file of type 24 bit colormapped. Input must
42 contain no more than 256 distinct colors.
43
44
45 -mono Make output Targa file of type 8 bit monochrome. Input must be
46 PBM or PGM or a PAM with BLACKANDWHITE or GRAYSCALE tuple type.
47 See -cmap.
48
49 You may specify at most one of -mono, -cmap, and -rgb. If you
50 specify neither, the default image type is the most highly con‐
51 strained compatible type is used, where monochrome is more con‐
52 strained than colormapped which is in turn more constrained than
53 unmapped.
54
55
56 -rgb Make output Targa file of type 24 bit unmapped color. See
57 -cmap.
58
59
60 -norle Do not use run-length encoding in the output Targa file. Run-
61 length encoded files are smaller, but Some Targa readers can't
62 read run-length encoded files.
63
64
65 -name=name
66 This is the value for the image ID stated in the header of the
67 TGA output file. pamtotga truncates it as necessary to meet TGA
68 standards.
69
70 By default, pamtotga uses the input file name argument, up to
71 the first period (or the whole thing if there is no period). It
72 truncates it as necessary to meet TGA standards. If you specify
73 (or default to) Standard Input, pamtotga omits the image ID from
74 the TGA header.
75
76
77
78
80 tgatoppm(1), pnmquant(1), pamstack(1), pam(1) pnm(1)
81
82
84 This program was called ppmtotga until Netpbm 10.6 (July 2002). That
85 was always a misnomer, though, because a PPM class program would not be
86 able to tell the difference between PGM and PPM input (it would all
87 look like PPM), and thus could not choose the output Targa image type
88 based on the type of the input. Netpbm 10.6 also added the ability to
89 handle a transparency channel, so it became a PAM class program.
90
91 In Netpbm 10.15 (April 2003), the program became the first in the
92 Netpbm package to recognize a transparency channel in a PAM. It recog‐
93 nized tuple type "RGBA". But when this kind of PAM image was later
94 added to the PAM specification, it was specified with tuple type
95 "RGB_ALPHA". So in Netpbm 10-26 (January 2005), pamtotga changed to
96 recognize "RGB_ALPHA" instead of "RGBA".
97
98
100 Copyright (C) 1989, 1991 by Mark Shand and Jef Poskanzer.
101
103 This manual page was generated by the Netpbm tool 'makeman' from HTML
104 source. The master documentation is at
105
106 http://netpbm.sourceforge.net/doc/pamtotga.html
107
108netpbm documentation 12 June 2008 Pamtotga User Manual(0)