Path: utzoo!attcan!uunet!mcsun!goya!colon!jjsf
From: jjsf@gmv.es (Julio Sanchez)
Newsgroups: comp.text.tex
Subject: Re: dvi files and printer drivers
Message-ID: <1626@colon.gmv.es>
Date: 21 Mar 90 13:19:08 GMT
References: <7457@latcs1.oz.au> <5224@jarthur.Claremont.EDU>
Reply-To: jjsf@colon.UUCP (Julio Sanchez)
Organization: Grupo de Mecanica del Vuelo, S.A. (GMV), Madrid, Spain
Lines: 22

In article <5224@jarthur.Claremont.EDU> dhosek@jarthur.Claremont.EDU (---) writes:
>In article <7457@latcs1.oz.au> suter@latcs1.oz.au (David Suter) writes:
>[stuff deleted]
>
>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).
Well DVI is DVI, more or less. On VAX/VMS, for instance, DVI files
are organised in fixed-size records (512 bytes, I think) for
the sake of efficiency. So transferring DVI files from a PC to a
VMS system may be non-trivial.

I would appreciate input from people who are doing this. The
same goes for font files.

Julio Sanchez                            Ph. +34 1 534 30 04
Grupo de Mecanica del Vuelo, S.A. (GMV)  Fax +34 1 533 32 50
Cristobal Bordiu, 35                     Telex  48487 GMEV E
E-28003 MADRID                           jsanchez@gmv.es
SPAIN                                    mcsun!gmv.es!jsanchez@uunet.uu.net
                                         uunet!mcsun!gmv.es!jsanchez