I used to make a hybrid bitmap-vector font called Unison [1] a decade ago and I made it in that way so that I don't have to learn the fine art of (vector) typography. Or at least that I could skip most of it (for example, kerning is still required for proportional fonts, but that doesn't have to be very precise in bitmap fonts). I'm now working on Unison once again after 11 years of time, this time armed with a dedicated font editor called Uniform. I haven't publicly released Uniform in public yet but anyone interested can already download and compile it.
Thank you, that was perfect Sumday-morning reading: Easy to read yet dense information-wise.
I learned today: The difference between ttf and otf, what strong and weak characters are, what an Em is and where kerning and leading really come from.
My favorite parts: Learning where the magic of ligatures and those tiny postion-changes in moments like "To" come from.
I don’t think I ever really considered that some fonts could be computationally more demanding than others. I wonder if you could make a font whose characters are so overwhelmingly complex that it can kill performance maliciously? Like certain characters having millions of control points in an otherwise unassuming font.
I suspect the URL and the article title are correct, if you buy the whole chapter - and it's just that we are seeing a preview which gets the grounding down first.
[1] https://github.com/lifthrasiir/unison
reply