Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!know!tegra!nad
From: nad@tegra.COM (Nancy Durgin)
Newsgroups: comp.sys.amiga
Subject: Re: POST1.3 -- findfont problems
Keywords: post, post1.3, postscript, findfont
Message-ID: <1703@robbie.tegra.COM>
Date: 7 Nov 90 18:03:01 GMT
References: <39277@ut-emx.uucp>
Reply-To: nad@robbie.UUCP (Nancy Durgin)
Organization: Tegra-Varityper, Inc. Billerica, MA
Lines: 41

In article <39277@ut-emx.uucp> phao172@emx.utexas.edu (Randy M. Roberts) writes:
>I downloaded post1.3 and post13fonts from "new xanth" the other day.
>I copied Helvetica from the post13fonts into PSFonts:
>I edited s:init.ps to use PSFonts: just as the comments say to do.
>
>When I tried post1.3 as:
>
>	post s:init.ps screen
>
>and went into interactive mode, and typed
>
>	/Helvetica findfont
>	96 scalefont
>	72 72 moveto
>	(ABC) show
>
>I got three big dots, i.e. the dumb default font.
>

Well, I'm not familiar with how Post1.3 works, but the above code needs
a 'setfont' before it is going to do what you want.  i.e.:

        /Helvetica findfont
        96 scalefont setfont
        72 72 moveto
        (ABC) show

If it doesn't find Helvetica at the point when it executes findfont,
it should print some kind of message the gist of which is "font not found,
using default font".  If you don't get this message, then it found the
font (Assuming Post1.3 handles this the way Adobe does).

Hope this helps...

	Nancy

-- 
==============================================================================
Nancy Durgin          | (Usual disclaimers | Tegra-Varityper, Inc. 
tegra!nad@uunet.com   | apply...)          | Billerica, Massachusetts
==============================================================================