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.
41 lines
1.0 KiB
XML
41 lines
1.0 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<ttFont>
|
|
|
|
<GDEF>
|
|
<Version value="1.0"/>
|
|
<LigCaretList>
|
|
<Coverage>
|
|
<Glyph value="c_t"/>
|
|
<Glyph value="o_f_f_i"/>
|
|
<Glyph value="s_t"/>
|
|
</Coverage>
|
|
<!-- LigGlyphCount=3 -->
|
|
<LigGlyph index="0">
|
|
<!-- CaretCount=1 -->
|
|
<CaretValue index="0" Format="2">
|
|
<CaretValuePoint value="11"/>
|
|
</CaretValue>
|
|
</LigGlyph>
|
|
<LigGlyph index="1">
|
|
<!-- CaretCount=3 -->
|
|
<CaretValue index="0" Format="2">
|
|
<CaretValuePoint value="33"/>
|
|
</CaretValue>
|
|
<CaretValue index="1" Format="2">
|
|
<CaretValuePoint value="55"/>
|
|
</CaretValue>
|
|
<CaretValue index="2" Format="2">
|
|
<CaretValuePoint value="66"/>
|
|
</CaretValue>
|
|
</LigGlyph>
|
|
<LigGlyph index="2">
|
|
<!-- CaretCount=1 -->
|
|
<CaretValue index="0" Format="2">
|
|
<CaretValuePoint value="11"/>
|
|
</CaretValue>
|
|
</LigGlyph>
|
|
</LigCaretList>
|
|
</GDEF>
|
|
|
|
</ttFont>
|