Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!cornell!uw-beaver!laser-lovers
From: laser-lovers@uw-beaver
Newsgroups: fa.laser-lovers
Subject: PostScript hackery
Message-ID: <1423@uw-beaver>
Date: Tue, 23-Jul-85 20:36:39 EDT
Article-I.D.: uw-beave.1423
Posted: Tue Jul 23 20:36:39 1985
Date-Received: Thu, 25-Jul-85 07:43:56 EDT
Sender: daemon@uw-beaver
Organization: U of Washington Computer Science
Lines: 17

From: Christopher A Kent <cak@Purdue.EDU>

I'm trying to get Purdue's logo (a stylized griffin) out onto our
printer's cover sheets. I have a digitized version and PostScript code
to print it out, but it's terribly slow. I'm defining my own font,
following the example in the cookbook, and it occurs to me that the
printer is probably bit tuning the logo every time it has to create it.
This isn't necessary -- I'd be happy just to get exactly the bits I
gave it back. Is there any way that I can construct the font machinery
code so that this is what happens?

Since the logo is large (about 1 square inch), and it's only used on
the cover page of each job, it doesn't end up in the cache very often.

Thanks,
chris
----------