Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!woody From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal) Newsgroups: comp.lang.postscript Subject: Re: Why is Mac PostScript a problem Summary: More proprietary bs Keywords: mac postscript Message-ID: <1406@chinacat.Unicom.COM> Date: 18 Jul 90 02:22:07 GMT References: <9674@hubcap.clemson.edu> <2514@sequent.cs.qmw.ac.uk> Organization: a guest of Unicom Systems Development, Austin Lines: 24 In article <2514@sequent.cs.qmw.ac.uk>, liam@cs.qmw.ac.uk (William Roberts) writes: > In <9674@hubcap.clemson.edu> philip@hubcap.clemson.edu (Philip L Harshman) writes: > > > Mac LaserPrep files are a problem because they make use of such > a wide range of PostScript esoterica and have built-in > assumptions about the kinds of printers they might be used > > Some of the eexec stuff actually contains a string of gibberish > which is passed to cexec (is this 68000 code?), so that may > cause some hassle with printers onther than the LaserWriters. Yes it is 68000 machine language. I would appreciate it if someone would email me the eexec portions of the laser prep file, as I don't have a MAC to get it from. I'd like to look at the 68000 code a bit. I'm currently tearing Cexec stuff appart, and documenting how it works. I'm looking for all the cexec stuff I can get my hands on. I suspect that Apple does these sorts of things, to encourage people to buy THIER laserprinter, rather than someone elses. I'm sure that is why the original laserwriters didnot have a centronics port...etc... Cheers Woody