Is it worthwhile to put combining mark anchors in letters like ð, ß, ŋ? Are there enough mad linguists out there that a commaaccent will inevitable end up under a capital eszett? Does this stuff add so much bloat to web fonts that it might delay a user from loading two dozen tracking scripts by a millisecond? I don’t see an obvious reason to set this stuff up. But the Brill fonts can handle any crazy thing I throw at them (except y+ogonek, that looks gross) so I worry that there really is someone who needs every crazy possibility to work.
0
Comments
If you are adding anchors anyway then adding a few more won't be a problem.
However it is unlikely anyone will ever use them on this sort of character.
One that might cause trouble is ŋ̩ (U+014B, U+0329). I don't know if some phoneticians use ŋ̍ to avoid collision.
Ogonek is used for nasal vowels in some Indigenous American languages, so they can appear on any vowel character, and perhaps also vowel-like characters such as v and w, though I have never seen that.
I don't know about eszett, but it looks like it might take a cedilla: ß̧. (https://en.wikipedia.org/wiki/Cedilla). It is certainly not a phonetic symbol, so I think it may be someones idea of an şş- or sş-ligature. I wouldn't worry about it.
In Danish linguistics, ð̞ is an essential sound. But it usually works fine.
What do you mean? If the designer doesn't create the anchor, it won't work. I assume you mean most fonts you came across supported this?
A different but related question, does it make sense to add anchors to accented characters? Sadly, it's the only way to get automatic compound accents in FontForge. But I guess they (the anchors in accented characters) are even less useful in real life applications.