Damien Guard

obviously 8x8 is comparably enormous but https://damieng.com/typography/zx-origins/ has a great collection of fonts

These are fantastic. For example, this one https://damieng.com/typography/zx-origins/zx-venice/ reminds me of "Lords of Midnight"[1]. Which was an incredible game which pioneered procedural generation so it just seemed vastly bigger than anything else I had played up to then. I never managed to keep my speccy alive for long enough in a single sitting to actually finish the game until one day the cassette just gave up entirely and I couldn't play it any more. [1] https://spectrumcomputing.co.uk/entry/0006604

Envy Code R is great. There is a power line version out there too. https://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-…

I also have a hard time understanding the question, but reading the text, it asks a different question: “The thing is I'm going to need to display stuff on it so I need character gloves and little graphics and stuff like that. Are there any standard glyphs or libraries for resolutions that small?” Because of that and the use of ‘one color’, I think/guess the OP has a 80×20 display that isn’t black and white (say a LED panel), and looks for fonts that can be used on it (I would go look at https://int10h.org/oldschool-pc-fonts/ or https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts, or look at old Mac and Windows bitmap fonts for those (warning: copyright laws may apply)) and, possibly, libraries to show an UI on it.

At least as early as 1977 the Commodore PET and the Apple ][ had "slashed zeros"; followed by the Atari 400/800 in 1979, the BBC Micro in 1981 and the Sinclair ZX Spectrum and Commodore 64 in 1982: https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts Uh, ok. Turns out it was the 12th and 13th century that it was first known to have been used! https://en.wikipedia.org/wiki/Slashed_zero#Origins

I have used Sudo and Monoid for years. Other fonts I like are: - Luculent, http://eastfarthing.com/luculent/ - Envy Code R, https://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-… B612 Mono would be an excellent font if the glyphs were well aligned.

It's not about whether you're actually printing it, the print version is just an accurate reference to the correct shape of how the font is designed. That shape doesn't necessarily line up on the pixel grid, so you can smush it around to get sharper edges on a computer screen at the expense of changing the shape/size/spacing of the font. Or you can follow the designed shape more correctly at the expense of smearing some stuff across multiple pixels. There are pros and cons to each, and which one you prefer is where it gets subjective. Some comparisons and discussion over here: https://damieng.com/blog/2007/06/13/font-rendering-philosophies-of-win… The Windows text has sharper edges but it looks funny to me in comparison.

There are two great blog-posts covering the typography in 8- and 16-bit systems (Commodore, Apple, Atari, Amiga, IBM, etc.): https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts https://damieng.com/blog/2011/03/27/typography-in-16-bits-system-fonts

See also these articles, for real old-school fonts: https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts https://damieng.com/blog/2014/07/20/typography-in-bits-other-english-m… Me, I grew up on Acorn machines, so those are my classic nostalgia font. Although, on a modern LCD with square-edged pixels, they look like arse --- jaggy and overly bold. I wonder if there's a way to emulate fuzzy CRTs with Truetype...

On Windows, requesting a particular font size is just a hope and a prayer. The OS will draw things at the size it thinks is best, with heavy-handed hinting, so the size of a rendered piece of text is quite non-linear with respect to font size: http://damieng.com/blog/2007/06/13/font-rendering-philosophies-of-wind… This makes it quite impossible for an application to implement a general solution to the problem. You pretty much have to treat HiDPI as another translation of the GUI with respect to sizing things.

I pulled Source Code Pro out of brackets a few weeks ago and loved it in Sublime, VS, and ConEMU on Windows and iTerm2 on the Mac. Then someone pointed me at Envy Code R [1]... I find it much more pleasing with the benefit of great differentiation between 0 O etc... http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r…

My favorite is the Envy Code R: http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r… I'm using it with full hinting enabled on Ubuntu/Xubuntu and it looks just as nice as the Windows screenshots on the homepage.

A trip down memory-alley with the Atari and ZX-81 fonts. ;-) This is the same person who has made Envy-code-R[1], my favourite font for the terminal and text editors. [1]http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r… Edited to add a link to the font.

A great font i've been using is envy code r. http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r…

Code Envy R is worth trying... you can get it here: http://damieng.com/fonts/envy-code-r

For code and console I love pixel fonts, so: Terminal 6px (included with all Windows) Envy Code A 7px http://damieng.com/creative/typography/envy-code-a I can't stand blurry fonts for code (especially since, at small sizes, text looks a blotch of blur). So, if I want small fonts (such as 6pixels by 8pixels) it better be pixel crystal clear hand tweaked. A font can do anti-aliasing or LCD based sub-pixeling, but that is more towards book reading / open office, than coding.

I don't personally use this at a large size, but I have found that it looks pretty nice even when large. http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r… I hope you find something that suits you. Best of luck.

The Droid family from Ascender, which Google commissioned for Android is uniformly excellent, renders well everywhere I've seen it and is Apache Licensed. I'm currently using 'Droid Sans' as a system UI font (on Linux) and 'Droid Sans Mono' for coding, terminals, etc... In fact I've just aliased the linux 'sans', 'mono', etc... to the appropriate Droid face. More info here, including the link to the git repo if you want to check the fonts out: http://en.wikipedia.org/wiki/Droid_fonts these are in the Ubuntu repo's as 'ttf-droid' or you can do a straight download from here: http://damieng.com/blog/2007/11/14/droid-font-family-courtesy-of-googl…

Both great! I would add Envy Code R: http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r…

my favorite programming font (and I think it is a pity that the article doesn't mention it): Envy Code R (http://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-r… I just love this font! it's such a beautiful piece of font-design and I only can recommend you to try it out!

I agree that there's substantial qualitative difference between sub-pixel antialiased text and the plain render. The former takes advantage of greater lateral resolution and perceptual differences between the primary colors. That said, I wouldn't consider the absence of that technique jarring. I intentionally change bright-on-dark text to greyscale antialiasing[1], to counter the halation[2]. All the links to images in the thread and the Reddit post you linked are dead, so I can't see how the text rendered for you. Did you by any chance experience this on a MacBook connected to an external monitor, where you had the system set up to render type better on the built in screen[3]? Your point holds though, they don't optimize for 3rd party hardware. I was a bit quick to jump in, thinking you were referring to the difference between their flavour of sub-pixel antialiasing and Microsoft's ClearType[4]. [1] https://srdjan.si [2] https://bootcamp.uxdesign.cc/why-dark-mode-isnt-a-ux-panacea-1590226e5… [3] https://cdn.osxdaily.com/wp-content/uploads/2018/09/font-smoothing-mac… [4] https://damieng.com/blog/2007/06/13/font-rendering-philosophies-of-win…

Even better download it, subset it then base64 encode it into your CSS for zero FOUC. https://damieng.com/blog/2021/12/03/using-variable-webfonts-for-speed/

Because almost all the early home computers supported lowercase. https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts/ The only notable exception I can think of is the ZX-80/81 which had notoriously rudimentary output capabilities because it was designed to be so cheap.

You can leave a row or two free for the descenders, and it doesn't look too objectionable. An 8x8 grid is plenty for a useful character set. Some examples: https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts/ There's even a couple of 6x8 ones here: https://damieng.com/blog/2014/07/20/typography-in-bits-other-english-m…

Sure but wget has a -D option to specify transitioning to other domains. So my command was actually something more like wget -m -D download.damieng.com,damieng.com -A .zip https://damieng.com/typography/zx-origins/ But it still wouldn't download the .zip files. I think this is one case where wget should, on paper, be superior to curl.

It was a historical distinction between the two OSes, even before Apple went all in on high-DPI. Basically, macOS uses "ideal" font rendering, meaning that all glyph shapes and overall text size is as if they were rendered with infinite resolution and then quantized using the pixel grid; when you increase font size, the text scales linearly. Windows, on the other hand, adjusts the shapes by snapping vertical and horizontal lines so that they correspond exactly to rows and columns of pixels. This distorts glyph shapes and spacing, but it makes small text (around 8-10pt) much more readable on low-DPI displays. (Coincidentally, this seems to be why macOS default UI font has always been a bit larger and thicker than Windows.) There are some screenshots to compare side by side here: https://damieng.com/blog/2007/06/13/font-rendering-philosophies-of-win…

That green check was in Borland Delphi too. https://damieng.com/blog/tag/delphi/

A similar article from a year ago: https://damieng.com/blog/2020/02/14/delphi-birthday-my-story (via https://news.ycombinator.com/item?id=24705109, but no comments there).

I used Envy Code R [1] for many years, recently I changed to Iosevka Term SS10 [2], which is kinda same. [1] https://damieng.com/blog/2008/05/26/envy-code-r-preview-7-coding-font-… [2] https://github.com/be5invis/Iosevka

Late to the party, but any idea what "inverse letter mode" in Rationale for Atari 400/800 is? https://damieng.com/blog/2011/02/20/typography-in-8-bits-system-fonts#…