One PostScript font and an EPS file: BOOOOM! In case you're wondering what kind of mind-bendingly complex document it takes to bring it down, here's a sample: Advertisement Again, this was painfully consistent on both the G5 and Intel Macs. A tip on the Linotype forum suggested removing duplicate fonts (hardly a good permanent solution) that also failed to fix the crashes. It apparently doesn't take much to get FontExplorer X to take a dive when the InDesign and Illustrator plug-ins are involved. Your mileage may vary, but I'm taking a lot of precautions to test all these packages properly (double-checking that no conflicting manager's plugin was installed, along with flushing the font cache and rebooting between running the other font managers). Judging from the FontExplorer X forum, it's known that there are stability issues with the InDesign plug-in.įontExplorer X's Illustrator results were not much better unfortunately and between outright failing to do anything when opening documents and lots of crashing of Illustrator CS2 on various documents (not related to the InDesign file and using different verified fonts), it was really not much fun using FontExplorer in production. It had better luck with other InDesign documents but I know it wasn't an issue with the document since it had no issues with the other font managers. But still the same crashing wouldn't go away.
#FONTAGENT 7 SOFTWARE#
All updates to the system and software were applied.
#FONTAGENT 7 INSTALL#
I thought that maybe this was because I was on the Intel machine so I switched to a fresh install of Tiger and Adobe Creative Suite CS2 on my G5. I cleaned the font cache and restarted, and still the crashing persisted. It then started looping in crashes with no end in sight. I didn't see any, so I restarted InDesign and tried again. It had activated some fonts before it crashed, so I opened it to see if there were any corrupt ones in the imported library. When I opened one of the layouts on the CD, it brought up the conflicts dialog: I seemed to have to have quickly found FontExplorer X's Achilles heel with InDesign CS2 activation. The test apps were QuarkXPress 7.0.2, Illustrator CS2 and InDesign CS2. To test each, I went through some common workflow scenarios: Import a set of mixed-format fonts from a variety of locations and activate them when the documents that need them are opened.
More on this in a bitfirst we'll see how each does with the official plug-ins. As a solution to this problem of perpetually outdated plugins, all three of these programs now have system-wide auto-activation to circumvent the whole process by handling all system calls for a font, instead of just on a per-app basis. On the MacBook Pro, font activation for the respective plug-ins works for all the Adobe programs even though they are running in Rosetta and the font managers are Universal Binaries.
#FONTAGENT 7 PRO#
The FontAgent Pro auto-activation plug-in folder: coder psychotherapy sold separately