🚀 go-pugleaf

Karen,

A couple of issues that I see in your situation. 

First, when creating postscript files for distilling, you should only
use the Adobe PDF printer instance to generate the postscript, as
postscript output is device-dependent. (Aside: distilling the
postscript on an other machine/configuration is actually using
Distiller in a server "mode" and you really should consult the terms
of the EULA - license - that Adobe provides with their products.) Your
FM license on Windows installs a version of Distiller (albeit somewhat
crippled) and that is what you are legally obligated to use unless you
have a bona fida server license on your Mac.

Secondly, Distiller needs to know where the fonts are located on your
machine. When the postscript is created, FM just inserts the reference
to the font on output and expects Distiller to be able to find it.
Distiller's joboptions for Fonts give you the options of cancelling
the job outright when a font isn't found, warning and continuing
(giving you substitutions) or simply ignoring the missing font (and
possibly creating "interesting" results). Distiller has Font Locations
setting that tells it where to look for fonts. It's a totally manual
process and does not automatically use the system information.

When printing to the AdobePDF printer instance in the default Windows
configuration, FM just pipes a postscript file through the backdoor
routine (the PDF port) into the supplied Distiller and attempts to
create a PDF using the joboptions specified. If you don't have the
Helvetica Narrow installed on your Windows machine, then you will get
the job failures or substitutions as you describe.

The solution is to either get the Helvetica Narrow font for Windows or
use a different entirely in your template and documents.