| Q: After loading fonts, my computer
seems to "hang." Did FontMatch™ really crash? |
OS X |
| A: Probably not. In Mac OS X, after
loading new fonts, the system attempts to notify all open applications
that new fonts are available (if they requested it.) This notification
process may take a long time, if one or more of the fonts which
FontMatch™ tried to load are corrupt. To eliminate the
problem, try using a program like Morrison Soft Design's FontDoctor to
diagnose and repair your fonts. |
| |
|
| Q: FontMatch™ seems to be conflicting with my font management software. What can I do about this? |
OS X |
A: We are aware that some users
are having conflicts and are working to find a
solution. The reason conflicts could occur is that FontMatch™ is
temporarily loading fonts onto your computer, in order to identify
them. For the interim, it may be better to not use another font
intensive product while FontMatch™ is
running.
UPDATE! Version 1.5 has been updated to play nicer with Font Management utilities like Mac OS X Font Book. |
| |
| Q: I've got almost 8,000 fonts. FontMatch™ takes nearly an hour to load and scan through all of them. Is this normal? |
All |
A: Yes. Lets break this down for a moment. 8000 fonts per hour = 133 per minute = 2 1/4 per second. Most people can look and compare fonts at a rate of 1 or 2 seconds each. Considering FontMatch™ is also collating them into a list of most likely candidates, an hour is not too bad. Please keep in mind that the more fonts you have, the slower FontMatch™ may run. Please be patient.
UPDATE! It shouldn't take this long any more! With version 1.5, the recognize process is 200%-800% faster which means this process could take as little as 10 minutes! |
| |
| Q: I've got all of my fonts located on a server. Will this affect the performance of FontMatch™? |
All |
| A: Most likely yes. FontMatch™ temporarily loads each font into memory during the process of analyzing them. In this instance, the faster your network is, the faster FontMatch™ will run. |
