![]() It seems that FAP is not shutting the fonts down when the computer is shut down. Hmm, there's contradicting statements here. Plus you know you'll always be using the correct one. It eliminates the need to have your font manager try and juggle between like named fonts. So I just deleted Helvetica, Courier and any other commonly used type faces from the /System/Library/Fonts/ folder and permanently activated Type 1 PostScript versions instead by placing them in the /Library/Fonts/ folder. I do prepress work, where any good designer will always use PostScript fonts. dfont version in the System folder and activates the one you want. Then when you activate a PostScript version of Helvetica, Suitcase or FAP deactivates the. ![]() The idea behind Suitcase and FAP is to allow you to leave, for example, Helvetica.dfont installed by OS X where it is. Mostly because it simply doesn't (or didn't) work as well as it's described to. That is in reference to Suitcase more than anything. ~Bee mentioned that I wrote you shouldn't let your font manager control the fonts in the /System/Library/Fonts/ folder. In short, you need to keep any font manager from using a Fonts folder as a location to store the fonts you activate. Deactivating the font(s) in both FAP and Font Book still won't turn them off. As described above, because Font Book uses a Fonts folder, the font(s) will always be active once there. FAP to the font library you designated in the program, Font Book to the Fonts folder chosen in its preferences. Any time you double click a font, both FAP and Font Book will activate and copy the font(s). If this is the case, call up the panel that shows the "Destination Library:" option, and choose, or create a new target folder that isĢ) Is Font Book still on your drive? If so, delete it. As far as the OS is concerned, they're still active due to their location. So it won't matter, or help if you deactivate the fonts in FAP. As far as the underlying Unix system of OS X is concerned, anything in one of the three Fonts folders on your drive is automatically "on". If you have it set to use the /Library/Fonts/ folder, or the Fonts folder in your user account, then that's an issue. Normally to your user account within (I think) the Documents folder. They can import them into the final library when they’ll be away from the computer for a few minutes.1) How do you have FAP set up? FAP copies all fonts you activate to a folder you designate in it's preferences. If users need the fonts “right now”, import them into a new library. This is much faster than manually comparing fonts in Suitcase and the Finder. Since FontAgent Pro doesn’t import duplicates, users can simply add new fonts to a library and FAPro will figure out if they need to be added. To anyone who depends on their fonts, that’s a small price for a pristine font library. On a dual 1GHz G4, it imported the entire Font Folio 6 CD in under 6 minutes. – organizes the fonts into alphabetical and family folders – names the suitcase file with the name used by OS X – creates new suitcase files with one font style per suitcase – only adds non-duplicate fonts to an existing library The reason Suitcase is “fast” is because it doesn’t do anything - it just creates a pointer. FAP 2.1 is still slow in importing fonts. In the meantime, font desginers can send fonts to and we’ll tell them exactly why they’re not importing.Ģ. ![]() We are working on an option to bypass the corrupt font checking. It won’t import my fonts, declaring that they are “corrupt”. Insider Software just replied to my email in which I asked about the two main problems people seem to have with FontAgent Pro:ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |