Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!uflorida!mephisto!prism!ae219dp
From: ae219dp@prism.gatech.EDU (Devon Prichard)
Newsgroups: comp.text.tex
Subject: Re: dvi files and printer drivers
Summary: dvi_1 is not necessarily dvi_2
Keywords: dvi
Message-ID: <7294@hydra.gatech.EDU>
Date: 20 Mar 90 19:41:32 GMT
References: <7457@latcs1.oz.au> <5224@jarthur.Claremont.EDU>
Reply-To: ae219dp@prism.gatech.EDU (Devon Prichard)
Organization: Georgia Institute of Technology
Lines: 23


From: dhosek@jarthur.Claremont.EDU (---)

>The problem is almost definitely with the file transfer process. DVI is DVI is
>DVI is DVI. An uncorrupted DVI file will be interpretable by any DVI driver
>and produce more-or-less identical results (assuming of course that no funky things like \special's or device fonts 
>are used).

I'm not sure about this.  I LaTeX-ed a file on hydra.gatech.edu (a Sequent
unix box) and FTP'd the file to a CYBER 855 running NOS 2.  I then
tried to print the file to a Xerox laserprinter in Epic format (there
is a utility to convert dvi to Epic).  The converter didn't understand
the "version" of dvi the file was written in!!  the LaTeX on the
Sequent is much more recent than that on the CYBER, as far as I know.




-- 
 ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 | Devon Prichard             making the world safe for helicopters ... |
 | ae219dp@prism.gatech.edu                                             |
 ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||