I built a custom Python-based procedural engine to generate the weights because I wanted more logical control over the geometry. It currently has 700+ glyphs and deep math support.
Regular weight is free for the community. I'm releasing more weights based on interest.
Also would like to see more examples, say including this deep math.
EDIT: The joke wasn't that bad. :(
so i just use reportlab and i just created custom drawing classes for lines and arcs, which takes in a variable "weight" that controls the "thickness" of the line it draws...
and then after you generate the "basics" (A-z, digits and some basic shapes like dots and whatnot), almost all the remaining glyphs are just some (scaled) combination of those glyphs, in some way or another... and i made like a "map" of that...
does that make sense?
There are a few odd things about this post though. Take this as well-intentioned feedback.
- New account. No previous submissions or comments.
- New Github account. No previous activity.
- Mentions custom engine (cool!), but omits any details.
- Calls other mono fonts 'fugly'; refuses to elaborate.
- Releasing based on interest feels like engagement farming. Let me know when it's done. Then I'll judge whether I'm interested.
- Regular weights are free. Implication is that other weights will be paid. That's fine. I'm happy to pay for fonts. But I'm unlikely to try a font in earnest without bold and italics.
Sorry if this comes off as harsh. I wish you the best with this!
Your documentation should definitely list the Unicode code points / glyphs covered, for people to get an idea which scripts are supported.
Also, the repository has a LICENSE file with the MIT license text, but the actual font file (.ttf) embeds the information that it's licensed under SIL Open Font License 1.1. One of these two pieces of information needs to be corrected.
EDIT: As many people have said, the "custom Python engine" would be far more interesting than the font itself.
fimdomeio•2w ago