Skip to main content
Bill_at_HNS
Bill_at_HNS
Known Participant
July 19, 2012
Answered

Is it possible to remove unseen font references from an .fm file?

  • July 19, 2012
  • 1 reply
  • 1319 views

We have used a Framemaker book template that was created about 15 years ago to create technical manuals. We've modified this template many times. It's pretty complex, but the main purpose is to keep the appearance, structure, etc., consistent among mulitiple writers. It works well.

We originally used Times and Helvetica as the primary fonts. Now we're using other fonts. It was a tedious job to replace all the instances of Times and Helvetica in the Paragraph and Character designers.

Here's the problem:

Theoretically, these fonts should be gone.

But if I open the template files, even with no content, I get this message in the Frame Console:

xxx Font is not available.               (where xxx is Helvetica or Times or variants)

zzz will be used in this session.

I didn't see this problem until today, because my computer was just reimaged by IT and so I no longer have these (Postscript) fonts installed. Frame thinks these fonts are still used in the various .fm chapters. But, it should not need them.

I got to thinking about how old our template is and so I "examined" one of the template files, chapter.fm. I renamed the file chapter.txt and was able to open in with Notepad. I found about 40 references to Helvetica buried in Frame's code (some of it "machine language"). This was certainly revealing. My real question is, is there anyway to purge the files of these font references? The file structure is totally complex and I would not think of editing these files. I'm sure this would not work, and Adobe would probably arrest me if I did.

Is there a MIF editor or similar that could do this?

I could reinstall these fonts as a workaround, but they're really not used and so I would rather purge the font references if I can.

Someone may say: Create a new template. If we did, we would want it to be the same as the one we have. It is complex enough that we just cannot take the time to do this. It would take days and days.

Thanks for any help.

This topic has been closed for replies.
Correct answer Arnis Gubins

Bill,

You don't say what version of FM that you're using. In FM10, there's a new Font replacement tool that will let you remap the "missing" fonts to anything else.

The alternative is to make permanent the alternate mappings for the Helvetica and Times by changing the Preference "Remember Missing Font Names" and saving the file. This will change those to whatever is set in your maker.ini [UnknownToKnownFontMap] section.

[Added] Once you've saved the file with this preference turned off, you can turn it back on again the next time you've opened the file. This will blow away the old references.

1 reply

Arnis Gubins
Arnis GubinsCorrect answer
Inspiring
July 19, 2012

Bill,

You don't say what version of FM that you're using. In FM10, there's a new Font replacement tool that will let you remap the "missing" fonts to anything else.

The alternative is to make permanent the alternate mappings for the Helvetica and Times by changing the Preference "Remember Missing Font Names" and saving the file. This will change those to whatever is set in your maker.ini [UnknownToKnownFontMap] section.

[Added] Once you've saved the file with this preference turned off, you can turn it back on again the next time you've opened the file. This will blow away the old references.

Bill_at_HNS
Bill_at_HNSAuthor
Known Participant
July 20, 2012

We use FrameMaker 9.

Very interesting.

When you say, "This will blow away the old references," do you think it would get rid of the numerous references that are unseen in the .fm file (unless you look at it in Notepad)? Most of all we don't want to see the Frame Console messages (referenced above) every time we open a file.

Bob_Niland
Community Expert
Bob_NilandCommunity Expert
Community Expert
July 20, 2012

> ... do you think it would get rid of the numerous references that are unseen in the .fm file ...

It can't get rid of the font invocations that are coming in with imported-by-reference objects, such as from DWG, DXF, EPS, and PDF, as well from formatted text insets from other .FM files.

It may or may not be able to remove such references from objects imported by copy-into-document.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices