🚀 go-pugleaf

Ok, I finally found the answer to the findfont/spaces issue. Adobe Tech note #5088 states spaces my not be used in the FontName which is used with the findfont cmd.

Regardless, it sounds like I've got to, as you've stated, embed the font to avoid relying on application dependencies in the Postscript interpreters.

I agree with you that this font embedding task is looking like a huge job. Maybe we can leverage the printer driver idea.

As a test, I installed a postscript printer driver and printed to a file. Interestingly, it converted the "Bookman Old Style" font name to "Bookman-Light" which displayed fine using Ghostscript on one of our unix boxes.

I then tried converting this Postscript file to an EPS file and failed in all cases to import. I figure there are too many differences between Postscript and EPS to make this an easy task.

Ok, so I then modified my Windows EPS file, which was failing with original name to "Bookman-Light" instead and findfont immediately worked.

So, how did the Postscript Printer driver know to convert the "Bookman Old Style" name to "Bookman-Light"?

Once I figure that out, I may be on my way.

landon