🚀 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.

I know the OpenType font is installed because I can use it in Windows and see it listed in the font folder. My test app (MS Publisher) is able to use all of the fonts as well from it's user-interface so I know it's not a problem on that end.

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.

Too much of a coincidence for me. It's becoming clear that the problem is not font availability, but rather simply that there's no way to specify a font name whith embedded spaces in Postscript because it can't parse the name properly... probably because Postscript uses spaces as a special character for parsing seperate tokens, as it does with all of it's commands.

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

Thoughts?