Re: cleaning out old fonts

["Mario Ruggier" <Mario.Ruggier@xxxxxxx>]

If you have not tried the following, maybe it will help.

Make a copy of a troublesome file. Gut it of all contents 
and, as much as possible, the formats, i.e. select all in flow
and cut, and delete all para and char formats in the catalogs.
Also maybe the table formats. 

Then save and reopen the gutted file and see if you have the
same complaints. In this case you can examine the MIF for it,
persumably it will be simpler. If no complaints copy the original
contents into the gutted file and see if you get the font
complaints again. If you do, they are coming from the contents 
or in the local definitions of some formats, presumably the 
overrided tables. Try and isolate a type of table that is 
giving these problems and define a new tag to correspond
to the overridden table. Then apply the new tag to the old
troublesome table...

Also try playing with yje new 5.5 feature of
Create and Apply formats... under File/Utilities.

mario


+ Deborah, thanks for the advice. Unfortunately, I've had "Remember
+ Missing Fonts" unchecked for some time. That gets rid of
+ everything except old fonts in tables. You sound like you really
+ know your stuff. Got any other ideas?
+ 
+ I've also followed Jay Smith's advice (thank you Jay!): I've
+ double-checked that the old, unused tags that have the unwanted
+ fonts REALLY don't exist anywhere in the doc--Body, Reference, or
+ Master pages. Then I've re-created the four or five old tags that
+ turn up in the MIF with the old fonts but I've re-created them
+ using current fonts and definitions and done Update All. Looking
+ in the MIF, I found that those tags STILL had the old fonts.
+ 
+ All occurrences of these tags/fonts are in tables. As far as I can
+ tell, they're being used to create "ghost" columns. I've got
+ three-column tables that have 8 or more columns defined in the
+ MIF! And the ghost columns have, of course, the ghost tags and
+ ghost fonts. I'm feeling pretty haunted 'long about now. 
+ 
+ These ancient tags and fonts seem to be locked away in parts of
+ the table that don't really exist. I'm pretty good with
+ FrameMaker, I've used it for years and I like it a lot. And
+ generally I have a fairly good time solving problems. But this one
+ has really got me. I'm trying to clean up the templates and doc
+ set so that we can distribute them to contractors and outsources.
+ I'm almost there. All I have to do is bust the ghosts.
+ 
+ Thanks to all...
+ 
+ Rhea
+ Lead Technical Writer, InterBase Software Corp.
+ 
+ 
+ "Snavely, Deborah" wrote:
+ > 
+ > Rhea,
+ > 
+ > >What to do? I can't search for either the tags or the fonts in the
+ > >native FrameMaker file, because they're not accessible in that
+ > >form. The MIF file is intricate, and I'm not at all confident that
+ > >I could remove the unwanted font calls without munging the file.
+ > >And, there are a LOT of them. These are old docs. They've been
+ > >around.
+ > >
+ > >FWIW, I'm using FrameMaker 5.5.2 on NT4 with Adobe Type Manager
+ > >Deluxe. I think that the docs have always been on Wintel
+ > >platforms.
+ > 
+ > On any version of Frame (4.0 and up for Mac, 5.5 and up for Windows) that
+ > offers the "Remember Missing Fonts" preference, you can quickly remove any
+ > truly unused font names with the following simple procedure (per file, but
+ > it's fairly quick):
+ > 
+ > 1. With the file closed/ open Frame Preferences and un-check Remember
+ > Missing Fonts.
+ > 2. Open the file or files you want to clean up, respond to the dialog box
+ > about missing fonts, then save and close the file/s.
+ > 3. Open the file/s a second time to check that you do NOT get the missing
+ > fonts dialog again.
+ > 4. When you're done with all files (or for the day, I don't recommend
+ > leaving Frame Prefs set this way for any length of time), open Prefs and
+ > check Remember Missing Fonts.
+ > 
+ > As always, do one or two test files to make sure this procedure does what
+ > you want. Note that uncataloged paragraphs or characters on reference and
+ > master pages may contain fonts not in your current styles but could cause
+ > some past-style fonts (ghosts, I call 'em) to remain in your document.
+ > Cleaning up document templates to delete such ghosts is a fine art, and an
+ > action I recommend whenever you make major style changes to dept/corporate
+ > docs (you're using templates, yes?). Once ghost fonts and other elements ar
e
+ > gone, there are two or three fairly clean ways to apply the new styles to
+ > older documents being revised or updated. For new docs, it's almost always
+ > easiest to clone a blank template or boilerplate (based on the current
+ > template) and assemble docs from there.
+ > 
+ > Good luck!
+ > 
+ > Deborah Snavely
+ > Senior Technical Writer
+ > consulting at Visa
+ > standard disclaimers apply
+ > 
+ > ** To unsubscribe, send a message to majordomo@omsys.com **
+ > ** with "unsubscribe framers" (no quotes) in the body.   **
+ 
+ ** To unsubscribe, send a message to majordomo@omsys.com **
+ ** with "unsubscribe framers" (no quotes) in the body.   **


Mario Ruggier
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Information, Process and Technology Group         Bat. 1, R-017
IT Division, CERN                               +41 22 767 8072
CH-1211 Geneva 23                         mario.ruggier@cern.ch *
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://ptsun00.cern.ch/~ruggier/
http://framemaker.cern.ch/

* please email all documentation-related queries to 
  docsys@ptsun00.cern.ch. 



** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **