From Fonts to Families
A family is more than a collection of related drawings. Its members need coherent names, style relationships, character coverage, and shared metrics so applications can present and use them as intended.
Font Families as Coordinated Sets
Recall family-properties and font-properties from Naming Fonts and Families. Shared properties identify the family and coordinate its behavior; per-font properties distinguish weight, width, slope, and style. The vertical-metrics realization from Font Metrics and Glyph Metrics requires matching Ascender, Descender, and Line gap when members are to share consistent line spacing.
The members may begin as separate source fonts or as static instances generated from one designspace, as taught in Defining and Generating Instances. Once they become family members, apply the same naming and consistency review to both.
Keep typographic identity, legacy style linking, and working organization distinct. Family-grouping means treating the relevant open fonts as one working family for operations such as Organize Fonts and Compare Fonts. Their naming metadata helps identify that set; it is not a separate temporary grouping that leaves names untouched. Exported names and style links determine how applications identify the members.
Open the intended members before a family operation and inspect their identities together. A shared typographic family can contain several legacy style groups, and an editor’s convenient comparison view is not proof that those groups are correctly named. Conversely, changing family organization can change the metadata that applications will see. The operational workflow in the next chapter therefore begins from a deliberate set of fonts and checks the consequences for both shared and member-specific properties.
Organize Fonts provides batch naming and grouping operations. Compare Fonts helps audit glyph coverage and design differences. Use them after the input names and design attributes describe the fonts correctly; automation cannot infer a reliable family from contradictory metadata.
Style Linking
OpenType naming supports two related views of a family. The typographic family uses a Family name and a distinct Style name for each member, corresponding to name IDs 16 and 17. It is not limited to four styles.
A legacy style group supports Regular, Italic, Bold, and Bold Italic through names and style-link states associated with name IDs 1 and 2. At most one member can occupy each of the four roles, so a family with more than four members must be partitioned into several legacy style groups.
The style-link selector has the four Regular/Italic/Bold/Bold Italic roles; those roles are separate from slope classification.
Keep the linking architecture simple
A conservative family setup uses one core group for Regular, Italic, Bold, and Bold Italic. Its Style group matches the Family name; the core Regular member is the default style of the whole typographic family. The conventional Regular/Italic weight is 400, and Bold/Bold Italic is 700. Linking a heavier style as Bold inside a Light group can make it appear as “Light Bold” rather than under its intended style name.
In older FontLab Studio 5 terminology, Family Name meant the legacy styling-group name; the current Family name means the typographic family name. Do not transfer that old label’s meaning unchanged.
Give other weights their own groups, linked only to their matching italics. For an illustrative family named Example:
| Typographic style | Style group | Style link |
|---|---|---|
| Regular | Example | Regular |
| Italic | Example | Italic |
| Bold | Example | Bold |
| Bold Italic | Example | Bold Italic |
| Light | Example Lt | Regular |
| Light Italic | Example Lt | Italic |
| Semibold | Example SemBd | Regular |
| Semibold Italic | Example SemBd | Italic |
The Light member remains typographically Light even though it occupies the Regular role of its own legacy group. The role describes the toggle relationship, not a demand to redraw it at regular weight.
Do not use the Bold link simply to mean “the next heavier style.” Linking Semibold as the Bold of Light can make an application's Bold toggle jump between unrelated named weights and produce confusing menu behavior. The recommendation above reserves the core Bold relationship for the conventional 400/700 pair rather than dividing a large family into arbitrary four-member blocks.
Keep width consistent within a style group and give each member its true weight and slope attributes. A Condensed group should not acquire a normal-width Bold merely to fill an empty slot.
These are compatibility-oriented authoring recommendations, not a claim that every application presents all naming systems identically. Test the exported family in the applications that matter. Large designs can also use deliberate family-name overrides to form separately branded subfamilies.
Configuration and Building at Scale
Set each member's Family name, Style name, Style group, and Style link in Font Info. For instance-generated styles, review the corresponding instance properties before generating the static fonts.
A useful non-default style-group name combines the family name with a short distinguishing suffix. Abbreviations such as Lt, Blk, Cond, or Ext can keep legacy menus readable, provided they remain unambiguous within the family.
Keep names concise and follow the current field validation. Older compatibility guidance favored short ASCII-only family/group names and especially short PostScript names; those conservative targets are not universal limits on every modern OpenType name record. That guidance used fewer than 32 characters for family/style/group names, fewer than 64 for the full name, and fewer than 30 for the PostScript name; treat these as legacy compatibility targets rather than the current maximum lengths of all those fields. Use the current naming rules and counters, retain valid PostScript identifiers, and test any broader character repertoire in the intended applications.
Correct the design attributes before running name builders, and save any hand-tuned names you may need to recover. A builder can replace those names, and its generated abbreviation may differ from the one you intended.
Select the family members in the Fonts panel before using Font > Organize Fonts:
- Optimal Styling proposes groups and links from weight, width, slope, and related attributes. Review that the result matches the intended core and italic-only groups.
- Build Styling Group Names is the family-scale counterpart of Build Names in Naming Fonts and Families; it derives each group using its Regular member’s typographic style name.
- Build Style Names derives style names from design attributes.
- Separate Styling makes members independent style groups with Regular roles, providing a starting point for deliberate relinking.
Review the resulting fields across the whole selection before saving.
Finish with a compact family table listing each member's typographic name, group, link, weight, width, and slope. Check duplicate roles, unexpected family splits, and the chosen default member before moving on to export proofing.
Copy font information between open fonts
Use Font Info’s clipboard controls to reuse metadata across open fonts. This transfers font information, not glyph outlines.
- Open the source font’s Font Info dialog and check the intended master and values.
- Click Copy all pages. The ordinary click includes the current master’s data; Alt-click includes all masters.
- Click Paste to fonts and check the destination fonts. Only open fonts appear in this list.
- Turn on Paste to all masters to target all masters; leave it off to target each destination font’s current master.
- Confirm with OK. Review the destination values, especially when the fonts have different master structures, and finish any pending edits in Font Info with Apply or OK.
The destination checkboxes and master option set separate scopes. Check both before transferring information that could replace different values in another design.
Paste Font Info lists the open destination fonts. Paste to all masters controls whether the transfer reaches every master or only each font’s current master.