#4601 ghostscript-9.18-3 to add upstream font handling fixes

[Jack Howarth]

The attached info and patch file for ghostscript-9.18-3 adds the changes from upstream...

diff -uNr ghostscript-9.18.orig/Resource/Init/gs_fonts.ps ghostscript-9.18/Resource/Init/gs_fonts.ps
--- ghostscript-9.18.orig/Resource/Init/gs_fonts.ps     2015-10-05 04:21:11.000000000 -0400
+++ ghostscript-9.18/Resource/Init/gs_fonts.ps  2016-01-29 08:17:32.000000000 -0500
@@ -183,7 +183,7 @@
     } if
     {           % Stack: key file
                 % Protect ourselves against syntax errors here.
-      dup { token } stopped { pop //false exit } if
+      dup { token } stopped { //false exit } if
       not { //false exit } if               % end of file
       dup /eexec eq { pop //false exit } if       % reached eexec section
       dup /Subrs eq { pop //false exit } if       % Subrs without eexec
@@ -410,7 +410,7 @@
             pop
           }
           {
-            3 -1 roll pop
+            counttomark 1 add -1 roll pop
             not { dup 0 get } if  % stack: (newname) [ (name) (path) ]
             % DEBUG { (  found ) print dup print (\n) print flush } if
             % add entry to the fontmap

which eliminates the gs crashes which I reported in http://bugs.ghostscript.com/show_bug.cgi?id=696554 that appear to only show up on darwin.

[Jack Howarth]

Info file for ghostscript-9.18-3 to add upstream font handling fixes

[Jack Howarth]

Patch file for ghostscript-9.18-3 to add upstream font handling fixes

[Jack Howarth]

Upstream analyzed the origin of the bug as...

It's a dfont file, which Postscript (and thus Ghostscript) does not support.

It's possible we could add a non-standard extension to support dfonts, but a)
this stuff is written in Postscript, and it is not really desirable to have
platform specific stuff in Postscript, and b) I understood even Apple were
shifting away from using dfont files.

So, for now, it's best just to handle the incompatibility gracefully.

[Hanspeter Niederstrasser]

In 10.9 tree.