4 \- PostScript picture packing preprocessor
13 to stdout, expanding picture inclusion requests
18 macros) into an in-line
19 format that can be passed through
30 standard input is read.
37 is a comma- or space-separated string of words used to locate
38 picture inclusion requests.
39 The start of every line in the input
41 is compared with each word in
43 If there is a match, the second string on the line is
44 taken as the pathname of a picture file that is added
52 Suppress ``missing picture file'' error messages.
55 is a trivial preprocessor that, in a sense, duplicates some of the
56 picture inclusion capabilities already available in
59 should not be used if your formatting command line includes
62 Its only purpose is to combine picture files with text in a single
63 file that can be passed through
65 and unpacked, at some later time, by
67 The original picture inclusion mechanism, with files are pulled in by
69 is the preferred approach.
71 A typical application might be in a distributed printing environment
72 where everything up to
74 is run by the user and everything after
76 is handled by a spooling daemon (perhaps
78 In that case the command line would be,
80 pic \f2file\fP | tbl | eqn | picpack | troff -mm -Tpost | lp
82 A poor example, although one that should still work, would be,
84 pic \f2file\fP | tbl | eqn | picpack | troff -mm -Tpost | dpost >\f2file\fP.ps
86 In this case picture inclusion requests could (and should) be handled by
90 is not needed or even recommended.
91 It should be dropped from any pipeline that includes a call to
94 A 0 exit status is returned if
96 were successfully processed.
99 Combining pictures and text using the capabilities available in
101 is the recommended approach and is always guaranteed to be more
108 in the same pipeline makes little sense.
112 will likely result in files that can no longer be reliably passed
113 through other important
119 is only guaranteed to work with