Fonts bundled with Creative Suite 2 (and individual CS2 products)

Peter,
There's a shareware program called Print Window that lets me do just that in OSX. You might want to look it up. It's a Searchware Solutions product, I don't have the web address.

Thomas,
I really appreciate the list, especially since OSX is not capable of printing the contents of a folder in list view.
In OS9, if I wanted a quik Excel spreadsheet of my font folder's contents, I could just open the folder, select all, copy and paste into Excel. The result would be the listed contents in Excel, with a little cell shuffling a nice sortable list could be created.
I haven't figured out how to do this in X yet.

Thanks again,
Peter

Fonts with the same internal names are NOT necessarily the same font. Apple has long had a habit of licensing from Linotype TrueType versions of the same fonts that Adobe licenses from Linotype, and keeping the names the same. The character set or other properties may differ.

Of course, on the Mac OS, there are not one but THREE system font locations (and more if you have more than one user). You'd have to decide which of those to install the fonts into.

Also, many serious font users use font management utilities (other than Apple's FontBook). These people don't particularly want applications dumping all their fonts in the system fonts folder. At least if they get dumped in a private Adobe fonts folder it's slightly clearer what's what.

Not that I'm saying that solution is great, either, just that there are pluses and minuses to any single location. Probably the ideal thing would be to have the installer ask the user what they want... but that's a bunch more complication for the installer.

Regards,

T

Nigel,

Identically named fonts can be installed multiple times, particularly if different installed locations are used. Then you have the potential for font conflicts.

Neil

I may be being naive, but I would assume that a font in the system fonts folder with the same name is the same font, so wouldn't be installed again.

Frankly, I didn't realise there was an Adobe fonts folder until I searched after coming across this thread. I wonder how many other users are in the same position? (BTW, I am quite tech savvy, lest you think I missed this because I'm a numnut)

I doubt it's a major hassle for the installer to install fonts in the system folder but it would be a major hassle for many users, especially if they have other fonts there with the same name. As for giving you the choice, I don't really see much of a difference between sitting there going through the fonts in an install screen or going through them in the common fonts folder after the install. Either way, you get to choose which stay on your system.

>Is it really such a hassle for people to move fonts out of one specified folder?

Is it really such a hassle for the installer to install fonts in the system font folder, or to give an option to choose?

You do have the opportunity to install fonts separately. Just move out all the fonts out of the Adobe common files folder and install them (or not) where you want. Is it really such a hassle for people to move fonts out of one specified folder?

>Ideally, I would want control over the installation of any new fonts (which, when and where), rather than have an application installer make the decision (rightly or wrongly) for me. From your description, I see a possibility of fonts being installed twice, causing font conflicts, if you should move your fonts to some location other than the default installation.

Sorry I'm a little late to the party on this one, but I've noticed that with two computers on which I've installed CS2 (Mac) Bickham Script is recognised by PS, AI & ID, but not by FontBook, which is annoying. Apparently, the font is installed in an Adobe folder, not the system folder.

Strangely enough, Warnock Pro, which was presumably installed at the same time, is present and correct in FontBook.

Really, I would like the opportunity to install fonts separately, or at least stipulate where the installer puts them.

Thanks, Dov.

Much relieved by your response! As I wrote, I never had any reason to believe otherwise.

Neil