RE: Working with non-existent fonts
> > Suppose you have to work with a document or book that uses >> fonts you do not have: you manually substitute fonts you do >> have, *and* tell FrameMaker to forget the missing ones, to >> get rid of all the irritating error messages. > >Well, you shouldn't have to manually substitute fonts. If you can live >with the alerts, Remember Missing Font Names takes care of the problem. >If not, you can make the appropriate substitutions automatic (at least >on the Windows side) with the proper entries in the Font Options portion >of the maker.ini file. You are of course right in your first point, but the issue is that of working with a book with many chapters for many weeks: the accumulated time wasted clicking the 'Ok' button is considerable, not to mention the irritation factor. For you second point, yes, for sure - but I'm on a Mac. >The trick, of course, is coming up with the proper substitutions. See >the manuals (PDFs) _Customizing FrameMaker_ and _Working on Multiple >Platforms_ for hints, but they aren't as clear and complete as one might >hope. :-} I looked. My brain fried. > > This discovery came about due to variations in the names of >> Times New Roman fonts between Mac and PC platforms >> (TimesNewRomanPS, TimesNewRomanPSMT). > >You can probably resolve a name variation like this with an entry in the >[WindowsToFrameFontAliases] section of maker.ini. Yup - if I had a maker.ini. >The hard part is figuring out the right names to use. It would be nice >if there were a list of FrameFont names somewhere, with their common >Windows and Mac equivalents, but I havn't seen one. That would be good, yes. In Another Part of the Forest, I'm facing the same issues with Frutigers. >...[loads of good stuff] > >That's the theory, anyway... :-) Thanks for the update. As so often with FrameMaker, there are many ways of skinning the cat. -- Steve ___ You are currently subscribed to Framers as [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: Working with non-existent fonts
Steve Rickaby wrote: > Suppose you have to work with a document or book that uses > fonts you do not have: you manually substitute fonts you do > have, *and* tell FrameMaker to forget the missing ones, to > get rid of all the irritating error messages. Well, you shouldn't have to manually substitute fonts. If you can live with the alerts, Remember Missing Font Names takes care of the problem. If not, you can make the appropriate substitutions automatic (at least on the Windows side) with the proper entries in the Font Options portion of the maker.ini file. The trick, of course, is coming up with the proper substitutions. See the manuals (PDFs) _Customizing FrameMaker_ and _Working on Multiple Platforms_ for hints, but they aren't as clear and complete as one might hope. :-} > This discovery came about due to variations in the names of > Times New Roman fonts between Mac and PC platforms > (TimesNewRomanPS, TimesNewRomanPSMT). You can probably resolve a name variation like this with an entry in the [WindowsToFrameFontAliases] section of maker.ini. Of course, save a backup of maker.ini before making changes. And stop/restart FM after making changes. The hard part is figuring out the right names to use. It would be nice if there were a list of FrameFont names somewhere, with their common Windows and Mac equivalents, but I havn't seen one. The entries in the [WindowsToFrameFontAliases] section specify the Windows font name on the left and the corresponding FrameFont name (which is not the same as the Mac name) on the right, with placeholders for the variations. Assuming that "TimesNewRomanPSMT" is the correct Windows name of your font, try adding this line: TimesNewRomanPSMT, *, *=Times New Roman, *, *, * I think the entry to the right of the equal sign is the correct FrameFont entry. If it is, and if FM on the Mac uses the same FrameFont name, that should solve the problem. That's the theory, anyway... :-) Good luck! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Working with non-existent fonts
> > Suppose you have to work with a document or book that uses >> fonts you do not have: you manually substitute fonts you do >> have, *and* tell FrameMaker to forget the missing ones, to >> get rid of all the irritating error messages. > >Well, you shouldn't have to manually substitute fonts. If you can live >with the alerts, Remember Missing Font Names takes care of the problem. >If not, you can make the appropriate substitutions automatic (at least >on the Windows side) with the proper entries in the Font Options portion >of the maker.ini file. You are of course right in your first point, but the issue is that of working with a book with many chapters for many weeks: the accumulated time wasted clicking the 'Ok' button is considerable, not to mention the irritation factor. For you second point, yes, for sure - but I'm on a Mac. >The trick, of course, is coming up with the proper substitutions. See >the manuals (PDFs) _Customizing FrameMaker_ and _Working on Multiple >Platforms_ for hints, but they aren't as clear and complete as one might >hope. :-} I looked. My brain fried. > > This discovery came about due to variations in the names of >> Times New Roman fonts between Mac and PC platforms >> (TimesNewRomanPS, TimesNewRomanPSMT). > >You can probably resolve a name variation like this with an entry in the >[WindowsToFrameFontAliases] section of maker.ini. Yup - if I had a maker.ini. >The hard part is figuring out the right names to use. It would be nice >if there were a list of FrameFont names somewhere, with their common >Windows and Mac equivalents, but I havn't seen one. That would be good, yes. In Another Part of the Forest, I'm facing the same issues with Frutigers. >...[loads of good stuff] > >That's the theory, anyway... :-) Thanks for the update. As so often with FrameMaker, there are many ways of skinning the cat. -- Steve
Working with non-existent fonts
Steve Rickaby wrote: > Suppose you have to work with a document or book that uses > fonts you do not have: you manually substitute fonts you do > have, *and* tell FrameMaker to forget the missing ones, to > get rid of all the irritating error messages. Well, you shouldn't have to manually substitute fonts. If you can live with the alerts, Remember Missing Font Names takes care of the problem. If not, you can make the appropriate substitutions automatic (at least on the Windows side) with the proper entries in the Font Options portion of the maker.ini file. The trick, of course, is coming up with the proper substitutions. See the manuals (PDFs) _Customizing FrameMaker_ and _Working on Multiple Platforms_ for hints, but they aren't as clear and complete as one might hope. :-} > This discovery came about due to variations in the names of > Times New Roman fonts between Mac and PC platforms > (TimesNewRomanPS, TimesNewRomanPSMT). You can probably resolve a name variation like this with an entry in the [WindowsToFrameFontAliases] section of maker.ini. Of course, save a backup of maker.ini before making changes. And stop/restart FM after making changes. The hard part is figuring out the right names to use. It would be nice if there were a list of FrameFont names somewhere, with their common Windows and Mac equivalents, but I havn't seen one. The entries in the [WindowsToFrameFontAliases] section specify the Windows font name on the left and the corresponding FrameFont name (which is not the same as the Mac name) on the right, with placeholders for the variations. Assuming that "TimesNewRomanPSMT" is the correct Windows name of your font, try adding this line: TimesNewRomanPSMT, *, *=Times New Roman, *, *, * I think the entry to the right of the equal sign is the correct FrameFont entry. If it is, and if FM on the Mac uses the same FrameFont name, that should solve the problem. That's the theory, anyway... :-) Good luck! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
Working with non-existent fonts
I've just discovered something useful, although it's probably second nature to a lot of you: FrameMaker can handle missing fonts as if they were actually installed. Suppose you have to work with a document or book that uses fonts you do not have: you manually substitute fonts you do have, *and* tell FrameMaker to forget the missing ones, to get rid of all the irritating error messages. Obviously, FrameMaker allows you to later import and re-apply the paragraph tag definitions that use the missing fonts from the original document. However, having done that, you can if necessary manually apply the non-existent fonts to new paragraph tag definitions: FrameMaker handles the non-existent fonts exactly as if they were present, even if it's currently applying a substitute font. This discovery came about due to variations in the names of Times New Roman fonts between Mac and PC platforms (TimesNewRomanPS, TimesNewRomanPSMT). -- Steve ___ You are currently subscribed to Framers as [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
