|
From: Thales M. <tha...@gm...> - 2026-08-27 19:42:56
|
Thanks for sharing that. I usually modify fonts that already have these lookups present, that's why I didn't think of it. Those anchor rules are really complex; One must take their time to grasp it. On Thu, Aug 27, 2026 at 3:27 PM Mauro Sacchetto <mau...@gm...> wrote: > Oh, the solution was just around the corner!! > > I must have messed around with a thousand useless attempts. > > In reality, compound glyphs are created correctly with mark combs under > these conditions: > > 1) have all the useful combing glyphs (Modifiers are also present, but > at this point they are not used); > > 2) create the "mark" lookup in Lookup - GPOS with the relevant classes; > > 3) set the anchors for base and mark; > > 4) in "Preferences - Accents" set PreferSpacingAccents to OFF (the other > two options have no effect). This is essential. > > Now everything works correctly. > > Thank you very much for your extensive help. > > m > > > > > Il 27/08/26 15:40, Thales Martins ha scritto: > > If you delete the spacing grave(U+0060) and the modifier grave(U+02cb) > > and leave only the combining grave(U+0300) and then tweak the > > "PreferSpacingAccents" back and forth, and it still doesn't work, then > > I don't know. Perhaps someone else could give a tip. > > > > > > > > _______________________________________________ > > fontforge-users mailing list > > fon...@li... > > https://lists.sourceforge.net/lists/listinfo/fontforge-users > > http://fontforge.10959.n7.nabble.com/User-f8781.html > > > > > > > > _______________________________________________ > fontforge-users mailing list > fon...@li... > https://lists.sourceforge.net/lists/listinfo/fontforge-users > http://fontforge.10959.n7.nabble.com/User-f8781.html |