It is allowed, as of at least PR №4154, to implement a feature in the Python API and not backport it to the legacy language. FontForge's Python API is always to be used for new scripts. We recommend no new scripts in the legacy language be written. Per §D2 (emphasis mine):įontForge includes two scripting capabilities: first, via a legacy scripting language created by George Williams, FontForge's original author, called internally ff. If you're going to be learning scripting in FontForge, it's non-intuitive to start with the native scripting language. Anyway if the function font.addLookup() and font.addLookupSubtable() are supposed to add new tables then the names shouldn't match anyway right?Īnyway this is what the file may look after simplifying: Then I opened fontforge and try edit the fonts lookup table and subtable names for ligatures to "liga" and generate the font again, there is something going on, because then after I open the newly generated font, the old default name 'liga' Standard Ligatures in Latin lookup 1 subtable is back (and not the simple "liga" that I edited there. Then I created the above mentioned script but modified the names in it to "liga" both. Then I installed it and tested it, and my newly created ligature worked. It allowed me to still generate the font and I did. It also found errors: self intersecting, missing points at extrema, too many points. I continued to generate the font, generated as an otf font. Generated a font file, at which point it didn't like the em size was 1300 and that it should be 1000. Then I just used the method for adding ligatures described in this tutorial and adde one ligature for a_b. I downloaded just some test font that already has ligatures and it was this Here's the process trying to add just this one ligature using scripting: Glyph.addPosSub('ligatureshi', ligature_tuple)
Glyph = font.createChar(-1, ligature_name)
0 kommentar(er)
