Features / Components
Components
Reusing glyphs inside other glyphs, such as a base letter plus an accent, so changes carry through.
How it works
A component is a reference to another glyph, placed inside a glyph instead of a copy of its outline. É can be built from the glyphs E and acute; edit the acute, and every glyph that uses it changes. A component can be moved, scaled, mirrored or slanted: a fraction can combine the fraction bar with two smaller digits. Components can contain components, as long as no glyph refers to itself. Decomposing a component turns it into an ordinary outline that no longer follows its source.
In a TrueType font, components are kept as composite glyphs in the glyf table, which also makes the font smaller. A TrueType glyph is either composite or simple, so a glyph that mixes components and contours is decomposed by build tools such as ufo2ft. The CFF and CFF2 tables, which hold PostScript outlines, have no composite glyphs; they share data through subroutines instead, so components are decomposed there too.
Why it matters
Components keep repeated parts, such as accents, identical across many glyphs, and one edit updates them all.
What to check
- Whether TrueType export keeps components as composite glyphs, or always decomposes them (the Partial level below).
- How it handles nested components, which the OpenType specification advises avoiding for the widest compatibility.
- Whether a composite can take its spacing from one component, as the TrueType flag USE_MY_METRICS allows, so that î matches the dotless i.
- Whether marks can be placed from anchors (see Automatic composite glyphs).
Read more
- glyf composite glyph description, Microsoft
- Comparison of ‘glyf’, ’CFF ’ and CFF2 tables, Microsoft
- UFO 3 GLIF component element, Unified Font Object
Editors
- Full
- Places, edits and decomposes components, and exports them as composite glyphs in TrueType fonts (CFF and CFF2 have no composite glyphs).
- Partial
- Components with stated limits, such as always decomposing them in TrueType export.
| Editor | Support | Evidence |
|---|---|---|
| FontCreator | Full | Live references; exported as composites in TrueType, decomposed for CFF outlines.Checked 2026-10-25 · developer documentationSource |
| FontForge | Full | Called references; unlinked on output only where a format cannot express them.Checked 2026-10-25 · developer documentationSource |
| FontLab | Full | Add Component and Decompose; the Export Process page says TrueType output keeps suitable composites.Checked 2026-11-10 · developer documentationSource |
| Fontra | Full | Checked 2026-10-25 · developer documentationSource |
| Glyphr Studio | Full | Offset-only instances export as TrueType composites; transformed ones are flattened.Checked 2026-10-25 · developer documentationSource |
| Glyphs | Full | TrueType export keeps components; overlapping ones decomposed unless a parameter is set.Checked 2026-10-25 · developer documentationSource |
| RoboFont | Full | Checked 2026-10-25 · developer documentationSource |
| BirdFont | Not supported | Checked 2026-11-02 · stated by the developer |
| Fontself Maker | Not supported | Developer on forum: components not supported; each accented letter is a separate glyph.Checked 2026-10-26 · developer documentationSource |
| FontStruct | Not supported | Editor code has no glyph components; Copy to Latin Accents copies letters unlinked.Checked 2026-10-29 · developer documentationSource |
| iFontMaker | Not supported | Glyphs share paths only by copying; components are not mentioned.Checked 2026-11-12 · developer documentationSource |