Anchors and Carets in Ligature Recipes
Build ligatures with deliberate attachment points and caret positions. Use the anchor matching rules in Constructing Glyphs with Named Anchors before combining several bases.
Anchors in Ligature Recipes
A ligature needs separate attachment positions for the letters it represents. Number those positions in reading order: top_1 and bottom_1 belong to the first component read, then top_2 and bottom_2 to the second. In the Anchors & Pins panel, edit names to set the indices and drag entries to group the anchors by component. Use the same organization for a hand-drawn ligature.
For =f&i, source top anchors become top_1 and top_2. A base without an anchor still occupies its component position; adding a mark with + does not allocate another position. An already numbered source ligature reserves its existing span when joined to another base. Ambiguous surviving names can cause a recipe error instead of a silent replacement.
A right-to-left ligature is built in left-to-right visual order but needs attachment indices in reading order, from the right. Inspect the generated names and panel order, and correct them before generating mark features (see Attaching Marks); do not assume that the recipe's component order supplies the required indices automatically. Because + is handled inside its base group before numbering, =f&dotlessi+dotaccentcomb@top still uses the unnumbered top of dotlessi for that attachment.
Carets within a ligature
A ligature caret gives a text cursor or selection a stopping position between the characters represented by one glyph. FontLab represents it with an anchor named caret_1, caret_2, and so on, displayed as a blue vertical line. The editor displays caret anchors in variable-font projects as well. GDEF, introduced in The Process Architecture, stores these positions in an exported font; FontLab also imports supported GDEF carets as editable caret anchors.
Modern & constructions generate a caret between successive spacing components. With &, it lies at the preceding component's advance boundary. With &\, it lies halfway through the kerning interval. For =f&\i, a kerning value of −10 places the caret 5 units before the end of f's advance. In a longer recipe, each boundary uses its own operator and accumulated placement. Positions are calculated for each master.
Check caret names and positions in reading order, especially in right-to-left ligatures. Add appropriate caret anchors by hand for a separately drawn ligature. Carets are excluded from Anchor Clouds and generated mark features; they do not replace ordinary attachment anchors or prevent their inheritance. Per-master caret positions in the editor do not by themselves establish how a particular variable-font export represents them.
Arabic construction examples
The following two constructions use existing Arabic source glyphs. Prepare their outlines and anchors first, and inspect the chosen master after building. Enter these = forms in an auto-layer recipe field; in Build Glyphs, put the intended destination name before the equals sign.
To assemble yeh_jeem_yeh-ar.fina from finished letters:
=yeh-ar.fina&jeem-ar.medi&yeh-ar.medi
The final yeh is listed first because it sits on the left. After building, inspect the joins and spacing, then arrange the attachment anchors by component in reading order, from the right, and check the generated carets. The finished letters supply their own dots.
A separately drawn dotless skeleton (rasm) can have a different shape from those three letters joined together; the distinguishing dots (i’jam) are added separately. Give behDotless_hah_alefMaksura-ar.fina the receiving pairs top_1/bottom_1 through top_3/bottom_3, numbered from the right, and place its two caret anchors by hand. Give each dot mark an incoming _bottom above its dots and an outgoing bottom below them. Then use this single-line recipe:
=behDotless_hah_alefMaksura-ar.fina+twodotshorizontalbelow-ar@bottom_1[_bottom]+dotbelow-ar@behDotless_hah_alefMaksura-ar.fina:bottom_2[_bottom]+twodotshorizontalbelow-ar@behDotless_hah_alefMaksura-ar.fina:bottom_3[_bottom]
The first dot group can use the preceding skeleton as its target. The later groups use the glyph: recipe-target prefix from Using Recipes for Composite Building to name the skeleton explicitly, so they do not attach to the previous dots. Each used bottom_N is replaced by the corresponding mark's outgoing bottom, inherited as bottom_N below the dots. The skeleton's unused top anchors and carets remain available. Inspect all three dot groups and the resulting anchor list before using the glyph for further mark attachment.
Check Right-to-Left Construction
For adjacent bases in right-to-left ligatures, use #exit and #entry anchors to establish the joins. RTL construction reverses inherited-anchor and caret numbering. Encoded RTL glyphs can be detected automatically; #?rtl supplies the direction for an unencoded glyph. Inspect the assembled glyph and caret sequence in actual right-to-left text.