(register)   username:   password:  

Community KB :: DITA / FrameMaker

A collection of tips and troubleshooting information. Feel free to register and add your own items.

Tags:                                        
Keywords: 

FMN DITA .. refers to the DITA support that is provided by default in FM9 and FM8.

DITA-FMx .. is a plugin that provides extended DITA authoring support for FM9, FM8, FM7.2 and FM7.1. More info...

Submitted by: Scott Prentice (2008-12-08)

TAGS:  Authoring, FM8 DITA, DITA-FMx 0.0, DITA-FMx 1.0, FM 7.1, FM 7.2, FM 8.0
SUMMARY:  "Zapfdingbats Font Family not available" message in console
ISSUE:  I keep getting the following message in the console window each time I open a DITA file ..

-------------------------------------------------------------------
The "Zapfdingbats" Font Family is not available.
  "Adobe Pi Std" will be used in this session.
The "Courier" Font is not available.
  "Courier New" will be used in this session.
The "Zapfdingbats Regular" Font is not available.
  "AdobePiStd" will be used in this session.
-------------------------------------------------------------------
SOLUTION:  This general issue is the result of opening an FM file that references a font that's not available on your system. The first thing to check is that your structure application template file doesn't reference any unavailable fonts. Once you've done that, there is one other file that may contain fonts .. the FrameMaker/Structure/entfmts file. This file is opened each time an XML file is imported. You might also check your structapps.fm file as well as your structure application "stub" files. (Also, if your r/w rules file is an FM binary as opposed to a text file, it may also be the cause.)

To cleanse these files of references to missing fonts, you can open the file and locate paragraph or chater style definitions that reference these fonts and change them to reference a more appropriate font. This is often very difficult, so you may need to ..

1) Make a backup of the file.
2) Save the file to MIF.
3) Open the MIF in a text editor, and search for and replace the bad font names. When you locate a bad font name, you'll need to change it to the proper name of a more appropriate font. If you are unsure of how to do this, locate the MIF structure of the font name you want to use and use the full name as shown.
4) Save the MIF file and open it in FrameMaker, then save it to the original filename.

To fix my particular situation, the entfmts file was the problem. All I needed to do was to change the default para font for the "Bullet" para style to "Courier New" to fix the Courier problem .. then to get the Zapfdingbats, I had to MIF out the file, search for "Zapfdingbats", and replace it with "Adobe Pi Std".

Unfortunately, this is system dependent so each person would need to change the file based on the fonts available on their system .. yuck.