4 ms·
Just curious, what would you say about this font sample: http://i.imgur.com/DSXqMCZ.png http://i.imgur.com/DSXqMCZ.png ? (It's a modification of Terminus, with
by a-nikolaev 12y ago
Just curious, what would you say about this font sample: http://i.imgur.com/DSXqMCZ.png http://i.imgur.com/DSXqMCZ.png ? (It's a modification of Terminus, with smaller letter height to have a bit more whitespace between the lines)
- danudey 12y agoI'm not the person you're replying to, but my answer: dizzying and illegible.
- aeflash 12y agoIndividual characters can be made out, but words are hard to read. Not enough separation between letters and symbols, so constructs like "(pred=%i)\t" are harder to visually parse. I'm also not a fan of aliased pixel fonts -- it really exacerbates the picket-fence effect while reading. Here's what your code sample looks like in Source Code Pro: http://i.imgur.com/uAknyGB.png http://i.imgur.com/uAknyGB.png Smaller font: http://i.imgur.com/m0p17tm.png http://i.imgur.com/m0p17tm.png Notice how all letters take up the full horizontal width so words clump together. It's easy to see that a space is a space, and not just an "i" next to an "l" It's also worth noting that I had to try 3 separate OCR processors with your sample before I got one that didn't output complete garbage.
- a-nikolaev 12y agoThanks for such a great analysis! You pointed out some things I did not really think about. Especially the way Source Code Pro handles "i"s and "l"s. I will try to add 1px of horizontal space between letters. The goal was to make the font vertically compact, but still legible. The size is small and it feels quite clumped though.