The MIF wash certainly sounds worth a shot! I've also noticed that appearance of the warnings is unpredictable. Sometimes these files will open with warnings, sometimes without--even after not making any changes to the files themselves (closed without saving).
Thanks all, Karen On Fri, Apr 12, 2013 at 11:31 AM, Fred Ridder <docudoc at hotmail.com> wrote: > > At that point I figured I'd waste a little more time and search the MIF. > Imagine my surprise when UltraEdit turned up *zero* instances of either > font name (or any significant part of either name) anywhere in the MIF > file. Apparently, the MIF export filter recognized the font names as > extraneous or anomalous and stripped them out of the file. All I had to do > is open the MIF file and re-save it in FrameMaker binary format, and I was > good to go. > > So the bottom line is, if turning off "remember" doesn't work, and you > can't find the unavailable fonts in the FrameMaker file, try a MIF wash as > the next step before spending any time searching the MIF file and figuring > out the syntax well enough to delete the font references without breaking > anything. > > Fred Ridder > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130412/b91868a7/attachment.html>
