Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!agate!agate!adrianho From: adrianho@barkley.berkeley.edu (Adrian J Ho) Newsgroups: comp.lang.postscript Subject: Re: Flattenpath (was letter height) Message-ID: Date: 28 May 91 22:03:00 GMT References: <1991May28.134420.3951@engage.pko.dec.com> <91148.135401CXT105@psuvm.psu.edu> Sender: root@agate.berkeley.edu (Charlie Root) Distribution: comp.lang.postscript Organization: University of California, Berkeley Lines: 25 In-Reply-To: CXT105@psuvm.psu.edu's message of 28 May 91 17: 54:01 GMT In article <91148.135401CXT105@psuvm.psu.edu> CXT105@psuvm.psu.edu (Christopher Tate) writes: >In article <1991May28.134420.3951@engage.pko.dec.com>, davis@3d.enet.dec.com >(Peter Davis) says: >> >>This is very simple: >> >> (N) true charpath flattenpath pathbbox >> /y2 exch def /x2 exch def /y1 exch def /x1 exch def >> /height y2 y1 sub def >> newpath >I'm curious. Why execute flattenpath before pathbbox? What happens if >you omit the call to flattenpath? ``If the path includes curve segments, the bounding box enclosed the control points of the curves as well as the curves themselves. To obtain a bounding box that fits the path more tightly, one should first "flatten" the curve segments by executing 'flattenpath.' '' [Postscript Language Reference Manual, 2ed, pp. 461] > Shouldn't the above code cause >different results based on the value of currentflat? Perhaps a net.PS.guru could answer this question -- I can't. 8-)