Monocraft: A programming font based on the typeface used in Minecraft
github.com
github.com
Not a nice thing to do to a type designer or a foundry, but a gaming studio/Notch(?) won't probably care.
Have you considered writing a blog post about the process you used to make it, anything that set you back while working on it, and advice for others who may wish to generate their own fonts?
FWIW usually fonts variants are named '|font| Code' for ligatures version and '|font| Mono' for normal
but feel free to ignore reminded me of spectrum font ^|
Basically this is how my `~/.nethackrc` config look like:
OPTIONS=windowtype:curses
OPTIONS=autoquiver,confirm:false,hitpointbar
OPTIONS=popup_dialog,perm_invent,showexp,!autopickup
OPTIONS=boulder:0,color,fruit:burgerWhen I right click that image to open in a new tab, I get the grainy and indecipherable webp.
- iPad: two finger click, open in background (or long press, open in background)
- iPhone: long press, open in new tab
Both are reasonably crisp, though on iPhone I need to rotate to landscape unless I use a magnifying glass. :-)
- It makes me have to think too hard to figure out where the boundaries actually lie between characters when I want to edit. I don't want to think about how many times I'll have to press backspace to delete a single "character"; without ligatures, I don't have to think at all. - With ligatures enabled, I have to remember how to type each character-group (e.g., that != is the same as slashed equals). With ligatures disabled, I can just read it back from an existing example. In other words, ligatures create a separation between what I type and what I see. - It makes it hard to quickly compare my code to examples online that don't use the ligatures because, again, I'm forced to translate between what's on my screen and what's in the file.
The only ligatures I appreciate are minor stylistic ones, e.g., raising a colon slightly before a number, adjusting the spacing between two consecutive colons, raising two consecutive asterisks, etc. Changes that don't fundamentally change the code appears but make it a teensy bit more aesthetically pleasing.
You'd have to spend time finding and learning the "common" ground between every fellow developer you talk to.
Me. It’s the 21th century. It’s bad enough I have to use monospaced fonts because people can’t properly tabulate. I will at least have proper symbols rather than weird combination of glyphes.
Unfortunately, with monospace fonts many of these glyphs do not look nice to me due to the width constraint. Maybe a "multispace" font would be nicer while still preserving the grid alignment.
Software engineering is one of the few professions where you can use a hammer you designed yourself that fits your hand perfectly and is optimal for the task at hand.
Changes like this don't mean you're forcing other people to use your weird shaped nails, tho.
On the whole I think they're nice.
"First, the short answer in the USA: Typefaces are not copyrightable; bitmapped fonts are not copyrightable, but scalable fonts are copyrightable. Authorities for these conclusions follow."
I actually find it odd that "typefaces" are not copyrightable, but I think that's more of an historical quirk than some wise feature of the legal system.
Yes, and if you’re interested in learning more, the link above goes into considerably more detail than my excerpt on why scalable fonts/typefaces (typically used interchangeably, though technically a typeface is generally a family of fonts) are copyrightable in the US while bitmapped fonts/typefaces are not.
that's more of an historical quirk
I wonder how it does for people with dyslexia. I'm guessing not great.
On the topic, I recently learned about the Dyslexie font [0] as well as OpenDyslexic [1]. You can see the goal is to make characters easily differentiated. Not sure how I feel about these fonts—I can certainly read them easily, but I am not a fan of the style. There are other fonts I can read just as well which look better too.
2) it's meant to be rendered large enough that this doesn't matter
3) "bitmap" fonts always have compromises to fit the limitations of the grid
E: VS Code loves it though!