Xref: utzoo comp.protocols.appletalk:5757 comp.sys.mac.misc:11474
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!ni.umd.edu!ni.umd.edu!zben
From: zben@ni.umd.edu (Ben Cranston)
Newsgroups: comp.protocols.appletalk,comp.sys.mac.misc
Subject: Re: Modifying 6.? LaserPrep for 80 Character Line Limit
Summary: Just break the hex lines up
Message-ID: <1991Apr28.182032.15514@ni.umd.edu>
Date: 28 Apr 91 18:20:32 GMT
References: <1991Apr27.130313.29659@cns.umist.ac.uk>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland at College Park
Lines: 31
Nntp-Posting-Host: ni.umd.edu

In article <1991Apr27.130313.29659@cns.umist.ac.uk> jf@ap.co.umist.ac.uk
(John Forrest) writes:

> We have access to a colour laserprinter, which is attached to a
> VMS VAX, and which is accessed via ftp. The basic problem we
> have is the VMS spooler on this machine has a line limit of 80
> characters (!!). The system programmers for this machine do
> have a program to help get round this - it adjusts postscript
> so that the lines are less that 80 characters long [I don't
> think it is very complicated (:], but this cannot cope with
> strings longer than 80 characters. The problem? Well the
> LaserPrep for the 6.? driver (v70 I believe) has a load of hex
> strings at the top, which are much longer than 80 characters.
> For us to procede, we need a way of breaking these up.
 
> Any suggestions, or alternative ideas, would be appreciated.

The long lines of hexadecimal are actually 68000 machine language programs.
The one near the top is a patch for a particular revision of a particular
Apple printer type, if you don't have one of these you can take it out.

The two big hex blocks near the bottom are a "stretch" routine and a
"smooth4" routine.  Again, unless the printer is 68000-based these routines
are never used.

Also, the hex scanner should ignore whitespace, so you should be able to
break these lines up in any convenient way (though for safety's sake I would
break them at byte boundaries...) to fit within 80 characters.

It might even work if you were to find them in the LaserPrep resource file
and put in explicit newline characters...