[comp.sys.next] dvips seeking

rokicki@Neon.Stanford.EDU (Tomas G. Rokicki) (01/17/90)

Two answers here.  For those doing odd/even separations (or double-sided
printing) on your cube from dvips, get dvidvi from labrea.stanford.edu in
the pub subdirectory (labrea:pub/dvidvi.tar.Z), compile and go.

Dvips needs a seekable input because it must scan the dvi file at least
twice (once to collect font usage information and create the font header
and once to actually send the pages.)  If you need a seekable input for
some strange reason, create a shell script that copies the input to a
temporary file and then runs dvips over this temporary file.  There are
some subtle flaws with this approach, though, if you are including
graphics and haven't fully specified the path of the graphics and
your temporary file isn't in the same directory as the dvi file.

The reason dvips doesn't do this is because TeX, by definition, writes
a nice solid dvi file to the disk, so one definitely exists.

-tom

lee@uhccux.uhcc.hawaii.edu (Greg Lee) (01/19/90)

From article <1990Jan16.225202.8817@Neon.Stanford.EDU>, by rokicki@Neon.Stanford.EDU (Tomas G. Rokicki):
" ...
" The reason dvips doesn't do this is because TeX, by definition, writes
" a nice solid dvi file to the disk, so one definitely exists.

But if you want to print on Unix with "lpr -d ..." you need a filter.

			Greg, lee@uhccux.uhcc.hawaii.edu