657a4463f3
The current OpenType Feature File specification is silent about what the proper behavior should be when a single glyph has multiple LigatureCaretByPos or LigatureCaretByIndex statements. After this change, we match the behavior of Adobe's `makeotf` tool. Arguably, `makeotf` might not be optimal in its current behavior, but it seems better to match the existing toolchain than to have two conflicting interpretations of an ambiguous spec. Once the specification gets clarified, we will of course follow. See https://github.com/adobe-type-tools/afdko/issues/95 for the spec discussion.
11 lines
415 B
Plaintext
11 lines
415 B
Plaintext
table GDEF {
|
|
LigatureCaretByIndex [c_t s_t] 11;
|
|
|
|
# The OpenType Feature File specification does not define what should
|
|
# happen when there are multiple LigatureCaretByPos statements for
|
|
# the same glyph. Our behavior matches that of Adobe makeotf v2.0.90.
|
|
# https://github.com/adobe-type-tools/afdko/issues/95
|
|
LigatureCaretByIndex o_f_f_i 66 33;
|
|
LigatureCaretByIndex o_f_f_i 55;
|
|
} GDEF;
|