Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!decwrl!adobe!heaven!glenn From: glenn@heaven.woodside.ca.us (Glenn Reid) Newsgroups: comp.sys.next Subject: Re: Preview and Postscript Oddness Message-ID: <381@heaven.woodside.ca.us> Date: 23 Dec 90 01:05:56 GMT References: <1990Dec19.181507.8063@noose.ecn.purdue.edu> Reply-To: glenn@heaven.woodside.ca.us (Glenn Reid) Organization: RightBrain Software, Woodside, CA Lines: 24 In article gessel@masada.cs.swarthmore.edu (Daniel Mark Gessel) writes: > Preview does not send >the postscript send to it to the printer, it actually gets the >postscript through the view used to display it onscreen. > >Look at the code it sends out sometime, and you'll see what I mean. That's not really true. It's exactly what would have gone to the printer. Try the "Save" button in the Print panel and compare. It's true that it's a version of the code the view used to display onscreen, but that's exactly how most apps print, since it's all just PostScript. The trouble with Preview is that it takes PS code that was destined for a printer, then wraps it up a second time when you print, so you get two copies of the NeXT emulations for some DPS operators, two copies of the page setup commands, and whatever else. Sometimes this works, often it doesn't. Preview, in my opinion, should pass the PostScript code straight through to the printer when you print, adding nothing. Glenn -- Glenn Reid RightBrain Software glenn@heaven.woodside.ca.us PostScript/NeXT developers ..{adobe,next}!heaven!glenn 415-851-1785