Releases

  • 2.002
    Prerelease

    In the 2.0 major release, we’ve done a few major changes listed below:

    • The typeface is now distributed only in ttf format for desktop usage. The format gives us additional control over hinting especially on the Windows platform. It also enabled us to ship the typeface in a variable form.
    • The professional version ships with a typeface that has variable weight for maximum amount of control.
    • As a result of this rework, there are now two extra weights: SemiBold (600) and ExtraBold (800).

    At the time of writing, editor support for specific weights (say 460) is poor and if you refer to a specific weight like that, it’s possible the editor will round it to the closest (i.e., 500 in this case). Font names work still as usual.

    In addition to these major changes, the release also contains a few other features and multiple fixes and these have been described below.

    Features

    • Font weight is now variable by design
    • Script variant now supports Cyrillic and Greek. Within the Cyrillic version, the Russian script variant looks different than Bulgarian for example.
    • Additional currency symbols: Ukrainian hryvnia ₴, Israeli new shekel ₪, South Korean won ₩
    • 〈〉 (Angle Brackets) added
    • Rounder () (parenthese) available as stylistic set 08 (ss08)
    • #133: Progress bars have been added
    • #141: Alternate >= and <= added as stylistic set 09 (ss09)
    • #150: Previous version of curly braces {} added as option (ss07)

    Fixes

    • #32: Ligature .- permanently has been removed to avoid confusion
    • #131: Hinting === and !== ligatures have been optimized
    • #136: Ligatures <( and >( have been disabled due to conflicts with the <> combination
    • #142: #{, #(, #[ and ]# have been permanently disabled
    • #145: Most Symbols have been disabled to make OS emojis usable
    • #152: Issue with wrong sidebearing in italic hyphen has been corrected
    • Inconsistency in horizontal stems in Ь (Soft Sign) has been corrected
    • Inconsistency in horizontal stem in Ц (Tse) has been corrected
    • Inconsistency in vertical stem in Њ (Nje) has been corrected
    • Sidebearing inconsistency in ↑↗→↘↓↙←↖ (arrows) has been corrected
    • Vertical orientation of ‹«»› (Guillemets) has been adjusted
    • Minor node misplacement in f has been corrected

  • 1.808

    Fixes

    • Make sure the version metadata is correct in ttf as well (#132)

  • 1.807

    Fixes

    • Broken TTF render version 1.806 in Linux fixed (#128)

  • 1.806

    Fixes

    • Problem with multiple ‘greater’ or ‘less’ signs (<, >) now fixed (#109)
    • Vertical box/border symbols now adjusted to prevent discontinuity (#100)
    • Minus, Hyphen, and Endash revised for better distinction (#120)
    • Greek letters ψ (psi), φ (phi), γ (gamma), and π (pi) revised (#115)
    • Personal – Make sure zero is included to the build

  • 1.805

    Fixes

    • Font weights are broken in 1.804 TTF (#112)

  • 1.804

    Fixes

    • Font weights in ttf are wrong (#110)
    • BoldItalic 6 & 9 don’t render properly 1.803 (#111)

  • 1.803

    Features

    • Added: Arrows ↰↱↲↳↴↵ (upTipLeftArrow, upTipRightArrow, downTipLeftArrow, downTipRightArrow, rightCornerDownArrow, carriagereturn) (#104)

    Fixes

    • Construction of figures 6 and 9 altered to better match figure 8.
    • Design of ☜ ☞ ☝ ☟ (leftWhiteIndex, rightWhiteIndex, upWhiteIndex and downWhiteIndex) adjusted
    • Render problem with ligature #( fixed (#106)
    • Distinction between italic lower cases ‘o’ and ‘a’ optimized (#102)

  • 1.802

    Features

    • Added: Bash specific ligatures (#58)
    • Added: Cold Fusion Comments ligatures (#86)
    • Added: ‘Checkmark’ and ‘heavycheckmark’

    Fixes

    • Fixed: >= and <= ligature widths match other ligatures (#85)
    • Fixed: !== ligature renders well on low resolution again (#91)
    • Fixed: Powerline arrow elements are aligned correctly now (#96)

  • 1.801

    Fixes

    • Fix font weight in ttf (#89)

  • 1.800

    Starting from this release, there are features that are provided for plus or professional only. Certain features and all fixes will still be available for the personal version as well.

    Features

    • Plus - Added script variant as alternative to italic (stylistic set ss02, ‘script variant’)
    • Plus - 1st alternative ‘g’ (stylistic set ss03, ‘alt g 1’)
    • Plus - 2nd alternative ‘g’ (stylistic set ss04, ‘alt g 2’)
    • Plus - Alternative ‘ß’ (stylistic set ss05, ‘alt germandbls’)
    • Plus - Alternative ‘@’ (stylistic set ss06 ‘alt @’)
    • Regular italic ‘k’ construction altered
    • A small adjustment to Light master of upright ‘r’
    • Added ||= ligature

    Fixes

    • ‘Non-breaking space’ added (#80)
    • Ligatures including or referring to [] or {} fixed to match in height (#78)
    • Diagonal stroke in ‘notequal sign’ and similar lengthen for better distinction (#72)
    • All Brackets are now aligned to match upper case letters

  • 1.700

    Features

    • New symbols: Pointing index hands (black, white, all directions)
    • New ligatures: |-> and |= (#68)
    • Curly brackets have now more open shapes { }

    Fixes

    • Position of period in ligatures .- ..= .= has been adjusted to render better
    • #24 and #38 have been addressed by employing ‘natural’ rather than ‘quantized’ gridfitting to deliver a smoother scaling across sizes

  • 1.604

    Fixes

    • Horizontal stem of letter f has been lowered in the second and the third master to render better in low pixel sizes
    • Minor inconsistencies have been fixed between upright and italic variants

  • 1.603

    Fixes

    • Positions of dots of letters i and j improved to render better in low pixel sizes #55
    • The font name shows up correctly under Windows now as MonoLisa instead of MonoLisa Bold #42

  • 1.602

    Improvements

    • f – The top shape has been made more open so that the character flows better with others

    Fixes

    • i and j – the spacing between the letter body and the dot has been increased. Now the characters look better on low resolution displays

  • 1.601

    Features

    • /** ligatures are now JSDoc compatible and balanced. Example:
    /*
 * Multi-line code comment
 */

/**
 * JSDoc comment
 */

    Fixes

    • Copyright (c) ligature has been disabled as it’s not useful for coding. #44
    • The terminals of the italic “f” character have been balanced to work better in common combinations like if or fi. #8

  • 1.600

    Fixes

    • TTF rendering should not crop on Windows anymore (#34)
    • ^ and ~ are easier to distinguish (#7)

    Features

    • Added ‘Normal asterisk’ (*) in ss01 (Stylistic Set 01)
    • Added ‘Slashed zero’ (0) in zero
    • Ligatures have been split into two sets - calt (contextual alternates) and liga (ligatures) to reflect the character meaning better.

    Ligature Sets

    Ligatures have been split into contextual alternates (calt) and actual ligatures (liga). Contextual alternates (calt) change only spacing between characters while ligatures (liga) replace combinations with different shapes.

    When you enable ligatures, both are enabled in editors like VS Code and WebStorm. Consider the VS Code configuration below:

    {
  "editor.fontLigatures": true
}

    In order to control which features to enable in VS Code, you’ll have to set configuration as below (standard CSS syntax):

    {
  "editor.fontLigatures": "'calt' on, 'liga' off"
}

    Stylistic Sets

    Stylistic sets are a new feature that allow us to refine the glyphs in the future and let you choose the customizations you prefer since sometimes a specific way of rendering a character might fit your preferences better.

    To use them in browser, consider the following CSS:

    .stylistic-set-1 {
  font-feature-settings: "ss01";
}

.stylistic-zero {
  font-feature-settings: "zero";
}

    To enable them in Visual Studio Code, configure its settings as follows:

    {
  // Enable stylistic sets for all languages
  "editor.fontLigatures": "'ss01', 'zero'",
  // Enable stylistic sets for a specific language
  "[javascript]": {
    "editor.fontLigatures": "'ss01'"
  }
}

    See VS Code issue 80577 for further information and technical details.

    It’s not possible to control the enabled features in many of the popular editors yet. Please get in touch with the creators of your editors to make them aware of this so that more control may eventually be added.

  • 1.500

    Support for new languages

    • Azerbaijani
    • Cornish
    • Esperanto
    • Greenlandic
    • Kurdish
    • Nahuatl
    • Old Icelandic
    • Old Norse
    • Pinyin
    • Sami
    • Vietnamese
    • Zarma
    • Zazaki

    Features

    • New symbols - ➲☁☇☠☹☺☻☼☾♥❄⎇⎋🌐🌧🌩💳🔒🔓⇪⌧⌫⌦⏏⌨⌥⌘⏎⏻⏼⭘⏽⏾⎙
    • New ligatures - ''' and """ - Issue #2

    Fixes

    • Ligatures are now aligned vertically to match each other
    • General vertical text alignment has been fixed - Issue #5

  • 1.401

    Fixes

    • Cyrillic ъ character - Minor interpolation error corrected.

  • 1.400

    Features

    • Cyrillic languages are now supported including Bulgarian, Ukrainian, Russian, and Serbian
    • Greek is now supported
    • New symbols - Box drawing elements
    • New symbols - Block elements
    • New symbols - Geometric elements (circles, squares, triangles, …)
    • New symbols - Arrows
    • New ligature - ||
    • Optimized TTF files are now included as the file format works better for Windows users

    Fixes

    • Position of various brackets in ligatures have been adjusted in height to match regular brackets
    • Now <> and </> ligatures match in height and their angular inconsistency has been fixed
    • === and !== ligatures render correctly now

  • 1.303

    Features

    • Improve font rendering in Ubuntu by reducing V and H standard stems and fixing zone extension to one unit

    Improved font rendering in Ubuntu

    Fixes

    • Fix font rendering in Ubuntu by improving hinting behavior #6

  • 1.302

    Fixes

    • Fix font rendering in WebStorm by changing font file naming.

    Fixed slant

  • 1.3.0

    Features

    • Add support for three more block elements (shadelight, shademedium, shadedark)

    Fixes

    • đ ħ ŧ - position of bar in bolder styles.
    • f - position of horizontal stem in bolder styles.
    • Make the branch glyph slightly wider.

  • 1.2.0

    Fixes

    • e - Altered position of middle stem do have better balance between upper and lower white space
    • i - Increased height of i dot to achieve better distinction
    • Diacritics/Accents: Same procedure as with i dot
    • Center accent characters

  • 1.1.0

    Features

  • 1.0.0

    • Initial version

What Developers Say

Gant Laborde
Gant LabordeCIO at Infinite Red

As a consultant, an instructor, and a presenter, having a clean and engaging mono font is paramount, and MonoLisa delivers information perfectly to everyone without forgetting to sneak in some personality in a gentle smile.

Kyle Welch
Kyle WelchSenior Software Developer at Eventbrite

MonoLisa is now my go to font for all places. It has become my expectation in my terminal and code to the point that seeing other fonts confuses me. From the well designed and unique characters make it simple to parse and read throughout the day.

Horacio Herrera
Horacio HerreraIndependent consultant

This font is so sharp that the readability of my code increased a lot! Definitely a font I will use for a long time.

Max Stoiber
Max StoiberFrontend Developer at Gatsby

I love it ♥️

Mark Dalgleish
Mark DalgleishDeveloper at SEEK

I’ve been using MonoLisa as my editor font for the past few months. After a small adjustment period, I really grew to love it. Going back to any of my old font choices feels like a downgrade in comparison.

David Khourshid
David KhourshidSoftware developer at Microsoft

I’ve been using this font for months, and while the slightly wider nature of this font took a little getting used to at first, it eventually grew on me and I saw how well this font works with my daily workflow. A great, quality font and I highly recommend it!

Sara Vieira
Sara VieiraEngineer at CodeSandbox

As someone with an eye condition this font makes my life way easier. And not just in coding but even in design since it doesn’t only carry regular but the whole set of weights so you can even use it in design, logos or anything a monospace font makes sense.

Cassidy Williams
Cassidy WilliamsTeaching and coding at React Training

I switched to MonoLisa after trying out several different fonts in my terminal and in my IDE. As a coding instructor and speaker (and just someone who codes a lot in her free time), readability is always the most important thing to me in a font.

Kent C. Dodds
Kent C. DoddsMaking people's lives better with software

I’m not much of a font guy, but after using this font for just a few days it’s grown on my and I really like it. (And people wasted no time in constantly asking me what font I use). Two thumbs up 👍👍

Dominik Sumer
Dominik SumerCo-Founder of seriouscode.io

Love the aesthetics of the font and how it improves code readability. That’s why we’ve also decided to use it as the default font at snappify.io

Michał Popek
Michał PopekFrontend Developer

I had been struggling with some vision issues before and MonoLisa really helped me a lot by taking a lot of strain off my eyes.

Caleb Porzio
Caleb PorzioCreator of Alpine.js

MonoLisa is the perfect coding font IMO. Spacious, stylish, and super readable. I never pictured myself having such strong feelings about a font, yet here we are.