[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Framers2" <framers@xxxxxxxxx>, "Framers1" <Framers@xxxxxxxxxxxxxx>, "Fields, Evelyn M (Evelyn)** CTR **" <emfields@xxxxxxxxxx>
Subject: Re: "Document... uses unavailable fonts" error
From: "Rick Quatro" <frameexpert@xxxxxxxxxxxxxx>
Date: Thu, 16 Sep 1999 13:16:43 -0400
References: <4624C75E76CBD111B43500805F6FA8C1028AEF18@pai820exch001u.micro.lucent.com>
Sender: owner-framers@xxxxxxxxx
Evelyn, I respectfully disagree. The default should remain Remember Missing Font Names. This is the safest approach. On Windows and Mac this setting is "sticky" so that if you uncheck it, it will stay unchecked from session to session. On Unix with multiple licenses, the setting may not be "sticky" because you are usually served a different license every time you launch Frame. A more convenient approach would be a "Replace Missing Fonts" command after you open the file. This would eliminate having to dismiss the warning, close the file, change the preferences, reopen the file, dismiss the new warning, and save the changes. Rick Quatro Carmen Publishing 716 659-8267 frameexpert@mindspring.com FrameScript Information at http://www.mindspring.com/~frameexpert > Framers -- > > I think there *is* an easier way to fix this problem: > > Open the offending file. Select File->Preferences.... In the dialog box, > make sure that the last checkbox labeled "Remember missing font names" is > unchecked. Save the file. Open it again, and hopefully your error messages > will be gone. (If not, repeat the procedure and try again.) > > To Adobe, if you're listening... it would make sense for this checkbox to be > unchecked by default to avoid this sort of cross-platform problem. I and > many of my colleagues have bumped into this issue. > > Regards > ________________________________ > Evelyn Fields > Technical Writer, Lucent Technologies > > _____________________Original Message___________________________ > Subject: Re: "Document... uses unavailable fonts" error > From: Grant <rowan@lgcy.com> > Date: Wed, 15 Sep 1999 19:12:21 -0600 > > two suggestions: > 1. Look on your reference pages, as well as your master pages. > If that doesn't find them > 2. Save the template as MIF, and search on the font name using a text > editor. > > You are right, though... there should be an easier way! > > Grant > > At 01:49 PM 9/13/1999 -0700, you wrote: > >I filtered some files over from MS-Weird and created a template for > a > >Framemaker book (actually, a contractor did it for me). > > > >Every time I try to open any document in the book *or* the template > I get > >this "Document... uses unavailable fonts" error: > > > <snip> > > > >I have scoured the template with a fine tooth comb and changed every > single > >instance of these offending fonts to variants of Times New Roman or > Arial. > >The bottom line is that I (apparently) cannot print my book until I > resolve > >these errors. I can save individual files as PDF, but not the whole > book. FM > >always returns an error trying to open these files. I think it's > related to > >this font problem. > > > > > >Adobe, if you're listening, I have to say, this is one brain-dead > problem > >for a "world-class" publishing tool to have. I (apparently) can't > even > >search on font name to find the offending instances. > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **