Re:Comic Code – Monospaced interpretation of the most over-h...
by tosche on Friday July 26, 2019 @02:49PM
(#20537321)
I originally had the so-called single-storey a by default, but it looked too confusing at coding text sizes. I even considered offering a "purist" version with that simpler a, but decided against it (too many options would confuse buyers). In my opinion, the simpler structure of a is better described as "writability" rather than legibility, and just because the new design does not follow the original does not mean it's bad. Whether it actually improved is a matter of opinion, but I believe in my decision in the context of coding.
[ Parent
| on HN ]
Re:Comic Code – Monospaced interpretation of the most over-h...
by joosters on Friday July 26, 2019 @07:34PM
(#20539247)
Yeah, I agree, it makes sense to target the legibility at small sizes, given the expected use as a coding font - rather than a 500pt poster printout on a classroom wall!
I wonder, is there any tool that measures the similarity of letters / glyphs(?) in a font, specifically as a way to highlight ambiguous letters? That might be handy when designing or choosing a font for coding.
Re:Comic Code – Monospaced interpretation of the most over-h...
by wodenokoto on Saturday July 27, 2019 @05:30AM
(#20541186)
It would be nice if you could add screenshots of the font used in different code editors to your sales page.
Re:Comic Code – Monospaced interpretation of the most over-h...
by thelazydogsback on Friday July 26, 2019 @05:48PM
(#20538646)
I just gave it a try... It has ligatures listed as a feature, but don't seem to be seeing the conversion of char sequences like I do in Fira Code. (E.g., in Vscode or VS with ligatures enabled, => turns into a "fat arrow", === turns into "a 3-bar equiv", etc.)