Hi, I’m working on a monospaced font and I’m wondering what is the best practice for standard unicode-based ligatures like fi (uni FB01) and fl (uni FB02).
I don’t want them on or automatically replacing characters for the user, and also not have to direct them to turn off ligature settings (i.e., if they type /f /i, then I want it to appear as those glyphs and not substitute with the ligature).
Should I keep these glyphs as part of the glyph set upon export to avoid any missing standard characters for certain programs. If so, how do I properly disable them so they don’t show up?
Provided the renderer in use supports substitution features and ccmp:
Make the ligatures pure composites of their individual letters (so there is no visual difference between the individually typed, unligated glyphs, and the ligature.
Disable the Liga feature.
that leaves only two ways to insert the ligature now: by its Unicode or a glyph insertion mechanism like a glyph palette. So, in ccmp, add decompositions like sub fi by f i; etc.
If it’s for coding, I personally wouldn’t recommend it because there might be situations where you do want to deal with these characters (I would just disable the liga feature).
Alternative approach is to just embrace it, having fun with the idea of these silly things being single glyphs.
Thanks much for the feedback @mekkablue and @Tosche. That /ffb lig is intriguing
It’s more for stylistic reasons, rather than coding intentions or the like.
Yes, seems that including the ligature glyphs (I do have them as same width as the other glyphs, but condensed the drawing) and disabling the feature in Glyphs app is working. I can still insert them if desired via the Glyphs panel in AI, for example.