Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!CLVMS.BITNET!ABSTINE
From: ABSTINE@CLVMS.BITNET (Art Stine)
Newsgroups: mod.computers.vax
Subject: Stream files...
Message-ID: <8608190243.AA24449@ucbjade.Berkeley.Edu>
Date: Mon, 18-Aug-86 22:41:00 EDT
Article-I.D.: ucbjade.8608190243.AA24449
Posted: Mon Aug 18 22:41:00 1986
Date-Received: Wed, 20-Aug-86 23:24:35 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

Has anyone ever had to convert a 512byte fixed length file to true UNIX
style stream format? Using CONVERT, we get a file that still has a
max record length of 512, no matter what we specify as the size in the
FDL to convert it. The problem is that convert is putting a LF at the
end of each 512 byte record and ends up messing up the data...

What this is for is TeX. We have a routine which converts from TeX DVI
to Postscript and the routine is written in C. The routine is expecting
just a stream of bytes, no record blocking.


One of our programmers is currently using a Pascal program to convert the
binary DVI to an ASCII dump and then using a C program to read the dump and
convert it back to stream binary. The output from the C program makes
ANALYZE/RMS lose its lunch, since it doesn't seem to conform to RMS. But
the DVI2PS C program will read it, no sweat.

Any ideas?

Art Stine
Systems Programmer
Clarkson University
Educational Resources Center
Potsdam, NY 13676

Phone: (315)268-2292
BITNET: ABSTINE@CLVMS