Features / OpenType layout
Mark positioning from anchors
Placing accents and other marks with anchors, so the font positions them through mark and mark-to-mark features.
How it works
Marks are glyphs such as accents, vowel signs and tone marks that sit above, below or beside another glyph. To place them, you add named points, called anchors: top on each letter where an accent should sit, and a matching _top on each accent, as in the naming convention of the open-source library ufo2ft.
From these anchors the editor generates GPOS lookups. Mark-to-base attachment, in the mark feature, moves each mark so its anchor meets the matching anchor on the preceding base glyph. Mark-to-mark attachment, in the mkmk feature, stacks one mark on another, using marks that carry both kinds of anchor. A ligature gets one anchor per component, such as top_1 and top_2, for mark-to-ligature attachment. The GDEF table records which glyphs are marks.
Why it matters
Anchors let a font place marks while text is laid out, covering combinations it has no ready-made glyph for, such as Vietnamese tone marks over vowel marks, or vowel marks in Arabic and Hebrew. Anchors can also build precomposed accented glyphs (see Automatic composite glyphs).
What to check
- Whether it generates both mark-to-base and mark-to-mark positioning (the Partial level below has only one).
- Whether it handles ligatures, with one anchor per component.
- Whether the lookups update when you move an anchor, and can be tested on text (see OpenType feature proofing).
- Whether anchors survive a round trip through UFO, which stores them in each glyph’s file (see UFO 2 and 3).
Read more
- GPOS mark-to-base attachment, Microsoft
- The mark feature, Microsoft
- UFO 3 glif anchor, Unified Font Object
Editors
- Full
- Anchors in the editor that generate mark and mark-to-mark positioning.
- Partial
- Only one of the two, or other stated limits.
| Editor | Support | Evidence |
|---|---|---|
| FontCreator | Full | Generates ccmp, mark and mkmk from anchors.Checked 2026-10-25 · developer documentationSource |
| FontForge | Full | Mark-to-base, mark-to-ligature and mark-to-mark from anchor classes.Checked 2026-10-25 · developer documentationSource |
| FontLab | Full | Anchors generate mark and mkmk features under the export profile's policy.Checked 2026-11-10 · developer documentationSource |
| Fontra | Full | Live emulation from anchors; compiler generates mark features on export.Checked 2026-10-25 · developer documentationSource |
| Glyphs | Full | Checked 2026-10-25 · developer documentationSource |
| RoboFont | Plugin | Mark Feature Helper extension writes mark and mkmk features from anchors.Checked 2026-10-25 · reference sourceSourcePlugin: Mark Feature HelperPrice: FreeWorks with RoboFont 4.4b or later (stated minimum) (source)Latest release: 1.0.1, 2026-03-11 (source)Checked 2026-11-10 · developer documentation |
| BirdFont | Partial (BirdFont Freeware and Commercial, BirdFont Plus only) | Mark classes with anchors generate mark-to-base; mark-to-mark not documented.Checked 2026-10-26 · developer documentationSourceBirdFont Open Source: Not supportedGPOS writer emits only a kern feature; no anchors.Checked 2026-10-26 · developer documentationSource |
| Fontself Maker | Not supported | Developer on forum: OpenType features beyond kerning, ligatures and alternates not implemented.Checked 2026-10-29 · developer documentationSource |
| FontStruct | Not supported | FAQ: no data on how letters combine is added to fonts.Checked 2026-10-26 · developer documentationSource |
| Glyphr Studio | Not supported | No anchors; only kerning and ligature features are supported.Checked 2026-10-25 · developer documentationSource |
| iFontMaker | Not supported | Marks are placed by hand inside glyphs; anchors are not mentioned.Checked 2026-11-12 · developer documentationSource |