Adobe Type Manager
computer program for managing fonts

Adobe Type Manager (ATM) was a family of computer programs created and marketed by Adobe Systems for use with their PostScript Type 1 fonts. The last release was Adobe ATM Light 4.1.2, per Adobe's FTP (at the time).
Around 2000, with Apple's Mac OS X and Windows 2000, support for both Type 1 fonts and OpenType fonts with PostScript outlines was built into the operating system using ATM Light code contributed by Adobe. As a result, ATM was then no longer necessary for font imaging or printing.
Apple Macintosh
The original ATM was created for the Apple Macintosh computer platform to scale PostScript Type 1 fonts for the computer monitor, and for printing to non-PostScript printers. Mac Type 1 fonts come with screen fonts set to display at certain point sizes only. In Macintosh operating systems prior to Mac OS X, Type 1 fonts set at other sizes would appear jagged on the monitor. ATM allowed Type 1 fonts to appear smooth at any point size, and to print well to non-PostScript devices.
Around 1996, Adobe expanded ATM into a font-management program called ATM Deluxe; the original ATM was renamed ATM Light. ATM Deluxe performed the same font-smoothing function as ATM Light, but performed a variety of other functions: activation and deactivation of fonts; creating sets of fonts that could be activated or deactivated simultaneously; viewing and printing font samples; and scanning for duplicate fonts, font format conflicts, and PostScript fonts missing screen or printer files.
“Adobe Type Manager” enters the record as computer program for managing fonts. Crown Archives preserves that source wording while asking what Adobe, Type and Manager can confirm, complicate or overturn.
Why this record matters
“Adobe Type Manager” is worth following because a concise public description often conceals a longer documentary argument. Here, Adobe, Type and Manager provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 12, 2026. The linked authority identifier is Q360450. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2000 and 1996.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Adobe Type Manager”, its source revision and the description used here.
- Expand the search: follow Adobe Type Manager primary sources, Adobe Type Manager archive and Adobe research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Adobe Type Manager”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Adobe Type Manager” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.