Help

System Requirements

FontExplorer X Pro Client has been optimized for Microsoft Windows® Windows 7, Windows 8, Windows 8.1 and Windows 10 and requires .Net framework 4.5. It runs on both 32-bit as well as on 64-bit Windows Systems. Supported languages include English, German and French.

If working in a FontExplorer X Server environment, this client version requires FontExplorer X Server version 2.5.1 or later. However, we recommend you update your server to the latest version 3.0.4 in order to get the most out of all the great new server features. Older FontExplorer X Server versions are not supported.

Version 3.5.4

New

• Support to Adobe CC 2019 plugins
• Support to QuarkXPress 2018 plugins

Resolved

• Non admin users are not able to run the FEX services
• Illegal characters in font file path are crashing FEX client

Known Issues

• If a font that is missing in FontExplorer X Pro is re-imported from another path, the font will still be shown as missing (in red) after the application is restarted
• On a multi-user machine (one machine with separate login accounts) FontExplorer X Pro can only be launched by one user. If another user attempts to launch FontExplorer X Pro a message will be displayed: "FontExplorer X Pro is already running in another user session"
• Manually activated PostScript fonts do not display in Adobe applications when font activation is temporary. Workaround: select Activate fonts permanently (required when using Adobe applications) in Options/Advanced panel or activate fonts via the plug-in font request dialog
• The auto-activation setting will not be effective for the QuarkXPress Plug-Ins. When opening a QuarkXPress document, the plug-in dialog will always open. If all the fonts are available in FontExplorer X Pro simply click on Activate All
• The activation status of a folder is not correctly shown in the source list when all fonts in the contained set are activated. This only occurs when the setting "Show status when activating/deactivating fonts" is disabled
• When a subscription font does not appear in FontExplorer X Pro for any reason, manual synchronization from the SkyFonts client does not cause the font to appear. Workaround: Restart the SkyFonts client

Plug-Ins

Known Issues

• Adobe Photoshop 64-bit plug-in no longer supports the "Replace" function in the plug-in request dialog
• Photoshop CS5–CC 2018: Fonts in layered TIFF files are not activated by the plugin. Activation occurs correctly when converted to a PSD file
• Missing fonts are not detected in Illustrator PDF files and no font request occurs
• No font request occurs on EPS documents with non-embedded fonts
• When using Adobe Creative Suite products to create new documents, Postscript server fonts that are activated on the server are not displayed in the Font drop down menu. Postscript fonts in an existing CS document that are activated on a server, will behave properly; the fonts will appear in the Font drop down menu and can be activated/deactivated appropriately. This issue only applies to PS server fonts, all other font types (TrueType, OpenType) work correctly. Local Postscript fonts will behave properly in Adobe Creative Suite products. Workaround: Update PS server fonts to TrueType or OpenType format

Server Users and Administrators – Requires Server version 3.0.3

Note

• The “Auto login” option should not be used together with Kerberos authentication when there are multiple user accounts on a workstation that are logging into FontExplorer X Server. With “Auto login” when a different user is attempting to log in, the login credentials for the last logged in user would be sent. This is the expected behavior

Resolved

• Login to the FontExplorer X Server was extremely slow when the Server had a large number of fonts, even if the user only had access to a small number of fonts
• Incorrect file size was shown in the Server backup panel, values after the decimal point were truncated
• Server font force download/force activate did not have an option to cancel once the process was started
• The font “Import” button was disabled if a Server, Server Library, Server Set or Server Folder was selected
• Kerberos users were not able to log in with the 3.5.2 client

Known Issues

• After updating from FontExplorer X Pro version 2.7 to version 3.5.3, the option “Login automatically to the server” needs to be reconfigured if it was previously turned on
• When generating a License Report the "invalid e-mail address" warning is shown even though the "send notification" option is not selected
• A generic error message is shown if a disabled LDAP user attempts to log in to the FontExplorer X Server
• Font Licensing: When a change is made to the available license count on a font it is not reflected by the "Last Modified" date
• The checkbox status of imported users is occasionally incorrectly set after deleting the group in the FontExplorer X Server Groups panel

System Requirements

FontExplorer X Pro Client has been optimized for Microsoft Windows® Windows 7, Windows 8, Windows 8.1 and Windows 10 and requires .Net framework 4.5. It runs on both 32-bit as well as on 64-bit Windows Systems. Supported languages include English, German and French.

If working in a FontExplorer X Server environment, this client version requires FontExplorer X Server version 2.5.1 or later. However, we recommend you update your server to the latest version 3.0.3 in order to get the most out of all the great new server features. Older FontExplorer X Server versions are not supported.

Version 3.5.3

New

• Integrated FontExplorer X Pro plug-ins for Adobe CC 2018 InDesign, InCopy, Illustrator and Photoshop applications
• Integrated FontExplorer X Pro plug-ins for QuarkXPress 2017

Resolved

• FontExplorer X Pro crashed if a system font did not contain a family name
• The Support button in the Ribbon was not correctly linked
• The client software license file was no longer valid if the system date was December 6, 2018 or later. It was not possible to start FontExplorer X client
• Various minor unrelated bug fixes and user interface improvements

Known Issues

• If a font that is missing in FontExplorer X Pro is re-imported from another path, the font will still be shown as missing (in red) after the application is restarted
• On a multi-user machine (one machine with separate login accounts) FontExplorer X Pro can only be launched by one user. If another user attempts to launch FontExplorer X Pro a message will be displayed: "FontExplorer X Pro is already running in another user session"
• Manually activated PostScript fonts do not display in Adobe applications when font activation is temporary. Workaround: select Activate fonts permanently (required when using Adobe applications) in Options/Advanced panel or activate fonts via the plug-in font request dialog
• The auto-activation setting will not be effective for the QuarkXPress Plug-Ins. When opening a QuarkXPress document, the plug-in dialog will always open. If all the fonts are available in FontExplorer X Pro simply click on Activate All
• The activation status of a folder is not correctly shown in the source list when all fonts in the contained set are activated. This only occurs when the setting "Show status when activating/deactivating fonts" is disabled
• When a subscription font does not appear in FontExplorer X Pro for any reason, manual synchronization from the SkyFonts client does not cause the font to appear. Workaround: Restart the SkyFonts client

Plug-Ins

Known Issues

• Adobe Photoshop 64-bit plug-in no longer supports the "Replace" function in the plug-in request dialog
• Photoshop CS5–CC 2018: Fonts in layered TIFF files are not activated by the plugin. Activation occurs correctly when converted to a PSD file
• Missing fonts are not detected in Illustrator PDF files and no font request occurs
• No font request occurs on EPS documents with non-embedded fonts
• When using Adobe Creative Suite products to create new documents, Postscript server fonts that are activated on the server are not displayed in the Font drop down menu. Postscript fonts in an existing CS document that are activated on a server, will behave properly; the fonts will appear in the Font drop down menu and can be activated/deactivated appropriately. This issue only applies to PS server fonts, all other font types (TrueType, OpenType) work correctly. Local Postscript fonts will behave properly in Adobe Creative Suite products. Workaround: Update PS server fonts to TrueType or OpenType format

Server Users and Administrators – Requires Server version 3.0.3

Note

• The “Auto login” option should not be used together with Kerberos authentication when there are multiple user accounts on a workstation that are logging into FontExplorer X Server. With “Auto login” when a different user is attempting to log in, the login credentials for the last logged in user would be sent. This is the expected behavior

Resolved

• Login to the FontExplorer X Server was extremely slow when the Server had a large number of fonts, even if the user only had access to a small number of fonts
• Incorrect file size was shown in the Server backup panel, values after the decimal point were truncated
• Server font force download/force activate did not have an option to cancel once the process was started
• The font “Import” button was disabled if a Server, Server Library, Server Set or Server Folder was selected
• Kerberos users were not able to log in with the 3.5.2 client

Known Issues

• After updating from FontExplorer X Pro version 2.7 to version 3.5.3, the option “Login automatically to the server” needs to be reconfigured if it was previously turned on
• When generating a License Report the "invalid e-mail address" warning is shown even though the "send notification" option is not selected
• A generic error message is shown if a disabled LDAP user attempts to log in to the FontExplorer X Server
• Font Licensing: When a change is made to the available license count on a font it is not reflected by the "Last Modified" date
• The checkbox status of imported users is occasionally incorrectly set after deleting the group in the FontExplorer X Server Groups panel