Organizing and Auditing Families
Select the intended fonts before a family-wide operation. Naming and grouping commands can change how members are identified, even though they do not alter their outlines.
Grouping Fonts into Families
These operations change naming metadata, not merely the temporary order of fonts in the panel. They reorganize the family-grouping defined in From Fonts to Families and must preserve the intended family-properties from Naming Fonts and Families. Save a source version before reorganizing a family. Then open the relevant fonts and select them in the Fonts panel. Font > Organize Fonts provides several ways to reconstruct family relationships from existing data.
Families from Styling Group derives typographic family/style identity from legacy group and link names. This can split a large typographic family into smaller Regular/Italic/Bold/Bold Italic groups and discard descriptive style names such as Semibold. Use it when a target workflow depends on legacy four-style groups, and inspect the resulting names instead of assuming universal application compatibility.
Families from PostScript Name derives family and style names from PostScript identifiers. It can help with legacy sources whose other names are unreliable, but identifiers without spaces may need manual cleanup afterward.
Separate Families makes each selected font its own family, using its full name as the starting family identity and Regular as its style. This is different from separating only legacy style links. It can suit deliberately independent delivery of incomplete families or separately named web-font members; use it only when separate family identities are intended.
Merge Families attempts to organize selected fonts into one family and rebuild member names and style relationships from their attributes. Review the result, then use the style-link and name-building tools where needed.
Inspect the affected names after applying an operation. Merging two selections does not prove that their designs, glyph sets, or vertical metrics belong together.
Auditing a Family with Compare Fonts
Select the open fonts to compare and choose Font > Compare Fonts…. Begin with the intended family set. Add Family Members can include other open fonts with matching family identity; it is not a guarantee that every installed or unopened family file has been discovered.
Compare coverage
Review the glyph-set differences before creating anything. A missing glyph can be an error, a deliberate style limitation, or an alternate whose naming has diverged.
The selected family member is missing four glyphs in this example. Review the differences and flag choice before Add Missing Glyphs; new entries still need design and spacing checks.
Add missing glyphs can populate missing entries. Depending on Preferences > Operations > New glyphs and available components, those entries may be blank or generated constructions. Enable Flag new glyphs and choose its color to identify them for review. Newly created coverage is not the same as a finished drawing, spacing, or feature implementation.
Check alternate and unencoded glyph coverage as well as Unicode characters. Two fonts can support the same characters while differing in small caps, ligatures, or mark variants required by their features.
Compare designs and metadata
For an appropriate two-font comparison, the design-difference percentage helps locate unexpectedly similar or different drawings. It is a comparison measure, not a quality score: a deliberate weight change should differ, while a supposedly unchanged revision may need investigation.
Use visual comparison for the actual forms. Overlay or side-by-side views can expose contour changes that a single percentage does not explain.
Family-level QA starts the pre-export checklist in The Export Process. Check names, style links, weight/width attributes, UPM, vertical metrics, and feature coverage. For the coordinated family workflow, keep UPM, Ascender, Descender, and Line gap identical across members; FontLab highlights differing family-dimension fields in yellow. Compare metrics numerically and in text: a shared naming group does not ensure consistent line behavior.
Record the unresolved differences and their intended fixes. Recheck after generating missing glyphs or rebuilding names, then carry the same representative texts into proofing of the exported family. A coherent source set is the starting point for delivery, not proof that every target application will group and render it correctly.