🚀 go-pugleaf

I'm trying to print out ALL the characters in a given built-in font
in a LaserWriter NTX.  In order to do this, I first print out the
256 positions in /Encoding, and then go after the character names
in /CharStrings which I missed.  This always seems to give rise to
an `invalidfont' error soon after printing starts.  Thank heaven
for ehandler.ps, but it doesn't answer two questions:

1. Is there a way to capture the `invalidfont' error without losing
   the current context (looping, etc.)?

2. Better yet, is there a test like `rcheck' which will tell me if
   this character is poison?

3. Do we have a bug in the NTX which causes these errors?  This
   behavior seems unreasonable, but I'm no marketing expert.

	Chuck Bacon, CRTB@alw.NIH.gov