Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ames!think!sdd.hp.com!samsung!cs.utexas.edu!chinacat!woody
From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal)
Newsgroups: comp.lang.postscript
Subject: Re: path to calligraphy penstroke
Summary: in a month or so.
Message-ID: <1297@chinacat.Unicom.COM>
Date: 4 Jun 90 04:49:38 GMT
References: <12041@june.cs.washington.edu> <1990May30.020154.7416@athena.mit.edu> <.644234162@dutepp1>
Organization: a guest of Unicom Systems Development, Austin
Lines: 21

In article <.644234162@dutepp1>, alfred@dutepp1.tudelft.nl (Alfred Kayser) writes:
> mar@athena.mit.edu (Mark A. Rosenstein) writes:
> >(TESTING) false charpath penstroke
> 
> According to my laserprinter (TI2115) and the PS red book: (page 192)
> If <charpath> was used to construct any portion of the current path,
> <pathforall> is not allowed; its execution will produce an 'invalidaccess'
> error.
> 
> Who can invent a routine <penstroke> alike, but working with fonts?

This invalidaccess thing on fontpaths has now been defeated.  I have seen
a nifty little routine that is called apathforall that happily allows you
to do apathforall on a path that has charcters in it, and proceeds to merrily
give you all of the coordinates and strokes.  It works on all type 1 fonts,
including the ROM ed ones.  I have NO idea who wrote it and don't know
how the guy got it, but it does work.  When I find out more, I'll put
out an update on the routine.

Cheers
Woody