Fonts in OSX

[by_Buko@adobeforums.com]

B)

[Nini Tjäder]

There is nothing wrong with Suitcase if you turn off Auto-Activation in ID and AI (and take otut the plug-ins for that). The choice in Suicase XI for managing system fonts is there if you have at least Suitcase 11.0.2. and you need at least Suitcase X1 for proper working with Suitcase.

[Kenneth_Lasley@adobeforums.com]

Okay. Do you have some stock in that company...lol!

Ken

[Nini Tjäder]

No. I have no stock nowhere. I've just used Suitecase - and still does with CS2 and an Intel iMac - for years as long as OS X has been around (I was an early adopter of OSX with 10.0 some six years or so ago) and never had any problems with it. Not now and not previously. I am also one of those who never had any problems with ATM Deluxe pre OSX.

I've been troubleshooting and solving font-problems with clients machines since around 1985 with various OS-s and font managers. When there are problems it is always because the font is damaged, not complete, not installed in the right place, or because the users uses more than one single font management application at the same time so the applciations you work in don't know which fonts are on or off, or have copied the fonts in not a complete state from somebody elses machine. Except for the auto-activation plug-in problem, I've seen no problems whatsoever with Suitecase over the years.

I feel all the kicking on Suitecase to be very unfair and without reason. None of the font managers are better than any of the others - it is just a matter of taste which one you use and how you want your fonts organized when using a font manager.

[by_Buko@adobeforums.com]

Except for the auto-activation plug-in problem, I've seen no problems
whatsoever with Suitecase




For the same price you can have FAP with auto-activation that works.

[Nini Tjäder]

Sure - but I already have Suitcase X1 and have no problems with it so I don't see why I should change? The day when Suitcase will no longer be possible to run on current OS on my machines, then I will let FontBook handle my fonts. By then I guess it will also have gotten more features than it presently has.

[Marco_A_SantaMaria@adobeforums.com]

or Linotype FEX1.1 which is free.
I still using Font Reserve at work, yes as incredible as it can be, auto activations works fine for all my applicaitons, InDesign, Illustrator, and qxp.
At home I have been using FEX with auto activation with InDesign CS2 on an iMac Intel, and I have not experienced any problems—knock on wood ;)
The important thing to remember is to know what fonts you will keep on the different OSX fonts folders and what you are controling via a Font Manager, whichever you feel more confortable with.
I just keep requiere OSX fonts in the appropiate folders and everyting else I manage with FR or FEX.
Kenneth, glad to hear that FAP help you solve your problem. Becasue they do not have support for CJK languages, or other non roman Languages, FAP would not work me at all.

[Eric_@_MCA@adobeforums.com]

Kenneth,

If you're using Tiger, log out and log back in and try again. This is the New Tiger Procedure whenever Suitcase starts claiming all your fonts are belong to System.

If it still complains, start looking around for other fonts sources.
/System/Library/Fonts
/Library/Fonts
~/Library/Fonts
/Classic System Folder/Fonts
/Library/Application Support/Fonts
/Applications/InDesign CS2/Fonts

And Nini--check out Font Explorer 1.1. IMHO, it's officially the best now for everything except Classic activation (which will not be with us much longer anyway.)

[Kenneth_Lasley@adobeforums.com]

Eric, I did all that. I finally bought FAP Pro..problem has been solved.

Thanks