🚀 go-pugleaf

In article <1991Apr16.154707.9283@wam.umd.edu> rustyh@wam.umd.edu (Michael Katzmann) writes:

>    In article <1991Apr16.002701.17403@bmers145.bnr.ca> friedman%chekov@uunet.uu.net writes:
>    >
>    >Being in need of a program to allow our printers to handle postscript
>    >and ascii transparently, I tried the 'dumb' ascii program recently 
>    >posted by Michael Katzmann.  Unfortunately, either it or I am too
>    >dumb :-) since it appears that once this program is loaded into a
>    >printer there is no way to revert to normal postscript operation short
>    >of powering off the printer.  Besides this the printer is extremely
>    >slow since the code seems to process input a character at a time.
>    >
>    >Come on guys, what is *THE BEST* unix solution to this problem?
>    >
>    If you send an EOF (ctrl D) to the printer, the read will return false
>    and the Finish routine will execute.  Problem solved!  Sorry I didn't
>    say this in the comments. 
> 
>    Also strip off the comments to the programme and it will take 1/2 the
>    time to download it. (You can't win. sigh)

  Why not convert the text to postscript?  I picked up a nice converter
program called 'lwf'.  It could be modified to detect if the file is postscript
or not by looking for the %! at the start of the file or... 
 Write a shell script that will detect if it is postscript and pipe it through
lwf.

  I picked up the 'LaserWriter filter' in comp.sources.misc.  It was posted by
brachman@grads.cs.ubc.ca (or, at least then shar file was created by him).

  This program has worked for me on QMS's, HP's, and an Apple.

--
# Harold Tomlinson			##	haroldt@paralandra.yorku.ca #
# Computing & Communications Services	##	(416)736-5257-33802         #
# YORK UNIVERSITY, Ont, CANADA		##	########################### #