by simantel on 12/28/23, 10:44 PM with 110 comments
by pushfoo on 12/29/23, 12:22 AM
Tom Thumb is also Public Domain (CC0).
[1] https://robey.lag.net/2010/01/23/tiny-monospace-font.html
by RpFLCL on 12/29/23, 1:34 PM
by lifthrasiir on 12/29/23, 7:42 AM
by zserge on 12/29/23, 9:37 AM
by elpocko on 12/29/23, 12:34 AM
by wonger_ on 12/29/23, 1:46 AM
It won't render nice here because of line spacing and unicode but it should work fine in the terminal.
See also another 3x3 font and someone else's figlet port of that one:
by karaterobot on 12/29/23, 1:20 AM
by kragen on 12/29/23, 2:04 AM
the same problem happens with the public-domain 'tom thumb' font pushfoo linked in https://news.ycombinator.com/item?id=38800409. it is actually 4×6 (24 output pixels) but claims to be 3×5
it can be accessed despite tls problems at http://web.archive.org/web/20230828193815/https://robey.lag.... but says 'Please do not post this article to Hacker News.'
my own 4×6 font is demonstrated at http://canonical.org/~kragen/sw/dofonts-1k.html, where it fits into a 1024-byte web page along with all the logic needed to render ascii text with it; but the proportional font i used in http://canonical.org/~kragen/bible-columns (rendered with http://canonical.org/~kragen/sw/netbook-misc-devel/propfontr...) is at http://canonical.org/~kragen/sw/netbook-misc-devel/6-pixel-1... and is slightly smaller; it averages 21.5 pixels per character. this is more than anders de flon's so-called 3×3, which is 16 pixels per character, but it supports the full character set, if you think ascii is the full character set anyway. so does simplifier's 4×4 font
i think you could do better by using grayscale for antialiasing, and as rafabulsing pointed out, matt sarnoff's millitext http://www.msarnoff.org/millitext/ uses subpixel antialiasing to get very readable text at 1⅔×5 pixels
by monokai_nl on 12/29/23, 11:15 AM
It's more of a typographic concept than being fit for actual use, but it was interesting to explore creating a font within a tight set of constraints.
by lagrange77 on 12/29/23, 12:21 AM
by modeless on 12/29/23, 12:21 AM
On my MacBook Air 13" seems like you could fit 640*400 = 256000 characters at once. Which ought to fit, for example, the complete text of Alice's Adventures in Wonderland.
by fimdomeio on 12/29/23, 12:27 AM
by nelox on 12/29/23, 2:09 AM
by mgoetzke on 12/29/23, 7:59 AM
by divbzero on 12/29/23, 6:18 AM
You need at least 6 pixels to encode 27 letters + 10 digits because:
2⁵ < 37
2⁶ > 37
But 2×3 pixels seems unlikely to be legible. From 2×3 pixels, you can increment the height to 2×4 pixels or the width to 3×3 pixels. The latter feels more feasible.by evertedsphere on 12/29/23, 2:30 AM
by xarope on 12/29/23, 1:22 AM
this would probably have beaten that smallest font back then
by Kerrick on 12/29/23, 12:20 AM
by andsoitis on 12/29/23, 9:57 AM
- 5 and S are indistinguishable
- 0 and O are indistinguishable
- 2 and Z are indistinguishable
- no lowercase
While context will generally suffice in making the indistinguishable glyphs understood correctly, there are some use cases where we mix letters and numbers in the same string and those would be ambiguous.
by layer8 on 12/29/23, 12:42 AM
by userbinator on 12/29/23, 1:32 AM
(Incidentally, a common 7-segment display can also fit all of ASCII, and if you include a decimal point too, can represent a single byte completely: https://dkeenan.com/7-segment%20ASCII%20characters.txt )
by seba_dos1 on 12/29/23, 4:44 AM
by simantel on 12/28/23, 10:57 PM
by justinl33 on 12/29/23, 3:06 AM
by shpx on 12/29/23, 4:12 AM
by avmich on 12/29/23, 1:45 AM
by spiritplumber on 12/29/23, 1:00 PM
by lencastre on 12/29/23, 11:26 PM
by tail_exchange on 12/29/23, 12:11 AM
by asylteltine on 12/29/23, 1:44 AM
by Herodotus38 on 12/29/23, 12:17 AM
by tap-snap-or-nap on 12/29/23, 12:40 AM
by ChrisArchitect on 12/29/23, 4:13 AM
by klyrs on 12/29/23, 1:28 AM
by globalnode on 12/29/23, 12:05 AM