this post was submitted on 29 Jul 2023
140 points (100.0% liked)
Technology
37712 readers
224 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Do modern day fonts even support automatic ligatures? How does that work? Or are there Unicode symbols for them?
Both! Unicode has some support for as-is ligatures. For example
fiis U+FB01.Modern fonts can also use self-defined ligatures. That's how fonts like https://www.sansbullshitsans.com/
So my plan is (eventually) to add in ligatures where Unicode has defined them - and automatically replace typed text with self-defined ligatures where it doesn't.
Of course they do, better than ever actually. Google OpenType ligatures, for example. You can even use those on the web using CSS.
Some fonts have hundreds of different ligatures.
Yes, they do. Part of the OpenType standard are the so called “OpenType features” which (amongst other things) allow for contextual alternates, i.e. different kinds of ligatures, and for stylistic alternates, e.g. a slashed zero, a single-storey ɑ, etc. All of these different glyphs are encoded in the font and can be enabled when typesetting using different selectors. This website shows them off.
Some ligatures, like “ffl”, are a separate character in Unicode. Some were added because they can be considered a different character in languages other than English. Some (like “ffl”) were added because of legacy reasons; “no more will be encoded in any circumstances”.