Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!samsung!munnari.oz.au!metro!extro!rossc From: rossc@extro.ucc.su.oz.au (Ross Cartlidge) Newsgroups: comp.lang.postscript Subject: Re: Type 1 font format Keywords: eexec type 1 font Message-ID: Date: 12 Mar 91 23:38:43 GMT References: <3466@polari.UUCP> Sender: news@metro.ucc.su.OZ.AU Organization: Sydney University Computing Service, Sydney, NSW, Australia Lines: 24 Nntp-Posting-Host: extro.ucc.su.oz.au mikeb@polari.UUCP (Mike Branch) writes: >In article rossc@extro.ucc.su.oz.au (Ross Cartlidge) writes: >>I have a PS interpreter that doesn't understand the type 1 fonts >>used in the eexec operator. How can I find out the format of >>these fonts so that I can at least skip them in the PS? >> >I don't quite understand what you mean by "skipping" them. Do you mean >you want your PS interpreter to ignore a request for a Type 1 font? >Hmmm, probably pretty sticky. >But, if you just want to examine a font file to see if it's Type 1, then >look for a line that says "/FontType 1 def". I incorectly guessed that the eexec's were encoded fonts - I was completely wrong. When I decrypted the eexec's I discovered that the Mac prologue uses eexec to send cexecs to the printer - and cexecs are 68000 code - so skipping them was a good idea. Mac LaserWriter drivers seem to produce the worst PS I have ever seen. -- ________________________________________________________________________ Ross Rodney Cartlidge | rossc@extro.ucc.su.oz.au University Computing Service, H08 | Phone: +61 2 6923497 University of Sydney, NSW 2006, Australia | FAX: +61 2 6606557