If you recently updated Adobe Acrobat, Ghostscript, or your OS system language packs, the software might regenerate its internal CID font registry. The software detects that the old cidfontf1 mapping (e.g., "Adobe Ming Std") has been replaced with a newer Unicode mapping. The "new" label simply means the cache was rebuilt.
The term "F1" in this context is shorthand for Adobe Font Metrics (AFM) Format 1 or refers to the internal naming conventions within PostScript Type 1 fonts. cidfontf1 font new
Historically, CIDFonts were often bundled with F1 metrics (.afm files). While the CIDFont handled the raw glyph shapes (the "bodies"), the F1 file handled the spacing, kerning, and bounding box data (the "clothing"). If you recently updated Adobe Acrobat , Ghostscript
In the 1990s and early 2000s, the combo was common: When PostScript interpreters (like Adobe CPSI or Harlequin
When PostScript interpreters (like Adobe CPSI or Harlequin RIP) saw an F1 metric file linked to a CIDFont, they could render complex scripts accurately. However, this dual-system is largely legacy; modern workflows have merged these metrics directly into OpenType-CID fonts.
In the world of digital typography, most users are familiar with TrueType (TTF) and OpenType (OTF). However, in high-end printing, PDF archival, and professional document workflows (like those used by government agencies and airlines), a different kind of font technology rules the roost: CIDFont.
But what happens when you combine the technical structure of CIDFont with the historical weight of "F1" and the modern push for "Font New"? Let’s decode the triad.