3 ms·

I'm quite surprised no serious "programming font" to this days didn't come with something improving camelCase readability: making ligature for each lowerUPPER c

by myfonj 7y ago

I'm quite surprised no serious "programming font" to this days didn't come with something improving camelCase readability: making ligature for each lowerUPPER combination with slightly wider center gap and narrower first character (so that sum was still in monospace grid) would FMPoW tremendously boost readability and would be remedy for camelCase haters. I've searched for it lately and the only what resembled this was interesting POC of "mixed" (semi-proportional monospaced) font [1], but with simple kerning pairs, not ligatures, but with extra trickery for "uppercase prefixes" (`_UUUl... `→`_UU·Ul...`). I wonder if in-word camelcase boundaries would be doable as well, so that `decodeURIComponent` would be rendered as `decode·URI·Component`. [1] https://twitter.com/Tricertops/status/951551714078941185 https://twitter.com/Tricertops/status/951551714078941185

runxel 7y ago
> I wonder if in-word camelcase boundaries would be doable as well Theoretically yes. But in practice most possibly no. OpenType tables just feature fixed length strings matching. It can't match to more powerful regular expressions. You would need an infinite number of OT rules. [0] If you'd have a well defined set, maybe it could work, but it would still be overwhelming fast. [0] http://pfaedit.sourceforge.net/gposgsub.html http://pfaedit.sourceforge.net/gposgsub.html