← Back to catalogue
Published

Hoefler Text

vr.tr.hoefler-text · thing-q1622796

Enable an agent to identify Hoefler Text, assess a particular font implementation, and choose supported, authorized ways to typeset with it.

Thing Registry Activities and processes ACT.ACT

Bundle → Layer → Finding → Questions Filled

6 bundles · 11 layers · 15 findings · 27 questions

Family identity and boundaries Recognize Hoefler Text as a named typeface family and keep adjacent identities distinct.

Identity evidence

Connect the registered name to documentary and visual evidence.

Corroborated family identification

Identify the candidate through naming records and a matching documented specimen, recording uncertainty when only appearance is available.

  1. Which internal family and face names identify the candidate as Hoefler Text? definition
  2. Which authoritative specimen or distribution record corroborates that identification? provenance

Neighboring designs

Separate family membership from authorship, supplier identity, and related designs.

Text versus Titling

Keep Hoefler Titling outside this family's ownership while recording a supported relationship; the supplier presents the two as separate products. See [Hoefler Text catalogue](https://www.typography.com/fonts/hoefler-text/overview).

  1. Does the candidate belong to Hoefler Text, Hoefler Titling, or another family by the same designer? boundary
  2. What documented relationship explains a proposed pairing without merging the two families? provenance
Faces and implementations Record which Hoefler Text resources are actually available and how their implementations differ.

Face inventory

Establish supplied faces and their roles in composition.

Documented face selection

Apple documents regular, italic, black, black italic, and ornaments identifiers; use these as implementation-specific evidence rather than a universal inventory. See [Apple font documentation](https://developer.apple.com/documentation/applenews/applying-apple-news-format-fonts).

  1. Which Hoefler Text faces does the acquired package actually contain? measurement
  2. Does a bold or italic command select a supplied face, synthesize a style, or trigger substitution? action

Implementation comparison

Compare specific font resources rather than assuming all distributions behave alike.

Version-specific equivalence

Record source and version alongside observed differences in naming, outlines, metrics, coverage, and layout features.

  1. What distributor, package, internal version, and fingerprint identify each compared resource? provenance
  2. Which measured differences would prevent replacing one Hoefler Text resource with the other? boundary
Text features and ornaments Assess Hoefler Text's usable typographic repertoire in a particular application.

Typographic feature access

Inspect requested text features without assuming their presence in every implementation.

Verified feature behavior

Test small capitals, ligatures, numeral forms, swashes, and other requested alternates individually; record absence or inaccessibility explicitly.

  1. Which requested Hoefler Text features exist in this font resource, and through which layout mechanism? measurement
  2. Which application controls produce the intended glyph substitutions in rendered output? action
  3. Are displayed small capitals supplied glyphs or scaled capitals generated by the application? boundary

Ornament selection

Treat the associated ornaments as deliberately selected decorative glyphs.

Ornament mapping and portability

Inspect the acquired ornament resource's glyph mappings and output behavior before using it for decoration.

  1. Which glyph and character mapping produces the intended Hoefler Text ornament? measurement
  2. Does that ornament retain its appearance and intended decorative role through export and text extraction? action
Composition and output Evaluate whether the chosen Hoefler Text implementation works for the intended text and delivery medium.

Required-text proof

Test actual prose, punctuation, names, and numeric material.

Coverage and reading proof

Judge the selected Hoefler Text faces using representative content at the proposed size, line length, and output resolution.

  1. Which required characters or combining sequences invoke fallback or fail to render correctly? measurement
  2. At the intended text size, do the selected weight, italic, and numeral forms remain clear in representative passages? measurement

Output stability

Check whether composition survives changes in renderer, machine, or delivery format.

Reflow and substitution control

Compare fixed Hoefler Text specimens across target outputs and record reflow, clipping, lost features, and substituted faces.

  1. Which line endings, glyph choices, or bounding boxes change between the authoring view and delivered output? measurement
  2. If Hoefler Text is unavailable at the destination, which fallback has been tested against the document's layout requirements? action
Acquisition and permitted use Connect the specific Hoefler Text resource to its acquisition evidence and proposed deployment.

Distribution record

Establish how the font resource entered the working environment.

Traceable acquisition

Retain the operating-system package, supplier delivery, or other documented acquisition record associated with the actual files.

  1. Was this Hoefler Text implementation acquired through an operating-system distribution, a supplier package, or another documented channel? provenance
  2. Which accompanying terms and version records apply to these particular files? provenance

Deployment decision

Evaluate a concrete output or distribution action against available evidence.

Action-specific use evidence

Record whether the intended document embedding, web serving, application bundling, or file transfer is supported technically and by applicable terms.

  1. What exact action will expose, embed, or distribute the Hoefler Text font resource? action
  2. Which applicable provision supports or restricts that action, and what remains unresolved? boundary
  3. Can the proposed delivery preserve the intended typography using a verified permitted method? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.

Reported evidence

Findings from the breadth pass, kept separate from the structural claims.

Check these first

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these check these first hold for the sense of Hoefler Text this model covers, and on what evidence? provenance

Kinds and varieties

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these kinds and varieties hold for the sense of Hoefler Text this model covers, and on what evidence? provenance

Real-world use

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these real-world use hold for the sense of Hoefler Text this model covers, and on what evidence? provenance

Failure modes and hazards

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these failure modes and hazards hold for the sense of Hoefler Text this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Recalled without web access and unsourced; every item is a lead to verify.

  1. Which of these neighbouring kinds and how to tell them apart hold for the sense of Hoefler Text this model covers, and on what evidence? provenance

Classifiers Filled

Family
Thing Registry
Category
Activities and processes
Entry kind
thing
Plane
ACT
Domain
ACT.ACT

What it is Filled

Hoefler Text is a serif typeface family designed by Jonathan Hoefler and released in 1991, drawing on historical book typography and incorporating features for sophisticated text composition.

In scope

  • Hoefler Text family identity and documented attribution
  • Relationships among text faces, italic faces, weight variants, and associated ornaments
  • Version-specific character coverage and typographic features
  • Rendering, text composition, and substitution behavior
  • Distribution provenance and evidence governing intended uses

Out of scope

  • Jonathan Hoefler's biography and other typeface designs
  • Hoefler&Co. as a business or its complete catalogue
  • Hoefler Titling as a separately modeled typeface family
  • General histories and classifications of serif typography
  • Document content, editorial policy, and complete page-layout systems
  • Operating-system font management beyond its effect on Hoefler Text

Why it exists Filled

Enable an agent to identify Hoefler Text, assess a particular font implementation, and choose supported, authorized ways to typeset with it.

Distinguishing features Filled

  • Require family-name metadata corroborated by an authoritative specimen or distribution record; a visually similar serif face is insufficient identification.
  • Distinguish the named family Hoefler Text from its creator, its supplier, and neighboring Hoefler Titling; the supplier lists Text and Titling separately. See [Hoefler Text catalogue](https://www.typography.com/fonts/hoefler-text/overview).
  • For an Apple implementation, compare face identifiers against documented examples such as HoeflerText-Regular, HoeflerText-Italic, HoeflerText-Black, and HoeflerText-BlackItalic. See [Apple font documentation](https://developer.apple.com/documentation/applenews/applying-apple-news-format-fonts).
  • Treat HoeflerText-Ornaments as a distinct ornamental resource when encountered, rather than interpreting its glyphs as ordinary running-text letters. See [Apple font documentation](https://developer.apple.com/documentation/applenews/applying-apple-news-format-fonts).
  • Use file version, source, and demonstrated feature behavior to distinguish implementations sharing the Hoefler Text name; family identity alone does not establish interchangeability.

What robots and AI may and may not do Filled

Must not

  • Distribute font files in breach of their licence.
  • Present a lookalike font as the original.
  • Misattribute the design.

Only with a human decision

  • Licensing decisions for an organization.

May

  • Identify the typeface in documents or images and describe its features.
  • Advise on the licence terms that govern its use.

Moral aspects Filled

  • Type designers' work is protected and deserves fair payment.
  • Typefaces shape readability and accessibility of texts.

Who is affected

  • Type designers
  • Readers
  • Licensees

Owners Filled

Steward

The rights holder for the font software.

Links to other meta-models Filled

parent

  • Q25416675 - registry parent class

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.hoefler-text
  • Wikidata: Q1622796 (https://www.wikidata.org/wiki/Q1622796)

Direct properties not applicable Not applicable

  • Family identity evidence: Font naming records linked to supplier specimens or documented distributions
  • Face role: Upright text, italic text, documented weight variant, ornaments; retain exact supplied names
  • Implementation provenance: Distributor, package, filename, internal version, and file fingerprint
  • Required-text coverage: Percentage of required characters and tested sequences rendered without fallback
  • Typographic feature availability: For each requested feature: absent, present but inaccessible, selectable, or verified in output
  • Composition behavior: Line count, line-ending differences, and clipping count for a fixed specimen and layout
  • Intended-use authorization: Verified permitted, verified restricted, or unresolved for the proposed action and acquired package

Plane ACT: no invented physical properties.

Recognition optional Filled

  • A classical serif text face with old-style figures and refined, slightly calligraphic details.
  • Comes with italics, small caps and ornaments.

Capabilities and actions required Filled

  • Identify an installed Hoefler Text face and record its implementation provenance.
  • Select verified text faces and weights for a document's typographic hierarchy.
  • Test requested ligatures, small capitals, numeral forms, and alternates where the implementation supplies them.
  • Inspect and place associated ornaments using verified glyph mappings.
  • Compare composition before and after replacing a Hoefler Text implementation or exporting a document.
  • Determine whether a proposed embedding or deployment action is supported by the acquired package and its terms.

Hazards and failure modes required Filled

  • Unlicensed use leads to legal claims.
  • Substitution changes layout and readability.

Standards and interfaces required Filled

  • ISO/IEC 14496-22 Open Font Format, International Organization for Standardization and International Electrotechnical Commission.

Context of use required Filled

  • This serif typeface family is used in books, essays and other documents requiring sustained reading and historically influenced typography.
  • It supports text composition where a particular font implementation provides features such as ligatures, small capitals and alternate numeral forms.
  • Use in print or digital documents depends on available glyphs, layout support and the permissions attached to the font files.

Sources Filled

  1. Wikidata item Q1622796: Hoefler Text - identity and sense of the item
  2. Wikipedia: Hoefler Text - general description of the item

Open questions

  • Does an existing Vercy world model already own Hoefler Text, requiring this registry entry to link to it?
  • Which authoritative historical records establish the family's attribution, initial release, and subsequent revisions?
  • How do Apple-distributed and supplier-distributed implementations differ in face inventory, glyph coverage, metrics, and layout mechanisms?
  • Which distinctive outline details provide reliable visual identification against commonly confused serif families?
  • For the implementation ultimately selected, which language sequences, advanced features, ornament mappings, and deployment permissions can be verified?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q1622796/spec.json