🚀 go-pugleaf

>I don't think a printer has anything to do with this. I'm writing an Encapsulated Postscript file for import into other applications.

Then I feel I have to say you are missing the point completely.  That
EPS file is eventually embedded in a PostScript file and sent to a
printer.  That EPS file therefore has to be able to find a font in the
printer.

So, I repeat - what are you doing to enable that font to be found?
What certainly WON'T happen is that Publisher will read your file,
look for findfont instructions, and take care of things.
>
>I know the OpenType font is installed because I can use it in Windows ...

Yes, but so what?  That isn't where the findfont is executed.

I think you may be expecting more of an EPS than actually happens.
UNLESS, you are adding suitable DSC comments - I asked this before but
you didn't comment.
>
>I've found that without exception, *every* font I use that has no spaces in the name works fine while *every* font I use that has spaces in the name fails. I've tried 30-40 fonts now.

A level 3 printer has over 100 fonts built in.

>So far, I haven't found anyone who has sucessfully done this using the Encapsulated Postscript language.

To work well, fonts are embedded in the EPS. To work less well, you
use DSC comments.

Aandi Inston