One second or or Quark VS wasn’t there, the next it was. No picture placeholders to eventually be replaced by pictures. Faster than a Speeding Bullet Glyphĭo you remember when you upgraded from a 56k modem to broadband Internet access? Whether you logged on for that first marvelous moment at the office or home, surely you remember the awestruck grin that slowly split your face from ear to ear as the Web was suddenly just there.
I was gratefulthat Suitcase and Suitcase Server work as fast as they do. I had come to terms with that fact, with using the delays as an opportunity to rest my eyes, stretch my legs, or sip my coffee. Heck, for all the little pauses and delays, Suitcase does it’s job pretty quickly. Fonts pushed to clients from the server will get there sometime in the next few minutes. Adding more than a couple of new fonts takes time, too, naturally-sometimes quite a lot of time-but then, Suitcase is not only indexing the fonts but analyzing them as well, storing them in the Vault for protection (if the user has enabled that feature). Of course there’s an ever so slight delay between changing a preview type or size and seeing the change reflected in the preview pane. Sure, Suitcase takes a moment or two to startup on standalone desktops and even longer to make connections with a Suitcase Server.
For many of the publishing and production workflows I’ve optimized or consulted upon, Suitcase Server is also the best available solution.
(Do you know how many keyboard shortcuts the average designer has to remember?! Well, yeah, I suppose you do.) Although not perfect, the current versions of Suitcase fit my font management needs better than any other font manager on either platform. For instance choosing between activating fonts permanently or only until the system is rebooted requires remembering a keyboard shortcut or changing a preference every single time a font is activated. They aren’t perfect, and I have my gripes.
Font universal type client mac osx#
Let me establish something right off the bat: I dig the latest versions of Extensis Suitcase-Fusion (version 12) on Mac OSX and Suitcase for Windows (version 11). Universal Type Server (UTS) runs on Windows and Macintosh servers, connects to Windows and Mac (PPC and Intel) clients, includes all the best features of both Suitcase Server and Font Reserve Server, and is faster than you ever imagined a font manager could be. We'll probably end up buying a new copy of UTS/UTC but that might not solve a duplicate font issue.Today at MacWorld Conference and Expo in San Francisco, Extensis, makers of Suitcase and Font Reserve, as well as Suitcase Server X1 and Font Reserve Server, will unveil an all new server-based font management system. It's possible the font is corrupt but seeing as UTS is supposed to have one version to stream to UTC, you'd think it'd not work on the other two macs but this is getting beyond me (especially because I'm not an IT person by trade.) and it even stumped the certified Apple engineer we have for emergencies. Using Extensis' uninstaller to scrub UTC from the problem mac and reinstall it. We could replace it with another version of Futura if needed but its needed for legacy artwork and I'd like to fix the problem.įorgetting the connection, synchronising with server, cleaning the font cache, deleted preferences, restarting the type core. We've looked through the web interface for UTS and couldn't find anyway of verifying/repairing or even removing fonts. The font doesn't appear on the copy of UTC running on the server itself and cannot be deleted. On the two problem Macs, an identical duplicate for Futura Bold has appeared (minus appearing in a workgroup) and seems to prevent either version from loading. On all 4 macs, it appears in the correct workgroups. Neither the Macs nor server have had any software/OS updates recently but last week, two of the fours macs suddenly showed a duplicate for Futura Bold. We have UTS managing the fonts for 4 macs. It's probably a long shot but Extensis no longer support UTC/UTS 5.2 so I'm hoping someone here might have seen this problem.
0 kommentar(er)
