Monospaced fonts for programming. This Github page is now the official home of the Proggy fonts.
The fonts are all fixed-width and designed for programming. They were optimized while writing C or C++. For this reason, characters like the * are vertically centered as * usually means dereference or multiply, but never 'to the power of' like in Fortran.
The {}s are centered horizontally (in case you align braces vertically), the zero looks different from the capital oh, and there is never any confusion between ells, ones, and eyes.
Additionally, the arithmetic operators (+ - * < >) are all axis-aligned... unlike the last ones you just saw.
New for 2019 is a vector (scalable) version of Proggy Clean Slashed-Zero. Proggy Vector comes in woff, svg, eot, ttf (with Mac variants), and otf (with Mac variants). Here is a sample.
In 2023 some cleanup to Proggy Vector was made to normalize all glyph widths, distribute a woff2 export, and include 8-dot braille. This change bumped the version to V1.1.6 for Proggy Vector.
A further update in 2023 has bumbed the Proggy Vector version to 1.1.7. This change adds a dotted-zero version of Proggy Vector. Both the regular (crossed-zero) and dotted versions have cleaned-up alignment/paths of some glyphs. In addition the TTF versions are now tagged correctly as monospaced and will appear bolded in font-selection dropdowns in IDEs like Visual Studio.
There are two variants of Proggy Vector. The first is Proggy Dotted -- it is a conversion of Proggy Vector with the dotted zero. Proggy-Regular has a crossed-zero.
Proggy Vector is a modified version of the Hack Font. The modifications were made using the Bird Font editor and Font-Forge. Both the modifications made by SourceFoundry for Hack and my subsequent modifications are licensed under MIT. However, Hack started life out elsewhere, so please read the licensing information in ProggyVector_License.txt. There's nothing arduous.
The web format woff/woff2 file was generated by importing the otf into FontForge and exporting. I have also included the FontForge (.sfd) project file in case anyone would like to make further edits.
Windows appears to do a better job rendering ttf fonts over otf versions (even though otf supports cubic beziers which should not be approximations of the authored curves). Point size 10 of the ttf works well for me in Visual Studio. Here's a sample.
Note the 100% at the lower left.
The original bitmap fonts are distributed as ttf, fon, pcf, and dfont files. The fon format works well with Visual Studio, a command prompt, Photoshop, etc. Some editors do not recognize fon fonts in which case you should use the ttf version (12pt PC, 16pt Mac). Not all fonts are available in all formats.
The original fonts are pixel-based and only look good at a particular point size. The ttf fonts should be used at their intended point size as they are basically conversions of the pixel based bitmap versions. These fonts will not benefit form having ClearType turned on. You're better off using some other ttf font that is curve-based and not pixel-based if you want sub-pixel anti-aliasing.
Most fonts contain the Latin-1 character set (ISO 8859-1) except ProggyCleanCE.ttf which can be used for the Czech language (Latin-2). You can try it if the characters you want are missing and you were able to read English enough to understand this paragraph.
The two Webby fonts are not monospaced, but may be useful for other purposes like websites.
Contributed fonts that were hosted by the original proggyfonts site are found in the Contributed directory. The licences, if originally supplied, are inside the zip files.
The contributed fonts include:
- CGMono
- CodingFontTobi
- Crisp
- Dina
- Opti
- PixelCarnageMono
- ProggyOpti
- Progsole
- Speedy
