Resolved

• An issue where the FontExplorer® X Pro "Check for Update" did not function.
• An issue where FontExplorer X Pro would sporadically crash when changing the input source.
• An issue where scrolling did not work in the kerning dialog.
• An issue where permanently activated fonts were not reactivated after a system restart.
• An issue where FontExplorer X Pro would crash when resolving duplicate fonts that were contained in an Apple® Font Collection.
• An issue where FontExplorer X Pro would automatically launch when opening an image document in Adobe® Photoshop® CS3 or CS4.
• An issue where FontExplorer X Pro would crash when exporting fonts as images using extremely large point sizes when too little memory was available.
• An issue where fonts were erroneously moved to the trash during the "Clean Organized Fonts Folder" process if the font filename contained accented characters.

• The Adobe InDesign® CS 3 plug-in now installs and functions correctly under Mac OS® 10.4.
• Simplified the installation procedure when using the Quick Installer to install FontExplorer X Pro on multi-user machines.
• Added support for iWork® 09 and Adobe Creative Suite 4 in the "Clean System Fonts Folder" function.
• Added an alert when Font Book Preferences are set to allow automatic font activation.
• The FontExplorer X Pro User Guide has been updated.
• Please note that the terms of the Software License Agreement have been updated.

Known issues

• Font activation with Adobe Photoshop CS3/CS4
  Situation: Fonts have been activated by FontExplorer X Pro (automatically or manually) after starting the program Adobe Photoshop CS3 or CS4. Selecting a text layer in Photoshop will cause a message to appear stating that the fonts are missing for the text layer and font substitution will occur. Continue? This message should be responded to with "OK". Activated fonts will be correctly displayed and not substituted.
• Rare ligatures under Mac OS 10.5
  With some fonts the rare ligatures feature does not work. According to Apple, this is a known bug which will be fixed in an upcoming Mac OS update.