Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!questor!aberno From: aberno@questor.wimsey.bc.ca (Anthony Berno) Newsgroups: comp.sys.next Subject: EPS Message-ID: Date: 18 Dec 90 16:33:59 GMT Organization: Questor: FREE Internet Access => +1 604 681.0670 Lines: 21 Thank you to everyone who responded to my message about EPS non-editability. However, I still think there is hope. So PostScript is like a full language, with routines and data structures and such. Well, the thing is, when you print an EPS file, you *generally* get a single, fixed, result, right? There are some exceptions - like those silly new "random" fonts, but generally, you get the same output if you do it twice in a row. As such, that output should be made up out of primitives, like squares, polygons, bitmaps, Bezier curves, etc. Well, suppose you wrote a program that simulated an EPS file printing out, but didn't send the results to the printer. Instead, it intercepted them, and converted the print calls into things like polygons or letters or bezier curves in some common, sensible format. Unless you simply CAN'T get at the output of the EPS file until it has been converted all the way to a bitmap, just about anything should be interpretable as a small set of graphics primitives. Any comments here? I don't know hoot about PostScript, but I would be most interested in learning it and doing just this when I get my NeXT.