The font ligatures are not working on XCode, if I use JetBrains Mono the ligatures work perfectly.

Hello how can "texture healing" be enabled on MacOS (system wide) or in Emacs?

I use gnome terminal and kitty.
I am not able to find monaspace font on kitty and gnome terminal..

Steps to reproduce in iTerm2 (3.5.20231109-nightly):

1. Preferences -> Profiles -> select profile -> Text -> Font dropdown
2. Select "Monaspace Xenon Var"
3. Select weight "Regular"
4. Result: Font weight appears to be Light:

5. Select weight "Light"
6. Result: Font weight appears thicker than "Regular":

Basically the title, I know this is probably more of a Visual Studio question but since it pertains specifically to this project, especially texture healing I thought it would be best to just ask here.

I've found that proportional typefaces (with variable widths rather than monospacing) are generally easier to read, even with code. However, proportional typefaces lack code specific features, like ligatures and differentiation.

I'm excited by Monaspace's texture healing feature, as it improves readability and reduces visual rivers in monospaced fonts. This could make it a great candidate for a variable font or custom axis that's spaced proportionally.

We should be able to start with default glyphs, and optionally use texture conflict data to adjust widths of glyphs dynamically, rather than replacing them with monospaced glyphs.

I really like the “texture healing” feature. I don't know if contextual alternates allow us to alter the glyphs based on the whitespace symbols nearby, but if it is possible, that would be a very logical thing to do.

An example:

Here we can see that the “M” by itself with the whitespace around it is narrower than the other Ms.

Add a script and instruction for Linux installation similar to the ones provided for MacOS

This is a glaring omission for an otherwise amazing set of typefaces.

I really like the examples shown in the Mix & Match section, using different font families for comments, Copilot suggestions etc.:

As I understand it from microsoft/vscode#36512, this is not yet reproducable in VS Code. Are there any plans to support that soon, perhaps via plug-in or by discussing support with the VS Code maintainers directly?

Monaspace offers a ligature for the character sequence /*, which looks good on its own, but when typing /** to start e.g. a Javadoc or JSDoc comment, only the first two characters get replaced by the ligature, the last asterisk remains unchanged and is now on a different height than the first one:

This does not look too aesthetically pleasing. Any chance we might find a ligature for the entire /** in a future version of Monaspace?

See title. Ideally on per-font-basis.

Can Italics be extended to accommodate:

• Italics within italics and
• Italics within italics within italics
• Left slanting italics
• etc.

Thanks a lot for making this font, and I can't wait to try it out! 🎉

However, I believe you would make it even easier for macOS users to install (and upgrade) your font via a brew cask instead of using a shell script. You can do this either by adding it to https://github.com/Homebrew/homebrew-cask-fonts, or by making a tap of your own including that cask. 🙇

Font does not always render properly for me. Seems to depend on family/size/settings used, but is very obnoxious. This is with Radon at size 14, weight 600:

Now a normal monospace font (Hack):

It also happens on the demo website (all default settings):

It doesn't happen for other users I talked to, so it may be an OS issue or something.
I'm using VSCodium 1.84.0 on Kubuntu 23.04

woff2 has better compression. I see that the variable typefaces have a woff2 version, but it would be nice if the individual fonts did as well.

❤️ this project, thanks.

How we can use the ligatures in PhpStorm (the most used PHP IDE)?

Hello!

This is somehow related to #6 but I would like to ask for a more generic one, I know some monospaced fonts are capable of mixing standard monospaced and handwritten style when the text is in comment block (probably they just change the italic variant?).

Could be build monaspace to allow that?
In my specific case, I would like to Argon for my code and Radon for my comments 🙏

Thanks for your awesome work ❤️

I know a lot of people really like ≠ as a replacement for !=, but I'm not among them. I was excited by the promise of turning off the ss01 stylistic set to avoid ≠, but it didn't work because (I think, based on the table on https://monaspace.githubnext.com/) it's also included in the dlig stylistic set, most of which I do want.

I think my ideal setup would be a way to opt into a space-adjusted glyph that's the inverse of the very nice =!, but out of ≠.

As stated.

Ligatures dont work

The glyph for U+2123 VERSICLE is a font version number indicator, currently “v1.000”. This violates the Unicode Standard’s conformance requirement about character identity. The glyph should instead be mapped to a private use character.

The website appears to only be available in a dark theme, even on systems with a light theme preference, which can affect accessibility. Additionally, the code samples can only be displayed in the dark variants of the Atom One and VS Code themes, which support light variants upstream.

Could there be alternative ligatures of <= and >=, whose equal signs are slanted, looking like ⩽ and ⩾? I guess there are many people like me who get more used to this style.

1. the quality font on phpstorm is a little bit bad
2. the ligatures does not work

Here, as you can see i have ligatures actived and does not work

Here the font does not look well!

First off congrats on the release, really liking the fonts! I saw that the ligatures changed the checkmarks and crosses in my .todo files using the todo+ extension. I'm not sure if this is intended as the characters were not in the ligature list on the site.

Works: (without ss03 without ss07)

Looks off: (with ss03)

Looks off: (with ss03 and ss07)

Here's the text:
☐
✔ @done(23-11-09 23:44)
✘ @cancelled(23-11-09 23:44)

edit: there is an easy workaround if this is intended:

  "[todo]": {
    "editor.fontLigatures": ""
  },

Could the width axis go to smaller values than 100? Narrow fonts are useful to show longer lines in a limited space. https://horstmann.com/unblog/2010-11-22/fonts.html

The baseline for some characters is much higher than the rest of the line.

In Sublime Merge on Windows using Monaspace Argon: (note the "X" is higher than "ML")

Description:

On the Monaspace website when viewed on desktop, the webpage is too wide, resulting in an undesirable horizontal scroll. This issue caused by elements styled with the 100wv value, which can be replaced with 100% to prevent horizontal scrolling.
Screenshots of the places that caused this issue attached.

Steps to Reproduce:

1. Access the website on a desktop browser.
2. Observe the horizontal scroll appearing due to the width styling.

Expected Behavior:

The webpage should not have a horizontal scroll on desktop view. Adjusting the styling from 100wv to 100% should resolve this issue.

Additional Information:

Browser: Google Chrome Version 119.0.6045.124 (Official Build) (64-bit)
Operating System: Windows 11 Pro x64 22H2

I'm using VSCode on Windows 11 and have the following in my settings.json file:

  "editor.fontLigatures": "'calt', 'liga', 'dlig', 'ss01', 'ss02', 'ss03', 'ss04', 'ss05', 'ss06', 'ss07', 'ss08'",

The .- and .= ligatures work but the ..< doesn't:

I tried with both "Monaspace Argon Var" and "Monaspace Neon Var" as the font family.

• As you see, when italics are used the pipe looks awkward.
• Vertical pipes are used in circumstances where they are supposed to sort of connect vertically, e.g. in ASCII tables
• It's inconsistent with other orthogonal shapes, like dashes etc, which aren't tilted either
• The vertical pipe may now be mistaken for a forward slash (this actually happened to me when someone else was reading code from my screen)

Some words that contain double letters look odd due to the texture healing. One example is the word "Humming". The two letters 'm' have a different width and one of them looks squished. Maybe do not do texture healing if it is a double letter?

You can see what I mean here:

First of all, thank you for a beautiful font family!

One small request though: Downloading 97MB of images together with fonts is rather unnecessary? I think it's enough to have the documentation examples online - no need to include it in the download zip.

See https://jsdoc.app/about-getting-started over how JSDoc comments are used. One common form is a one-line like

/** This is a description of the foo function. */

Which, when using the /* ligature is not rendering in a very pretty way:

I think it would be nice to lower the second * in a /** sequence.

I would expect that the font provides a clear distinction between - (U+002D HYPHEN-MINUS), − (U+2212 MINUS SIGN), – (U+2013 EN DASH), and — (U+2014 EM DASH). The screenshot shows that the first three of these glyphs look identical.

gvim under Linux only lets you select fonts that have the monospace flag set in the truetype header.
These fonts don't. So I can't select them in my editor of choice.

Please set the monospace flag in the header!

Can the Nerd Fonts added so we can use these fonts in the terminals?

It would be amazing to have these type of Icons included!

I want to see how it looks with Ruby source code.

Feel free to use this snippet:

class Person
 attr_accessor :name, :age

 def initialize(name, age)
   @name = name
   @age += age
 end

 def ==(other)
   @name == other.name && @age == other.age
 end

 def <=>(other)
   @age <=> other.age
 end

 def !~(other)
   @name !~ other.name || @age != other.age
 end

 def =~(other)
   @name =~ other.name && @age == other.age
 end

 def <<(other)
   @name << other.name
 end

 def >>(other)
   @age >> other.age
 end

 def **(other)
   @age ** other.age
 end

 def &&(other)
   @name && other.name && @age && other.age
 end

 def ||(other)
   @name || other.name || @age || other.age
 end
end

alice = Person.new("Alice", 30)
bob = Person.new("Bob", 35)

puts alice == bob # => false
puts alice <=> bob # => -1
puts alice !~ bob # => true
puts alice =~ bob # => false
puts alice << bob # => "AliceBob"
puts alice >> bob # => 30
puts alice ** bob # => 9000000000000000
puts alice && bob # => true
puts alice || bob # => true

Trying Monaspace Neon in VS Code, there is no difference with and without calt. For example the // ligature does not work. However, with dlig this ligature does work.

>>= is a popular operator used in the Haskell and Haskell inspired programming languages, although not as popular as other languages they still occupy a space in functional programming

Right now monaspace turns >= to a ligature, and >>= looks like >≥ which looks ugly in my opinion

Maybe a future version of the font could have the >>= ligature?

Title says it all, really.

Congratulations on the launch.

I'm developing a terminal emulator so whenever any monospace font is released, the first thing I do is jump on it and see how it all looks. I was especially interested because all the features Monaspace uses (variation axes, opentype features, etc.) are supported by my terminal so I wanted to make sure everything looked good. I immediately noticed that things looked weird, and then loaded the font in a variety of other terminals and verified they look a bit weird in all of them.

Some background (you may be aware of this): terminal emulators in particular aim to fit glyphs into a cell. Descenders do not typically descend below what is traditionally the baseline. Instead, the baseline is adjusted so that descenders at most touch the bottom of the cell. For example, in a typical typesetting situation, the bottom of the "g" hangs below the line into the next line. In a terminal, the "g" sits at the bottom of the cell, but does not typically enter the cell below it.

The way these metrics are calculated somewhat varies between terminals, but a common algorithm is:

cell_height = ascent + descent + leading
cell_baseline = descent + leading

where ascent, descent, and leading are directly from the font face.

If you look at a number of popular terminal emulators (macOS in this case, but similar things happen on Linux), this causes the glyphs to sit high in the cell. I've chosen two extremely popular terminal emulators as examples below, but I'm not trying to pick on them, this happens also in other terminals:

Kitty

iTerm2

There are various rendering artifacts but just focus where glyphs sit (since the other issues are likely not caused by monaspace). Notice that the top of the "h" is touching the top of the cell. The lowest part of the "y" descender is sitting quite high in the cell as well. The "N" is well above the midline because the baseline is so high.

I'm not 100% sure this is your fault, but each of these terminals use slightly different algorithms for calculating cell metrics and these algorithms work across hundreds of other known monospace fonts of varying popularity, but seem to have issues with Monaspace. So I wanted to raise this issue and perhaps discuss what can be done to help make Monaspace work better with these terminal projects.

Thanks!

In 1.0, the equal and colon characters are not vertically aligned which is unsettling for the := sequence used for example in Go.

It would be helpful to support more Unicode code points. My specific needs would be for combining diacritics.

I write a lot of scripts that use them in strings.

The fonts look great!

Add ".vscode" into the .gitignore file to fix this issue

one cjk width = two Latin char width

So I first followed the readme, for MACOSX & ran the bash file.
Then verified if I have all the fonts in Font Book -> they are there.

Using the following options in VSCODE:

"editor.fontLigatures": true,
"editor.fontFamily": "Monaspace, Arial, serif", // for testing

Also tried with the Monaspace _____

Result

Seeing Arial being used in the editor... Is there something that I'm missing?

Thanks in advance!

Not sure if I am misconfigured on something, the font characters go a bit high in a line, both in Kitty and VSCode:

❤️ this project so much, immediately switched to Monaspace Krypton 🤘

I haven't figured out how to get <=> to look right. This is used in Ruby and Python too.