🚀 go-pugleaf

In article <l9r7r0INNq42@utkcs2.cs.utk.edu>, eijkhout@cupid.cs.utk.edu (Victor Eijkhout) writes:
> In article <1992Aug28.010819.1940@umr.edu>, mcastle@mcs213d.cs.umr.edu (Michael R Castle) writes:
> |> Our local IBM mainframe has a 3820 laster printer on it that can handle 
> |> duplex printing.  The mainframe has TeX and dvi support for the 3820, but
> |> I'd rather use the TeX system on our unix system.  My problem is moving the
> |> dvi files from the ascii based unix system to the ebcdic based ibm mainframe.

> |> I've done a little of of looking and asking around, but can't seem to find
> |> anything that looks like it would be useful for making an easy transition
> |> between the systems.

> You don't say that you have tried to simply transport the dvi files and
> that you've failed. Have you tried simply binary transporting them?

> (Dvi files are completely byte-based, so it should work. In the past I've
> moved dvi files from an Atari-st to a Unix system, and they printed
> perfectly.)

DVI files should be transferred as binary files.

When moving a DVI file to any system with a record-based file
system (CMS, MVS, VMS, ???), you also need to worry about the
padding of the final record of the file. Simply using FTP to
transfer the file with F1024 records is not enough for a valid
DVI file on CMS (although it is necessary). One must also make
sure that the file is padded xDF (which is valid) instead of the
x00's that are inserted by every file transfer protocol.

-dh

btw Victor, even ignoring the record issue, ST-Unix is far from
an analogous file transfer.

And it's the paper, not the ink.

Don Hosek                  
dhosek@ymir.claremont.edu  
Quixote Digital Typography 
714-621-1291