|
Font Finagler Publisher's Description:
If you're having problems on your system with text appearing "garbled" as in the image below, it could be caused by corrupt font cache files. What appears to be happening is that incorrect or corrupted encoding vector information is being used when mapping the character codes as input by your keyboard to the glyphs they represent in the problematic font. You can use Font Finagler's Font Cache Cleaner feature to purge these cache files in an attempt to restore normal behavior, and to help rule out a font cache corruption as the sole cause of the problem. If, however, you use Font Cache Cleaner but the problem remains, then it could be caused by a font conflict, by a corrupt or less-than-ideal-quality font, or by an underlying OS X font-handling bug. Try removing fonts to isolate the problematic fonts that are causing this behavior.
What's new in this version:
Features:
* Built as a Universal Binary to run natively on both PowerPC Macs (G3, G4, G5) and Intel Macs.
* Adds support for Mac OS X 10.5 (Leopard).
* Adds support for cleaning the font cache files of Adobe, QuarkXPress, and Microsoft applications. The method Font Finagler uses to search for these additional files is both incredibly fast and thorough. Font Finagler can often find up to twice the number of font cache files as other applications: potentially thousands of files in seconds. Try a competing application first, and then use Font Finagler to see what files their application missed.
* When cleaning the OS X font cache files, Font Finagler now examines your ~/Library/FontCollections/ folder for any corrupt font collection files and will include these in a clean if needed. Corrupt font collection files can cause Font Book to hang or crash at launch, can cause applications to crash, and can prevent applications from opening the standard Font panel.
* Adds the ability to preserve Font Book's disabled fonts for the current user when cleaning the OS X font cache files (only applies to Mac OS X 10.4.x and later).
* Adds the ability to preserve Font Book's external libraries when cleaning the OS X font cache files (only applies to Mac OS X 10.5.x and later).
* Font Finagler now only requires authorization (entering an administrator name and password) if it's absolutely necessary to successfully clean the font cache files.
* Adds a "Problem Fonts" feature: when you launch Font Finagler, it automatically checks the active fonts on your Mac, and if it identifies any that are known to cause problems, such as Helvetica Fractions or Times Phonetic, it'll alert you of this. To aid in troubleshooting, Font Finagler provides information about the font's name, type, location of the font files, and what font manager application (if any) is responsible for activating the font. It also provides the ability to reveal the font files in the Finder and to deactivate the problematic fonts.
* Adds an "OpenType Font Cache Cleaner" feature that's designed to clean only the OpenType font cache file and doesn't require a restart. This feature addresses an OS X font-handling bug present in OS X 10.4.7 - 10.4.10 that affects the use of OpenType fonts in certain applications such as QuarkXPress, Macromedia FreeHand, and possibly others. The bug can cause those applications to crash when they try to work with OpenType fonts, and can also lead to a general instability in other applications as well. Many users have found that using Font Finagler to clean the font cache files seems to alleviate the crashing problems at least temporarily. Once they shutdown the machine and start back up, however, the crashing problem returns until the font cache files are cleaned and the Mac restarted. While a daily cleaning of the font cache files prior to shutdown is a possible workaround, it's rather inconvenient. That's where "OpenType Font Cache Cleaner" is designed to come in: it can quickly fix the crashing problems with OpenType fonts without requiring a full restart after cleaning. It can also be run automatically at login. (Note: you can permanently avoid this bug by updating to Mac OS X 10.4.11).
* Adds a "Font Icon Helper" feature to make PostScript Type 1 printer fonts easier to recognize. (This feature is the same as in my "Font Book Helper" application, but it fixes the AppleScript error/incompatibility that Font Book Helper had with OS X 10.4).
* Unregistered users can now freely try any and all of Font Finagler's features, including Administrator-Free Font Cache Cleaner. (Previous versions of Font Finagler required that you be registered in order to use Administrator-Free Font Cache Cleaner).
Bug fixes:
* Font Finagler is now able to function properly even if the BSD Subsystem is not installed. (In the rare case where a user didn't have the BSD Subsystem installed, Font Finagler 0.5.3 and prior would hang indefinitely while searching for the font cache files).
* Clicking the "Stop" button while Font Finagler is searching for the font cache files now works properly. (Font Finagler 0.5.3 was too busy searching for the font cache files to allow the Stop button to be clicked).
Interface enhancements:
* With font cache files that are listed in the inspection table view of Font Cache Cleaner, you can hold your mouse cursor over the file icon to see the path to the file shown in a tooltip.
* Adds new high-resolution 512px. x 512px. icons.
Registration enhancements:
* Adds a separate preference file just for the registration. That way, if you need to disable your Font Finagler preferences for some reason (troubleshooting a crash, etc.), it will still be registered. At the same time, it's also backwards-compatible: if you register with this version of Font Finagler, previous versions will be registered as well.
* You can now clearly choose whether to register Font Finagler for the current user (default) or for all users. If you choose to register it for all users, you'll be prompted for administrator-level authorization to assure that the registration preference file can be saved successfully. (Previous versions of Font Finagler would always attempt to register the application for all users as well as the current user. If the current user didn't have administrator privileges, however, the attempt to register for all users would fail and wouldn't provide any direct feedback of such failure).
|
