Post #2470669
2025-12-21 18:25 UTC
Replies (2)
-
@tphinney@typo.social 2025-12-21 19:14
As always, @glennf@zeppelin.flights is right on! That said, I will point out that part of the problem is likely that the underlying text had a hard-coded ffi ligature character, instead of using the OpenType layout ligature feature. Had the feature been used, it would have gracefully degraded. Perhaps someone did that because they knew the output app was unlikely to support OpenType layout features, but they thought the Unicode approach would be a safer way to ensure the glorious ligature appeared. Problem is, while the “success mode” is more likely to happen in that case, the failure mode is much worse. Better text with the three letters and no ligature, than a notdef or no text at all. (I wonder if there was a notdef that was seen in proofing and manually deleted?) Sigh....
-
@gknauss@mastodon.social 2025-12-21 19:34
@glennf@zeppelin.flights The most Glenn sentence in history: “Turns out that it’s one of my favorite subjects: ligatures.”