1DVIPOS(1) ConTeXt DVIPOS(1)
2
3
4
6 dvipos - compute positions in a DVI file
7
8
10 dvipos [ OPTION... ] infile[.dvi]
11
12
14 dvipos parses a DVI file looking for pos: specials. It currently rec‐
15 ognizes pos:pxy, pos:pxywhd, pos:pxyplus, pos:begbox, pos:endbox,
16 pos:beglines, and pos:endlines. It then outputs the information from
17 those specials along with information that only a DVI postprocessor
18 could determine, such as the current x and y location. The output
19 looks like:
20 \pospxywhd{text:54}{54}{10663sp}{8535sp}{21326sp}{34081sp}{0sp}
21 and is suitable for including in a tex(1) or pdftex(1) auxilliary file,
22 such as document.tuo, to be read in by the next run of the tex(1) or
23 similar typesetting engine.
24
25
27 -h, --help
28 print usage.
29
30 -W, --warning
31 print warnings.
32
33 -v, --verbose
34 print verbose output.
35
36 -d, --debug
37 print dvitype(1) debugging data.
38
39 -s, --smashchars
40 regard height and depth as zero.
41
42 -o, --output=FILE
43 send all output to FILE. Without this option, output goes to
44 stdout.
45
46 -b, --bbox[=FILE]
47 send bounding box to FILE (default FILE is infile.pos).
48
49 -f, --framed[=BASE]
50 request copy of DVI file, BASE.dvi, with bounding boxes framed
51 (default FILE is infile_frames.dvi). See the --framesize
52 option.
53
54 -m, --mag=INT
55 override tex(1) magnification by INT.
56
57 -w, --framesize=INT
58 set frame rule size by INT (default 6554 = .1pt).
59
60 -p, --pages=X:Y
61 set page ranges from X to Y.
62
63
65 dvipos is run mostly behind the scenes by ConTeXt's texexec(1) between
66 runs of tex(1) or pdftex(1), in order to provide information to and get
67 information about positional graphics. These graphics are provided by
68 the MetaFun interface to mpost(1). dvipos is not used (or needed) in
69 PDF-output mode but is needed for DVI-output mode. pdftex(1) starting
70 with version 1.40 can produce position information even in DVI mode, so
71 once the ConTeXt macros take advantage of this feature, the need for
72 dvipos will fade.
73
74 Until then, here is a typical use of dvipos:
75 dvipos notes.dvi
76 The position information that is output is collected by texexec(1) to
77 include in the notes.tuo auxilliary file to use in the next run.
78
79
80
82 Extract positions from doc.dvi, with output to doc.loc:
83 dvipos -o doc.loc doc.dvi
84
85 Same as above, but also send bbox information to doc.pos:
86 dvipos -b -o doc.loc doc.dvi
87
88 Instead send bbox information to /tmp/debug.pos:
89 dvipos -b=/tmp/debug.pos -o doc.loc doc.dvi
90
91
93 dvips(1), dvitype(1), mpost(1), pdftex(1), tex(1), texexec(1).
94
95 For more about positional graphics, see the MetaFun documentation on
96 the ConTeXt wiki ⟨http://wiki.contextgarden.net/MetaFun⟩.
97
98
100 If you specify a file for the -b option, you must join the option and
101 name with rather than (the more common) space:
102 dvipos -b=/tmp/debug.pos notes.dvi
103 works, but
104 dvipos -b /tmp/debug.pos notes.dvi
105 does not.
106
107
109 dvipos is written by Jin-Hwan Cho <chofchof@ktug.or.kr>. It is free
110 software (GPLv2 or later). This manpage was written by Sanjoy Mahajan
111 <sanjoy@mit.edu> and is in the public domain.
112
113
114
115dvipos 20070107 (KPATHSEA) January 2007 DVIPOS(1)