tang@eleazar.dartmouth.edu (Charles W. T. Tang) (08/13/90)
Hi, could someone kindly tell me how to use the lpr command in UNIX to
print out a postscript file (but not a listing of)? What are the flags
that need to be specified? And, what should the files start out saying?
(I want to know where to make the cut....)
Thanks in advance!
Charles the Clueless
--
**** Om Ma-Ni Be-Me Hung **** | "All the world's phenomena and ideas
==============================| Are unreal, like a dream,
Charles Wei-Ting Tang | Like magic, and like a reflected image."
charles.tang@dartmouth.edu | -- The Diamond Sutrasteves@mcrware.UUCP (Steve Simpson) (08/13/90)
In article <23632@dartvax.Dartmouth.EDU> tang@eleazar.dartmouth.edu (Charles W. T. Tang) writes: >Hi, could someone kindly tell me how to use the lpr command in UNIX to >print out a postscript file (but not a listing of)? What are the flags >that need to be specified? And, what should the files start out saying? >(I want to know where to make the cut....) > >Charles the Clueless Your Postscript file should have a .ps extension and you can lpr it directly to you PS printer. We generate PS files from our FrameMaker system, put them on an MS-DOS or Mac disc and take them to a PS service bureau for 2540 dpi output. We use this in place of set type for our magazine, brochures and other literature. Good Luck ============================================== "Homer" Simpson "Remember...As fas as anyone knows, we're a nice, normal family." Disclaimer: My words, not theirs. ==============================================
willis@eosdev.eos.ncsu.edu (Dr. William E. Willis) (08/13/90)
Actually it is probably NOT the .ps file type, but the first line of postscript code. It should begin with %!...
hwt@.bnr.ca (Henry Troup) (08/14/90)
In article <1990Aug13.163300.25168@ncsuvx.ncsu.edu> willis@eosdev.eos.ncsu.edu (Dr. William E. Willis) writes: >Actually it is probably NOT the .ps file type, but the first line of >postscript code. >It should begin with %!... It's very system dependent - for a while here we used the -v (versatec) flag. Ask your system administrator. If you are your system administrator, decipher the /etc/printcap file - and good luck! -- Henry Troup - BNR owns but does not share my opinions | 21 years in Canada... uunet!bnrgate!hwt%bwdlh490 HWT@BNR.CA 613-765-2337 |
brown@vidiot.UUCP (Vidiot) (08/15/90)
In article <23632@dartvax.Dartmouth.EDU> tang@eleazar.dartmouth.edu (Charles W. T. Tang) writes:
<Hi, could someone kindly tell me how to use the lpr command in UNIX to
<print out a postscript file (but not a listing of)? What are the flags
<that need to be specified? And, what should the files start out saying?
<(I want to know where to make the cut....)
If you send a PostScript file to a PostScript printer, with lpr, it should
print out just fine. That is unless you have some kind of strange filter
attached to your print spooler.
You didn't say, but are you sending the PostScript file to a PostScript
laser printer? If not, all you'll get is a listing.
If you have a PostScript printer attached to your system, make sure the
first line is: %!PS
These are a few things to check. But without details about your system,
it is a little tough to figure out. Please give exacting details of
what you have and what you are doing, as it will help people on the net
to understand what is wrong. Just saying that it is broken and asking
what is wrong is like asking us to use a crystal ball.
--
harvard\ att!nicmad\ spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot ucbvax!uwvax..........!astroatc!vidiot!brown
rutgers/ decvax!nicmad/ INET:<@spool.cs.wisc.edu,@astroatc:brown@vidiot>brown@vidiot.UUCP (Vidiot) (08/16/90)
In article <2445@mcrware.UUCP> steves@mcrware.UUCP (Steve Simpson) writes:
<
<Your Postscript file should have a .ps extension and you can lpr it directly
<to you PS printer.
As far as I have every noticed, on either a 4.3BSD system, or my current
AT&T SysV 3.2 system, the name of the file is unimportant. The .ps extension
means nothing to the printer spooler.
--
harvard\ att!nicmad\ spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot ucbvax!uwvax..........!astroatc!vidiot!brown
rutgers/ decvax!nicmad/ INET:<@spool.cs.wisc.edu,@astroatc:brown@vidiot>desh@watserv1.waterloo.edu (Desh D. Sharma) (08/16/90)
In article <673@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes: > In article <2445@mcrware.UUCP> steves@mcrware.UUCP (Steve Simpson) writes: > < > <Your Postscript file should have a .ps extension and you can lpr it directly > <to you PS printer. > > As far as I have every noticed, on either a 4.3BSD system, or my current > AT&T SysV 3.2 system, the name of the file is unimportant. The .ps extension > means nothing to the printer spooler. Sorry, I have lost the name of the person that originally asked the question. Anyway, this problem seems to be a case of probably a filtering program (setup as default in the printcap entry for the printer) that seems to be grabbing the file given it, wrapping some standard ASCII-to-PS code around it, and sending the result off to the printer. What you have to do is to tell lpr to use the literal switch so that this does not occur. On some older lpr's it used to be "-l", or some fixed and better written ones the "-Fl" switch is used. i.e. lpr -Plaser -Fl foobar.ps I don't think that the .ps extension should have any effect at all, but let's be consistent anyway. ....desh -- -=-=-=-= Desh D. Sharma, Arts Computing Office, Univ. of Waterloo, Waterloo, ON. CANADA Internet: ddsharma@watmath.waterloo.edu | desh@watserv1.waterloo.edu BITNET: DESH@WATDCS .OR. DESH@WATACO