Release notes

Important: If you are working in a FontExplorer X Server environment,

please make sure that the FontExplorer X Server is updated to version

1.6x before installing this Client version.

FontExplorer X Pro version 3.1.x for Macintosh is not compatible with older

server versions!

 

Changes in Version 3.1.1

New Features:

  • When a font is intentionally removed from a System Font folder (via Finder), it can now be removed from FontExplorer X Pro via the context menu in the font list. Previously it could only be removed by using the "Conflicts" feature
  • It is now possible to classify all the fonts in a set, folder or smart set by selecting the set, folder or smart set in the source list and start the classification


Resolved Issues:

  • Permanently activated fonts were not activated after a system startup or restart unless FontExplorer X Pro was started
  • FontExplorer X Pro only started in the Mac user account that originally installed the software package. An "Unauthorized Bundle" message was shown when started by other Mac user accounts (e.g. after "Fast-user Switching" or "Quick Install" installations)
  • An incorrect warning message was shown when exporting font previews
  • Font Information Window: When the "Show missing characters" option in the "Characters" panel was activated, the missing characters were not shown in red
  • Various user interface issues in the French language version of FontExplorer X Pro
  • Generated "Smart Set" titles did not show detailed format information when using "Format" as the criteria
  • Several issues around scanning PDF documents for fonts (crashes, no fonts found, etc.)
  • When a communication error occurred while attempting to send feedback to Linotype, closing the error dialog with "Don't try" would also close the Feedback window containing your message
  • After updating from version 1.2.3 to 3.1 an "Attempt to mutate immutable object…" error sometimes occurred which prevented FontExplorer X Pro from starting up when the system language was set to German
  • Font Conflicts: Previous scan results were not cleared when a new scan was started for "Fonts listed in FEX but deleted in Finder"
  • Kerning was not shown in the preview or detailed preview although the font contained kerning information. See also "Known Issues"
  • Authentication was required to clean the system font caches although Admin-free mode was activated
  • OS X 10.7: If full-screen mode was active when FontExplorer X Pro was quit, the main window would open in a standard-size window when the application was restarted
  • Fonts would occasionally sort incorrectly in Group Font Family view. This resulted in the inability to jump directly to a font by keying the first character in the name

 

Known Issues:

  • OS X 10.7 only: System Font collections – Rename a collection, add a font, remove a collection requires a restart of FontExplorer X Pro before the changes are shown in the source list
  • OS X 10.6 only: Fonts with # in their filename will not appear in FontExplorer X when they are located in /Library/Fonts. When imported into FontExplorer X Pro or FontExplorer X Server they cannot be activated nor will they display a preview. Resolved with OS X 10.7.x
  • OS X 10.6 and 10.7 only: Kerning is not shown in the preview on Postscript fonts and some pairs in some OpenType fonts. Kerning is correctly shown in the detailed preview
  • After fast user switching FontExplorer X Pro refreshes the fonts in order to ensure that any System Font changes made by other users are available to all users on that machine. When doing this, the FontExplorer X Pro main window will always come to the foreground
  • When attempting to overwrite FontExplorer X Pro with a newer version, a "Fatal Error … unauthorized bundle" message may appear when there is a problem with permissions on the file you are attempting to replace. Should this occur, delete the older version of FontExplorer X and re-copy the newer version to your Applications folder
  • Mac OS X 10.5.x only (Resolved with Mac OS X 10.6): Removing font suitcases from a System Collection may cause FontExplorer X Pro to crash if some of the fonts in the suitcase are not activated. This may also occur when resolving conflicts and the font suitcase is contained in a System Collection
        – Using Mac OS X 10.5.6 – Activate or deactivate the entire suitcase and then remove the suitcase from the collection
        – Using Mac OS X 10.5.8 – Move the fonts you wish to keep to a new System Collection, then delete the System Collection containing the suitcase font

 

Known PlugIn Issues

  • Adobe Illustrator CS3, CS4 & CS5: If an Adobe Illustrator document contains a placed PDF or illustrator document with embedded fonts, an incorrect font request will occur with the status missing. Activate any fonts that the document may require and ignore the incorrect requests by clicking on the Done button
  • FontExplorer X Pro will not auto-start for an Adobe or Quark document when the Mac user account is managed with parental controls. Workaround: Start FontExplorer X Pro prior to opening Adobe or Quark documents
  • Photoshop CS5 crashes when the FontExplorer X Pro plug-in is installed but FontExplorer X Pro or its license is missing. Solution: Remove the FontExplorer X Pro Plug-in
  • Font activation with Adobe Photoshop CS3/CS4/CS5: Situation – Fonts have been activated by FontExplorer X Pro (automatically or manually) after starting the program Adobe Photoshop CS3, CS4 or CS5. 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


Resolved Issues for FontExplorer X Server Users and Server Administrators:

  • Fonts uploaded to the FontExplorer X Server version 1.6 were sometimes missing after restarting the server. This could also be seen after restoring a backup or after server replication, both of which require a server restart
  • Fixed an issue where login was slow when connecting to servers with many nested sets and folders
  • Server error messages were not shown correctly when the language was set to French
  • LDAP directory was not displayed correctly when accessing Open Directory (Mac client only)
  • With "Hide Library" enabled, users with "Write" permissions on Sets were able to select File>Import
  • Connection between server and client was periodically lost during font upload/download
  • After a long connection (more than 8 hour) users were not notified that their login had expired and were forced to quit the client in order to log in again
  • In the LDAP Configure Domains window, the Domain Name field allowed entry of IP addresses. An error is now displayed when attempting to save the configuration
  • In the LDAP Configure Domains window, the Domain Name field was labeled "IP or Hostname" in the German and French translations. This has been changed to "Domain Name" (German: "Domänen-Name:" French: "Nom de Domaine")
  • After upgrades of server with LDAP Authentication enabled, administrators were not automatically directed to LDAP Configure Domains window and instructed to enter domain information
  • Windows server panel Backup Destination now allows selection of a network directory for backup
  • Offline usage information in the small info panel is not displayed accurately when not logged in to the FontExplorer X Server
  • LDAP Synchronization would occasionally assign users to the wrong group


Known Issues for FontExplorer X Server Users and Server Administrators:

  • Due to changes to better handle concurrent user load, server upload and download times may be slower than those seen with FontExplorer X Server version 1.5