Skip to main content
Inspiring
February 26, 2002
Question

FAQ: Multiple master fonts on OS X

  • February 26, 2002
  • 81 replies
  • 19194 views
(This notice has been updated repeatedly to discuss: OS X 10.2, Adobe app bugs with 10.2 support, "cocoa" applications; Adobe phasing out MM font sales; Adobe discontinuing tech support for MM fonts. Last update: 23 Sep 2005.)

With versions 10.0 and 10.1, Mac OS X's native support for Type 1 and OpenType initially failed to include support for multiple master Type 1 fonts. This problem is fixed in OS X version 10.2 and later for applications using the "carbon" APIs, but not for applications using "cocoa" APIs. The two most common "cocoa" applications are TextEdit and Keynote.

Note that applications running in "Classic" mode are unaffected. They still need ATM for supporting Type 1 fonts, including multiple master fonts.

There is a workaround for some Adobe applications, such as InDesign 2, Illustrator 10 and Photoshop 7. You can rely on the native font imaging support in these applications, which is largely independent of the OS. Just put the fonts in the the Fonts folder in the application's folder, or the Application Support/Adobe/Fonts folder.

Additionally, the above-mentioned Adobe applications may have problems accessing all multiple master instances, when accessing the MM fonts which are installed at the system level, even in Mac OS X 10.2 and later. In some cases, this may be worked around by installing the fonts in the application's own fonts folder or the Application Support folder as described above.

PHASING OUT MULTIPLE MASTER FONTS

Adobe stopped making new MM and Type 1 fonts in 1999, and there is no equivalent to MM in the newer OpenType format. From late 2002 to mid 2003, Adobe phased out sales of multiple master fonts. As of this writing, they can only be bought from Adobe as part of Font Folio 9, which is still available for people who need compatibility with older fonts. The current version of Font Folio is Font Folio OpenType Edition, which shipped in August 2003.

At the end of 2004, Adobe stopped offering tech support for MM fonts, excepting for people with Font folio 9.
    This topic has been closed for replies.

    81 replies

    Known Participant
    May 30, 2003
    Jeff,

    Adobe's conversion process is just about complete. But there is no reason why you cannot continue to use PostScript Type 1 fonts for quite a few years longer. As I understand, other foundries are just beginning to convert their libraries. There is still plenty of support for this older font technology.

    Neil
    Participant
    May 28, 2003
    Thanks again Thomas. I have been out of the loop, I suppose. After a couple of days of research, I am ready to purchase some OpenType fonts. I read that Adobe is converting its library to OpenType. Is there a utility for end users to convert their own existing Type 1 (especially MMs), or TrueType fonts to OpenType?

    Thanks,

    Jeff
    Inspiring
    May 25, 2003
    Although I don't know specifically, and couldn't say if I did, it would seem unlikely that Apple would put much more effort into increasing their level of MM support at this time, given that Adobe has stopped selling MM fonts.

    T
    Participant
    May 25, 2003
    Hi Thomas,

    Thanks for your reply. I am not a type expert but it seems that the inability to generate interim instances nullifies the reason for MM fonts in the first place? Is that correct? Do you have any idea if Apple plans to fully support MM fonts in 10.3?

    Thanks,
    Jeff
    Inspiring
    May 24, 2003
    You can't generate new instances for MM fonts in OS X, unfortunately.

    T
    Participant
    May 24, 2003
    Hi,
    Thank you for this information. Using the Application Support->Adobe->fonts folder, I was able to see MM fonts in InDesign 2. However, I can only see the primary instances. I used to generate other instances with ATM under OS 9. How does this work under OS X?

    Thanks,
    Jeff Ratliff
    Known Participant
    May 22, 2003
    Marc,

    As I understand this has been an Apple OS problem, not an Adobe problem.

    Neil
    Participant
    May 22, 2003
    The applocation spport>adobe>fonts solution does not seem to work for me, running OS 10.2.6 - I cannot see MyriadMM (jsut the reg instance) must I delete all instances of the font everywhere else (I put copies int othe folder)? I run Suitcase but quit out of it when testing this.
    Seriously, Adobe should be thoroughly embarassed by this situation
    Participating Frequently
    May 22, 2003
    >The applocation spport>adobe>fonts solution does not seem to work for me, running OS 10.2.6 - I cannot see MyriadMM (jsut the reg instance)

    Which Adobe application are you using here? And what version?

    Aandi Inston
    Known Participant
    May 12, 2003
    Neil,

    If they solved it, that is wonderful. It's a little late for me, as I have already converted hundreds of files to type1 for now, with many more to go, but I am now on a roll, have it down to a workflow to eliminate MM completely.

    I am using OSX 10.2.5 for now as there have been some issues with 10.2.6 from users on these forums. You can't be too careful when making changes in a high-demand situation like I am working in. Downtime is out of the question. The MM issue does not appear to have been resolved as of update 10.2.5.

    Type1's will not reach out and bite me like MM did because they are a more stable form of type, being non-animated for weight and other variables associated with interpolation related to design axis.

    I don't care if Type1's are no longer sold - I have a fort knox of type1 that should hold me for the next 10 years at least, while I give OpenType a trial run on another machine in my office.

    OpenType sounds really cool, I just want to make sure I don't get into another jam when OSXX comes out.
    Known Participant
    May 3, 2003
    Ken,

    The latest incarnation of Mac OS X is supposed to have solved multiple master font handling.

    Neil