diff options
author | Sanjoy Mahajan <sanjoy@olin.edu> | 2007-01-17 19:44:57 +0000 |
---|---|---|
committer | Sanjoy Mahajan <sanjoy@olin.edu> | 2007-01-17 19:44:57 +0000 |
commit | bd20a8ca78657278f385d36860ed91569b264ba1 (patch) | |
tree | e7b777e169488b65f90b3b9798548edc672c2a1d /Build/source/texk/dvipos/dvipos.1 | |
parent | 962bcd857b997ff552fd938fa94e4007565d3690 (diff) |
dvipos: added ChangeLog, revised man page, fixed version strings
Consistent with the GPL's section 2(a), I added a ChangeLog and
updated the version strings to be 20070107. People will then know
that they are running a different dvipos from the CTAN -20030628
version (which didn't work with current versions of ConTeXt), and can
blame the right people (i.e. me) if one of my two changes to dvicore.c
causes a problem. No binaries need rebuilding because all the changes
are to uncompiled files (ChangeLog, dvipos.1) or to uncompiled parts
of files (comments). In utils.h, the #define VERSION was already
20070107, so it remains unchanged.
git-svn-id: svn://tug.org/texlive/trunk@3556 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Build/source/texk/dvipos/dvipos.1')
-rw-r--r-- | Build/source/texk/dvipos/dvipos.1 | 31 |
1 files changed, 24 insertions, 7 deletions
diff --git a/Build/source/texk/dvipos/dvipos.1 b/Build/source/texk/dvipos/dvipos.1 index 477fdcec7bf..14e726b578f 100644 --- a/Build/source/texk/dvipos/dvipos.1 +++ b/Build/source/texk/dvipos/dvipos.1 @@ -1,4 +1,4 @@ -.TH "DVIPOS" "1" "January 2007" "dvipos 20030628 (KPATHSEA)" "ConTeXt" +.TH "DVIPOS" "1" "January 2007" "dvipos 20070107 (KPATHSEA)" "ConTeXt" .de URL \\$2 \(laURL: \\$1 \(ra\\$3 .. @@ -35,7 +35,10 @@ and is suitable for including in a .BR tex (1) or .BR pdftex (1) -auxilliary file, such as \fIdocument.tuo\fP, to be read in on the next run. +auxilliary file, such as \fIdocument.tuo\fP, to be read in by the next +run of the +.BR tex (1) +or similar typesetting engine. .SH OPTIONS @@ -81,22 +84,32 @@ set page ranges from X to Y. .SH USAGE .B dvipos -is run mostly by ConTeXt's +is run mostly behind the scenes by ConTeXt's .BR texexec (1) between runs of .BR tex (1) or .BR pdftex (1), -in order to compute positions for the metafun interface to +in order to provide information to and get information about +positional graphics. These graphics are provided by the MetaFun +interface to .BR mpost (1). -A typical use: +\fBdvipos\fP is not used (or needed) in PDF-output mode but is +needed for DVI-output mode. +.BR pdftex (1) +starting with version 1.40 can produce position information even in +DVI mode, so once the ConTeXt macros take advantage of this feature, +the need for \fBdvipos\fP will fade. + +Until then, here is a typical use of \fBdvipos\fP: .EX dvipos notes.dvi .EE The position information that is output is collected by .BR texexec (1) -to include in the \fInotes.tuo\fP auxilliary file for the next run -to use. +to include in the \fInotes.tuo\fP auxilliary file to use in the next +run. + .SH EXAMPLES .TP @@ -117,6 +130,10 @@ Instead send bbox information to \fI/tmp/debug.pos\fP: .BR tex (1), .BR texexec (1). +For more about positional graphics, see the MetaFun documentation on +the +.URL "http://wiki.contextgarden.net/MetaFun" "ConTeXt wiki" . + .SH BUGS If you specify a file for the \fB-b\fP option, you must join the option and name with rather than (the more common) space: |