Intel One Mono: a monospaced typeface designed with low-vision developers in the room

Designed with the audience the design is for

The README is explicit about who this typeface is for and that is the most interesting thing about it. The designers identified what it calls a typographically underserved low-vision developer audience, and Frere-Jones Type designed the typeface in partnership with the Intel Brand Team and VMLY&R. The stated goal was maximum legibility, addressing developer fatigue and eyestrain with the expectation of fewer coding errors as a result.

What makes that more than a marketing line is the process described alongside it: a panel of low-vision and legally blind developers provided feedback at each stage of the design. A typeface tuned for legibility by people who work all day in it, reviewed by the people who use it, is a different proposition from a corporate typeface decided in a review meeting.

The family covers over 200 languages using the Latin script, and ships in four weights, Light, Regular, Medium and Bold, each with a matching italic. That gives eight styles, which is a sensible amount: enough range for interface hierarchy and code emphasis without a weight axis that becomes a maintenance burden.

The licensing is straightforward for this kind of project. The fonts are free, released under an open source font license, and the tree carries an `OFL.txt` at the root, so the SIL Open Font License terms travel with the repository rather than living on a marketing page.

Programming ligatures exist but are off by default

The most requested feature arrived in release 1.4, and the choice to leave it off by default is the right one. Not every developer wants `!=` rendered as a joined glyph, so the ligatures live behind a stylistic set that you activate yourself.

To turn them on in VSCode, the README gives one setting:

"editor.fontLigatures": "'ss01'"

Sublime Text takes the equivalent through a `font_options` entry with the same feature tag. Once `ss01` is on, two more sets become relevant. Stylistic Set 2 switches the `<=` and `>=` combinations to arrow forms, which the README notes means the math contractions are the default otherwise. Stylistic Set 3 additionally activates a `www` ligature.

So there is a real choice inside the ligature feature: a conservative programming set that only joins the sequences readers already parse as single tokens, and an opinionated set that also redraws comparison operators as arrows. Anyone who has stared at a `<=` and found the two-character form easier to scan will want to know that option exists, which is exactly why it is not folded into the default.

Release 1.4 also added box-drawing glyphs, which matters more than it sounds for a coding font, since terminal and TUI applications draw borders with them and a font missing those glyphs produces broken layouts.

A raised colon, and the rest of the OpenType surface

The detail that tells you a designer actually worked in code editors is the colon. The README explains that the colon is automatically raised in operators so it aligns with mathematical symbols, and that for non-programming contexts the raised form can be applied contextually between numbers or turned on globally. The contextual option is Stylistic Set 11, and the global switch is either Stylistic Set 12 or `salt`.

Aligning the colon in `:=` or in an operator context is the kind of one-pixel decision that a general purpose font will never make for you, and once you see it you cannot unsee it.

The rest of the feature list is thorough in the way font repositories of this quality usually are. `ccmp` and `locl` handle correct display across languages, and the README advises setting the language tag in your software for best results. Superior and inferior figures are available through their Unicode codepoints, or from the default figures through the `sups` feature and `subs` or `sinf` for subscripts. Fraction numerals come from `numr` and `dnom`, with a set of premade fractions included.

Release notes add a few more to the documented set: `mark` for mark attachment, which matters for the Latin script coverage across 200 languages, and the `calt` contextual alternates feature introduced in 1.3 to handle the colon raising automatically.

Formats, size floors, and where the built fonts come from

The README is specific about which file format to use where, which saves you from picking the wrong one. The `.otf` and `.ttf` formats are recommended for desktop use, `.ttf` is also described as well suited to mobile apps, and `.woff` and `.woff2` are the ones optimized for the web.

There are size floors, and they matter more than a font's own opinion about its elegance. The recommendation is 7 points and larger in print, and 9 pixels and larger on screen. The README notes that the `.ttf`, `.woff` and `.woff2` files in the official release have been manually optimized for screen display to improve clarity and legibility, particularly on Windows platforms.

That last point is worth pausing on. Manual hinting is labour intensive work that font foundries often apply only to their commercial products, so a hinting pass on the screen oriented builds signals that the legibility goal was taken seriously rather than applied to the design only.

The 1.4 release notes fill in the technical inventory: 1,043 glyphs, eight styles across the four weights with italics, hinting applied to the TrueType and web formats, and no embedding restrictions. Version 1.3 was about language support and artwork refinement for characters including hyphen, en dash, em dash and grave, and version 1.2.1 was a packaging change that removed Mac specific metadata from the archives without changing the fonts themselves.

Editable UFO sources, and the interpolation workflow

The repository ships sources as well as builds, which is rarer than it sounds for a corporate typeface. Editable files live in the `sources` directory, with an `instances` subfolder holding a separate source file per style. They are `.ufo` files, an open human readable font source format whose specification is linked, and each one contains complete artwork, links to OpenType features in separate `.fea` files, and metadata such as naming and vertical alignments.

The README is careful to say these are not installable fonts but the sources that produce them, and it recommends RoboFont version 4.4, noting that many other font editors can open the format as well.

Underneath the instances you find `postscript` and `truetype` subfolders, holding the outline sources for the `.otf` format and for the `.ttf`, `.woff` and `.woff2` formats respectively. Since the outline drawing format differs between those two families, the README recommends using the PostScript sources for `.otf` output and the TrueType sources for everything else.

For edits that should apply across every weight, there is a more advanced path through the masters, which describe the extreme points of the design space, the lightest and heaviest weights for both roman and italic. Editing masters means rerunning interpolation, which relies on the `.designspace` files, an open XML based format, and the README recommends the Skateboard extension for RoboFont, or the free DesignSpaceEditor alternative. One constraint is stated clearly: masters are only available in PostScript format, so they are best for producing `.otf` builds.

Editorial conclusion

Intel One Mono is a well made coding font with an unusual amount of care behind it, and the design decisions are documented well enough to argue with. The raised colon, the ligature sets that are off by default, and the size floors of 7 points in print and 9 pixels on screen are all deliberate choices you can evaluate rather than discover. For most people the release builds are enough, and the ligatures are one settings line away. The repository also ships the editable UFO sources, which makes it a legitimate starting point for your own typeface work if you are comfortable with font editors. Note that the newest tagged release is 1.4.0 from July 2024 even though the repository itself has seen more recent commits.

Frequently asked questions

Official sources

1. intel/intel-one-mono on GitHub
2. Issues
3. License: OFL-1.1
4. README
5. Releases