![]() This may actually be a limitation of the MySQL engine that FontExplorer uses to keep up with its fonts. Users/Shared/Linotype/FontExplorer X//Īnd, I think that Linotype wants to keep the database file on the local computer's startup disk to avoid having to worry about opportunistic file locking with network filesystems, like AFP. That is, whenever FontExplorer is launched in a NHD environment it creates a new "FontDatabase.db" file in a directory on the Upon investigation, I can see that FontExplorer is actually doing something very similar to the FontAgent shell scripts. In other words, as users move around from machine to machine, session to session, and day to day it always forgets all their fonts- even though the actual font files always remain accessible in the same place. ![]() ![]() So again following Gerrit's tips from here, I tried the latest version of FontExplorer which is supposed to support network home directories- and it runs! (Unlike FontAgent.)īut it has an incurable case of amnesia. (I did get the official work-around shell scripts from Insider Software, and those looked to be an easily broken kluge that only solve half the problem.) We started with FontAgent (cause we own 30 licenses), but quickly found that to be not very well adapted to a network home environment. (Even Word is playing nice thanks to a tip I found here!) In my testing of network home directories everything is working perfectlyĪccept our font manager. At the beginning of January I migrated all workstations to a freshly built 10.4.4 universal image and updated (actually re-installed) my server and took it to 10.4.4. I'm a humble (tho ambitious) graphic design instructor trying to get network home directories working in my 30-seat design lab.
0 Comments
Leave a Reply. |