Re: Adobe Font Folio V11 Font Collection ISO LZ0
Towanda Tuning
Yes, as long as the fonts have been downloaded, they will be unaffected. If not yet downloaded, purchased products will remain in your Adobe account for three years after the date of purchase. Read more about this Adobe policy.
Adobe Fonts is a collection of over 20,000 fonts included with a Creative Cloud subscription. Many of the fonts included in Font Folio are available in the Adobe Fonts library. Read more about licensing Adobe Fonts.
Adobe Font Folio was a collection of more than 2,400 OpenType fonts,[1] designed by several renowned type foundries. As of early 2005[update], there were around 10,000 fonts available in OpenType format. Adobe's font library makes up under a third of the total, all of which are included in Font Folio.
Anyone trying to navigate the transition from Type 1 fonts for hundreds or thousands of documents should be aware that Adobe has suddenly just yanked the ability to purchase Font Folio. After careful research over a couple of months and careful planning to create a cross-reference to transition us from Type 1 fonts (Helvetica, Times, etc.), just the other day I sent final justification to our purchasing department/supervisors. They agreed to purchase.
Today I received an email from Adobe letting me know that "The Adobe sales team unfortunately decided to end sales of Font Folio. Sorry for the inconvenience". BOOM. But heck, the Buy Font Folio information and button are still prominent on the Adobe site.
And Helvetica, Times and many other basic fonts are NOT in the subscription plans. Plus, Adobe can yank a font from your subscription plan at any time, so you may fire up a document one day only to discover you no longer have the font. So now I have to hop around from foundry to resupplier trying to find (and re-justify) each font to purchase, instead of loading the entire purchased library into our Font Server and have them all immediately available.
Inconvenience? This is a disaster. Another one. Between this and yanking the Pantone libraries, Adobe, you're beginning to resemble a certain former phone company. ("We don't have to care. We're the phone company Adobe.") And yes, I posted in Adobe Voice also.
Several type foundries choose to include some of their fonts on Adobe Fonts. Adobe does not "yank" the fonts from your subscription plan, but there have been a couple of times when foundries have pulled out, taking their fonts with them. When you go to Adobe Fonts, you can see if the font is an Adobe Original or if it belongs to a foundry.
Clarification: I had two postings in Voice; I was trying to get lists of both Adobe Font Folio, and fonts available via subscription. The email from Adobe that Font Folio was no longer available went to the Font Folio posting.
I did also receive a list of subscription fonts, with the caveat that "This list will quickly become outdated". The fluxuation of subscription fonts was part of our reason for pursuing Font Folio, along with the need have physical fonts to upload to our font server for our entire team so we can set up per-project sets for a smoother transition. We did our research, determined what we needed, justified it, and our purchasing department was setting it up when Font Folio was rescinded. Obviously things do not move quickly at a larger company, so we're looking at significant delays if we now must switch to per-foundry research, re-justification and purchase orders.
I was just about to ask @Sil.C about the conflicting information on the Buy Button for Font Folio and the announcement that the team decided to end the sales of Font Folio. Now that you've answered here, though, I realize she would have tagged you. Can you address this for @quoz ?
Even if you had Font Folio, these fonts "no longer exist" as they were restructured and renamed e.g. HelveticaLTStd, so you would have had to do a "manual" find/replace to update any old documents anyway. A minor inconvenience, but at least you had a way. That being said, like Pantone withdrawing, the fonts contained in the Font Folios were part of an existing licensing agreement with the foundries which no longer exists, hence they can longer sell them. You can blame Adobe, Linotype, Berthold or whoever, but these "free" "basic" fonts are no longer free. No printer comes bundled with them any more as well. On the Mac side, they drooped the Type 1 versions of the "Basic" font sand switched to Truetype versions more than 20 years ago (which caused enough problems), but there is no such default set in Windows. I get that Linotype, Monotype, etc want to make money off their own version of cloud fonts, but still, I feel your frustration.
Yes, we're aware of the need to manually replace, but at least the font names were the same in the Font Folio package, and we created our path forward with the list that Adobe provided of Font Folio fonts that we planned to purchase. We WERE planning ahead. The suddenness of receiving an email on June 24 "Sorry you cannot purchase this as of June 1" threw a monkey wrench into all of it, forcing us to spend more unproductive time reassessing a plan we thought was solid.
Here's a sample list of Helvetica from the Font Folio catalog. Yes, they WERE based on the same Linotype outlines, so you could safely F/R the Type 1 for the OTF version with minimal chance of reflow, but they already had new internal Postscript names. Not all fonts in the Folio were like that though. Some of the Adobe original fonts, for example, were slightly updated/redesigned/rekerned when they made OTF versions, especially when they upgraded them to the Pro set, so there were some that caused considerable reflow.
Hi Brad. What I meant by "same names" was Font Folio had an Open Type Helvetica, a Times Roman, Frutiger, Univers, etc. I understand size, kerning, tracking will not be identical, but it would have given our team single-purchase base collection of closely-named fonts, loadable into our font server, and a static foundation for a cross reference for our substitution project. Hence my post title.
Linotype used to have a CD collection of their own... all of the fonts they had on the Adobe Font Folio were there; Not sure if they still do. Any links I searched for now are falling silent (They seem to be reorganizing their product line (e.g. their font manager Font Explorer (which has been mine for many years) has been announced as EOL as of 2023 and won't be updated after that).)
I recently accquired a copy of Adobe Font Folio 8 as part of a lot of old computer software (I collect the stuff, we all have to have hobbies, don't judge) and while the included PFM files work great for using the fonts with classic versions of Windows, I'd like the AFM files to use them on OS/2 and various DOS based programs. Those used to be available on the Adobe FTP site, but there seems to have been a wholesale removal of legacy product support recently? Can anybody help?
16 out of those 37 packages (400-436) are MM fonts. These never contained *.afm-files but *.mmm instead. So these are not missing. Most or all of the rest should be in the zip-archive you can download from my MEGA.nz account below.
Thanks. That has the AFMs for packages 1-399, but it's missing info for packages 400-436. Given that the Font Folio 8 CD was nowhere near full, I can't for the life of me understand why they would have left off the AFM files.
Thanks for the files. This is certainly one of the gems of my Retrocomputing collection, up there with my Amiga 500. And as a single double wide CD case, it takes up a lot less space. One other bit of Adobe history I'd like would be some of the printed specimens books that Adobe did for some of the Originals back in the 80s and 90s.
Lately I've been baking them into the base image but for 10.6 I'm going with a real base image and using packages and scripts to modify it, so when new versions come out there is minimal modification required. I'm just looking for a way to package the fonts and have them available in a collection for the users in Font Book.
That sounds like a decent solutions, but since Font Book allows activation and deactivation of fonts, couldn't we just install all of them in one location (meaning no dups) and let users activate them and deactivate them at will.
What I've done with the baked in image is get about 200 commonly used fonts, as reported by the graphic design profs, and have those installed in everyones Font Book, centrally, then just putting up instructions to add fonts through font book from the /User/Shared folder.
Now that I think as I type, your solution could work. I don't like telling people to copy stuff in and out of their Library folders because of the dicey nature of other things in there, but I could make a package of the 200 included fonts in /Library/Fonts, then allow the users to add the others from the shared location through Font Book. I guess I was trying to keep them separate from system fonts in /Library/Fonts, but why?
in the event that a user decides to be lazy and loads all fonts, we have a application that goes and removes all the unnecessary fonts and requires the user to reboot.
I'm sure a little script could purge the users font directory. Maybe even serve it up over Self Service.
Our app also combs the /Library/Fonts and /System/Library/Fonts ....just incase we install something that slips a font into one of these directories.