🚀 go-pugleaf

[In my previous posting, I neglected to set the Followup-To field.  I
have corrected this oversight; further discussion of this topic is
redirected to comp.lang.postscript only.]

A Display PostScript expert has come up with the following better
solution to the FontDirectory problem.  Mine was a quick hack; his
solution here is more elegant and will work on both printer PostScript
and Display PostScript.

1. Just replace "FontDirectory" with

	[
	 FontDirectory {pop} forall
	  /SharedFontDirectory where {
	    /SharedFontDirectory get {pop} forall
	  } if
	]

   This simply builds an array of font names from both the private
   FontDirectory and the SharedFontDirectory, which is defined for
   Display PostScript systems.

2. Remove the leading "pop" from the "getfont" procedure because the
   array constructed in step one contains only font names.

The program then works as advertised on both Printer and Display
PostScript systems.  Be default fonts that are loaded via findfont are
put into SharedFontDirectory.  If an application simply uses the "run"
operator to load a font, it will be put into FontDirectory.  This may
lead to a font appearing more than once in the enumeration.  The
enumeration is the union of the fonts that are loaded in private and
shared font directories.

The VM statistics are less concrete in Display PostScript than they are
in printers because the DPS system doesn't know in advance the maximum
amount of storage the operating system will give to it.


- Terry Weissman	weissman@wsl.dec.com	...!decwrl!weissman