🚀 go-pugleaf

In article <9204100138.1.UUL1.3#5127@aladdin.com> ghost@aladdin.COM (L. Peter Deutsch) writes:

>  > When I try to load a .pfb file (like
>  > Adobe's por_____.pfb (palatino-roman)) gs complains with a screenfull
>  > of numbers (0's and 3's) and a complaint beginning ``/undefined''
>  
>  This is not a simple or obvious problem.  Someone else has reported
>  it, and I'm working on it right now.  I haven't any idea yet what
>  causes it.
>  
>  L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306

For what they are worth, here are some observations I made with
respect to the problem, using the real mode MSDOS executable of
Ghostscript2.4 (gs.exe):

(a) I printed a document to disk using the new Windows 3.1 PS driver.
The driver downloads an error handler into the print-file which
will print out stuff when things go haywire, e.g. when the interpreter
can't successfully load the font file. Now, the interpreter has to
print these messages and it does so (hold your breath) using the very
same font it choked on.(??)

(b) While the interpreter rejects some (but not all) dubious converted
binary font files, it will also barf at some (but not all) Adobe fonts
(see first quote).

(c) The protected mode version of gs24 (gs386.exe) will load all of my
fonts, _including_ those rejected by gs.exe with no problems at all.
(I thought both versions used the same code, or do they?)  Alas,
gs386.exe and Windows will not coexist (Unix people stop sniggering
:-} ).

I am not complaining, but I would like to see a fix...

th.










--
Thomas Plass                                    | University of Edinburgh
Fax:   +44 31 650 4587                          | Centre for Cognitive Science
ARPA:  thomas%cogsci.ed.ac.uk@nsfnet-relay.ac.uk| 2 Buccleuch Place
JANET: thomas@uk.ac.ed.cogsci                   | Edinburgh EH8 9LW Scotland