Xref: utzoo comp.lang.postscript:8340 comp.sources.wanted:16287
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!decuac!haven!wam.umd.edu!rustyh
From: rustyh@wam.umd.edu (Michael Katzmann)
Newsgroups: comp.lang.postscript,comp.sources.wanted
Subject: Re: ACSII text to postscript
Keywords: postscript ascii dumb
Message-ID: <1991Apr16.154707.9283@wam.umd.edu>
Date: 16 Apr 91 15:47:07 GMT
References: <1991Apr11.145636.462@debet.nhh.no> <1991Apr11.210439.19346@wam.umd.edu> <1991Apr16.002701.17403@bmers145.bnr.ca>
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: Broadcast Sports Technology.
Lines: 25
Nntp-Posting-Host: epsl

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)


--
Michael Katzmann  (VK2BEA/G4NYV/NV3Z)   Please email to this address |
Broadcast Sports Technology                                          |
2135 Espey Ct. #4                                                   \|/
Crofton MD 21114-2442    (301) 721-5151      ...uunet!opel!vk2bea!michael