Remapping TrueType Fonts in Framemaker 9.0 maker.ini

[ashrae-editor]

Greetings, forum community.

When attempting to embed non-base 14 fonts in PDFs using Pitstop v7.52, I receive a notice that no TrueType version could be located.

I believe (please correct me if I'm wrong) that the solution is to remap the unavailable font (in this case Arial, Bold) to an available font (Helvetica, Bold) in the Framemaker maker.ini file.

My entry in the maker.ini file is as follows:

Arial, Bold, *, *=Helvetica, Bold, *, *, *

Alternately, I could use Arial MT.

Neither, however, seems to work as I've mapped it. Upon generating a PDF, I still receive an error from Pitstop saying it was unable to embed the font.

Can anyone easily see where I may be messing up and offer a solution?

Thanks, as always, and best regards.

JMW

[Mike Wickham]

I'm not sure I follow your problem. FrameMaker is perfectly capable of

embedding Type1 (whether Base 14 or not), OpenType, and TrueType fonts. So

it sounds like your problem is a Pitstop problem and you are asking for help

in the wrong place.

On the other hand, I'm not sure you've made your font mappings correctly, as

the example in maker.ini shows the font angle (italics/oblique/etc.) as the

first entry, not font weight. You might try this instead:

Arial, *, Bold=Helvetica, *, Bold, *

Finally, I was looking into Pitstop recently and found that it is not

compatible with Acrobat X. So if Pitstop is using Acrobat to create its

output and you've recently upgraded to Acrobat X, perhaps you are running

into one of the incompatibilities.

[Michael_Müller-Hillebrand]

JMW,

Like Mike I feel I don’t get what you need. From my experience maker.ini font mapping was sometimes important in pre-Unicode times and should be avoided if possible, because it will create problems if you have to work with the same files on another rmachine which might not have the correct settings. I have not come across a FM9 user working with maker.ini font mapping neede for more than  a short migration period from some old PostScript fonts to a more modern version.

Please describe your situation, what you want to achieve, and what you currently get unexpectedly.

- Michael

[ashrae-editor]

Mike and Michael,

Thank you both for your time, attention, and expertise. It's very possible I misunderstand my problem and have misdiagnosed the cure accordingly.

In a nutshell, we are unable to embed certain fonts (most typically Arial and Times) during preflight using Enfocus Pitstop on PDFs generated with the default PDF printer in Framemaker. Is there a better way to embed fonts without Pitstop?

Best,

[Mike Wickham · Accepted solution]

Unfortunately, I'm only vaguely familiar with Pitstop. I used it for a short

time years ago, but remember little about it. But I do recall that it is an

Acrobat plugin and therefore uses Acrobat to produce the PDF. So check your

"PDF presets" (.joboptions settings) in Acrobat Distiller because there is a

dialogue that lets you specify fonts that will never embed. Some of the

default Adobe PDF presets, including (if I remember right) even the Standard

options, have some fonts set in there to never embed (it assumes that

everyone has them on their computer already) and that may include the fonts

you are having problems with. If this is the case, just move the fonts from

the "never embed" column into the "always embed" column to fix your problem.

Then save as a custom PDF preset to use in the future. You can also save the

changes to the current preset, but I seem to recall that Acrobat updates

have recently started resetting some user settings without permission. So

you may find that changes you made have disappeared in the future if you

don't save as a custom preset!

[ashrae-editor]

Mike,

Forcing the fonts to always embed in job options may have solved my problem. First file was successful. Going to run it on the rest of this batch now. I'll report my findings.

[ashrae-editor]

Mike,

Forcing embed from joboptions was exactly the right fix. Thanks for making the correct recommendation in spite of my poorly articulated diagnosis, and thanks to everyone who posted for taking the time to offer help.

Very much appreciated.

Best regards,

JMW