211–220 of 289 posts
* bitmapped + ligatured fonts - you can have both!
* sans-serif normal, serif italics - Italicized words were serif-ed. "Latin Modern Mono" is an example. Also, Donald Knuth made that font - did you know Donald Knuth made a font?
Really cool work, thanks for making this.
Earlier quoted context omitted.
> "When the strike passes the edge of the circle, it's no longer a zero, it's a Danish or Norwegian "Ö" (Ø). It's been a part of their alphabet for centuries." You can't please all the people, all of the time. There are ~21 million people living in Scandinavia - and for them, that could indeed be somewhat of an issue. What about the rest of the planet? > "By badly thought out design and a need to be different for no…
> what would you consider to be a better design I don't think there is one. The standard is the standard for a reason, and doesn't need to be better IMHO.
I loved traipsing through the different fonts to see what they did. I discovered some font-features I wasn't aware of: * bitmapped + ligatured fonts - you can have both! * sans-serif normal, serif italics - Italicized words were serif-ed. "Latin Modern Mono" is an example. Also, Donald Knuth made that font - did you know Donald Knuth made a font? Really cool work, thanks for making this.
Earlier quoted context omitted.
That's what I feature on the blog, but you'll notice the right-hand side of app.programmingfonts.org is interactive. That's kinda hard to do with static images ;)
Would it violate the ToS to create a simple sprite sheet out of a proprietary fixed-width font?
Great site, but one request: Please make the up/down keyboard arrows switch to the prev/next font (rather than just scrolling the list of fonts). That way I could keep my eyes on the code window to really feel the change. Currently, having to visually bounce from code window to font selection window and back slows me down and makes it harder for me to compare fonts.
J/K for next/previous font
A/Z to increase/decrease font size
S/X to increase/decrease spacing
T to toggle anti-aliasing
https://gist.github.com/MCluck90/1cbcbb615eca18466b8be6c7ec0...
Earlier quoted context omitted.
Ligatures could probably be simply shown by adding one or two of the most common ones ( <=, != etc...)
Maybe it's changed in the last hour or two, but for me it does indicate when ligatures are present -- in the list on the lest, under the name of each font there's a line giving name, date, and some features -- one of which is "ligatures".
This is a really cool site, thanks! It also helped me understand something about the font sizes that always puzzled me (but never enough to actually look it up). All of the fonts there have the size of 16, but some are clearly bigger than others. Compare e.g. Inconsolata and Meslo: http://app.programmingfonts.org/#inconsolata http://app.programmingfonts.org/#meslo Having them side by side, you can see that they conta…
I wish there was a filter. It would be nice to filter out fonts that are not mono typed and don't have ligatures.
The Terminus font doesn't seem to render properly there. Possibly it's just my browser but I use that font all the time in the terminal. Here it looks glitchy/aliased or something.
It's one of the reasons why I still haven't fully switched to VSCode. There doesn't seem to be a way to disable antialiasing in VSCode to make this font look good, as far as I can tell.