[Fontforge-devel] Minor bugs in PrintFont Postscript and PDF output

[Peter D. <pd...@co...>]

I've encountered the following two minor bugs (or in TeX-speak
"infelicities") in recent versions of fontforge
Tested on Gentoo Linux, fontforge built from source 5-Dec-2005.

1) the postscript output either from the gui
(Print..."fontdisplay"...either to ps file or to lp) or a script
(PrintSetup(0|3),PrintFont(0)) gives postscript containing "%%Pages:
atend".  This should be "%%Pages: (atend)".  Without the parens the file
doesn't emerge from my printer without manually pressing the formfeed
button.  This breaks my attempts to print out, e.g., the font tables for
*.pfb.

The fix is to edit line 997 in print.c to read "fprintf...(atend)\n".

2) Print to PDF either gui or script omits the fontname at the top of
the fontdisplay.  This was probably not intended and makes it difficult
to tell which printed page goes with which font.

Other than that, I still love fontforge.

Best wishes for the New Year,

-peter

P.S. -- I had a heck of a time tracking down item (1) -- recheck print
queue setup; try to find where to force a formfeed (you apparently can't
with CUPS); gs didn't complain about the postscript.  Finally tried
(windows) gsview which griped about atend breaking DSC.  Is there a
postscript validator (pslint??) around somewhere.  GSView is about as
picky as I know of...