Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!natinst!rpp386!woody From: woody@rpp386.cactus.org (Woodrow Baker) Newsgroups: comp.lang.postscript Subject: Re: currentpoint != last-point-in-path after charpath??? Summary: I hit it to Message-ID: <18088@rpp386.cactus.org> Date: 4 Mar 90 01:48:43 GMT References: Distribution: comp Organization: River Parishes Programming, Plano, TX Lines: 30 In article , loki@moncam.uucp (Never Kid A Kidder) writes: > (a) false charpath > > > the `a' (presumably the last point in the character data). I've never > read of this discrepancy as a feature, but I noticed that Adobe's > implementation of their `boldening' does a charpath (each character > individually) followed by an explicit `currentpoint moveto', so it > looks like they're aware of it. You don't notice it if you just > charpath a string and then stroke it. You also don't notice it if you > do something like I recently encountered it when working on a new program. This one typesets music TABLATURE for the fiddle. It does not use normal notation, and as such, I am not using Sonota. I am using some DINGBATS, and normal drawing commands such as lineto. The problem started when I was creating multiple note heads, with various shading. It really vexed me. I gave up worring about it, and did the expicit moveto that was needed to cure it. I have never heard of it before, but it would seem to be a very subtle bug. I'd call it that, because to my knowlege it is not documented behavior. On a related topic, does anyone know EXACTLY what is preserved by a gsave. grestore pair. The books say "the current graphics state" and give some general things, but so far, I have never seen a comprehensive list of EVERYTHING that gets saved. This would be imensely helpful... C Cheers Woody