🚀 go-pugleaf

Re <9210260325.AA06018@cookie-crisp>
<199210241340.AA10000@claude.cs.umb.edu>:

> Date: Sat, 24 Oct 1992 09:40:15 -0400
> From: Karl Berry <karl@claude.cs.umb.edu>
> Sender: gnulists@ai.mit.edu
> To: bug-ghostscript@prep.ai.mit.edu
> Cc: walsh%ibis@cs.umass.edu
> Subject: charpath produces no output
> Reply-To: karl@cs.umb.edu
> Resent-From: bug-ghostscript-request@prep.ai.mit.edu
> 
> charpath produces no output for characters in the following Type 3 font.
> (show works, though.)  I'm not sure if it's a bug in Ghostscript or the
> font.  I didn't see anything obviously wrong in the font.  (Well, that's
> not quite true, the way they do encoding vectors seems confused, but I
> saw nothing that looked like dubious in re charpath.)
> 
> Specifically, I say:
> [... font and example omitted ...]

This is a bug in Ghostscript.  The `fill' in the BuildChar procedure,
since it's being called inside a `charpath', just appends the path to
the outer path; then a `restore' deallocates the path that was just
appended!

Unfortunately, I don't see any way to fix the bug without some
significant surgery to the memory manager, to decouple path
allocation from object allocation (i.e., multiple heaps).  Multiple
heaps is actually on my task list, since it's required for the Level
2 global/local VM and Display PostScript multiple context facilities,
but it's not scheduled until after the next (2.6) release.

Sorry, this one isn't going to get fixed right away.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; voice 415-322-0103 ; fax 322-1734
	    "Implementation is the sincerest form of flattery."