CompuServe Messages

Even when all the family-level ID numbers are harmonized (they should be right out of the box, if they are NFNT fonts) there may still be font number conflicts at the second, intra-family level (according to my sources, the primary numbers are FONDs, and the secondary numbers are the NFNTs). Font/DA Mover arbitrarily assigns these secondary numbers, and if you are using multiple suitcases, conflicts will crop up which must then be harmonized. NOTE: The second-level, intra-family numbers only affect screen display, not printing. They are used to call the proper screen font when you have chosen the plain version and apply, say, italic from the style menu or dialog check box instead of choosing the italic version from the menu. For example, the Adobe Eurostile font # is 14845. Each point size and style has a second-level number. In the case of Eurostile, 10-pt plain, mine is numbered 2936, while the 10 pt. plain + italic is 10177. So, the Eurostile Oblique font # is 14844. The 10 pt plain # is 10177, the same as for Eurostile plain + italic ~ this is intentional, and not a font conflict. This allows it to be linked when you choose Eurostile from the menu and add the italic style to it. Font display conflicts arise if there is a font in another suitcase with this same secondary number. It will show up in funny ways, as we found. For example, in PageMaker at 100% view Garamond + Bold 20 point will be displayed as specified. Switch to 50% view and it could display Belwe Bold Condensed. This is because Garamond 20 + Bold and Belwe Bold Condensed xx point have the same secondary number. In any case, harmonizing the fonts with Font Harmony will take care of this. Anytime you add a new font to a suitcase with Font/DA Mover, you must reharmonize the suitcase with any other suitcases which you want to have open at the same time.