| Formerly of | LWN, Linux.com, OSTG |
| Currently of | Type design research |
| Texas | Linux Fest |
| Just interested in, you know, in, | uh, Principles of Modern Banking and, History of Piracy. Paintings of Orozco. Modern French Theater. The... Jurisprudential Factor of Mafia Administration. Diseases of Horses and novels of Joyce Cary and... Ethnic Choices of the Arabs. Thing |
PSA: Election season is here!
And I'm in the unique position of knowing exactly how all the good candidates can win. It happens to be them saying exactly what I like, but that's just coincidence.
(And not just win, either, but get such a huge mandate that society's ills would all evaporate in a single swoop, after which everyone would be happy all the time, except for the bad politicians, who'd all be imprisoned, though they'd have confessed so even they'd feel okay.)
DM for consulting rates.
I mean, there is still stuff to strip out: name table entries, since those could be lies anyway, etc.
If you had a pre-known text you care about, you could subset the glyphset and compute the GSUB/GPOS to go with it, but I think for the app that I have in mind you can't limit it to a fixed text, so that's a non-starter.
RE: https://mastodon.social/@n8/116514898322120180
I have borderline impossibly high hopes for the reactions this is going to prompt at around noon, when all the nerds start waking up and checking their rainbow-LED-lit transparent-sidepanel PCs for the morning news.
Don't fail me now, Federated Hashtag Infrastructure!
It would be interesting to make the compilation step fully modular, and/or extract the compiler into its own parallel utility, but whether the benefit would be "edit in other tools but build with Fontforge" or "edit in Fontforge but build with something else" depends on who you ask.
As does where that idea falls on the hierarchical list of Things That Need Doing, of course.
Still thinking about a hallway conversation about #Fontforge that I had at @lgm. Yes, Fontforge has a lot of technical debt, & a lot of it comes from the app doing ≈everything internally. So it is a big deal to see the recent work to switch to HarfBuzz for previewing shaping.
HOWEVER, a big piece of that internal baggage is also compilation, and it's important to keep the old compiler available somehow to prevent breaking old projects (think Debian here). So replacing that would be problematic.
The infographic in question had, naturally, several jokes, but the one in particular that I still think about and want to reference is:
.com2
