3 ms·
If you go into the more thorough "Compare" mode of the site, you'll see that the long code sample contains the line 1Il|L 80Oo 5S ([{<>}]) \*+-–—/!?:;.,@=~^%$
by s9w 10y ago
If you go into the more thorough "Compare" mode of the site, you'll see that the long code sample contains the line
1Il|L 80Oo 5S ([{<>}]) \*+-–—/!?:;.,@=~^%$ __# "q" 'q' “q” ‘q’
Which is designed to cover all those tricky cases. Do you still think something is missing?
The reason for not flagging the fonts on those differences is that it's kinda tricky. First it would be a lot of work and increase the complexity of the site. But mainly it's not so clear because some fonts like Monoid and Input actually offer highly customizable options to fine tune for these things like slahed or non-slashed zeros etc
- e12e 10y agoNo, I think your compare-page is excellent. I'd just like an (even) easier way to pare down fonts to pick and compare. Personally I don't really care all that much if a font is really pretty, if it falls down on (some) of those. I get that it would be a lot of work, and a pull request would be more welcome than a comment :-) Maybe an interface where others could tag the fonts, and have some suggested tags (dashed-zero, dotted-zero, plain-zero; el-one (1 and l too similar), pipe-I etc) -- and a way to filter on those? I'm not sure it would be all that helpful, but it's an idea as the number of fonts grow. I suppose I could even see that work for a bigger project that included non-monospace fonts.