Could be cool to to let people customise without having to download first and use font squirrel - anybody with the skill to create the opentype flattening server side ?

Or any other clever idea how to do this?

Hey, so I saw your article today and thought I'd give this font a shot. However, trying it on Archlinux I see glyphs getting mixed up. Here's a code snippet with Envy Code R: vs Monoid . I see * and x and = and ≤ getting mixed up. Additionally (not visible in the screenshot), '<' displays as a space.

Another guy on the #archlinux IRC channel also gave it a shot and he sees similar problems. https://i.imgur.com/Mvjsf0W.png

This is the PKGBUILD I used (from AUR). Not sure if this is a correct way to build the font, but even if I replace the build line to python3 ./build.py and package all the resulting ttf files, I see the same problems. The patch just replaces a few instances of xrange with range to get the thing to run.

First try available now in 0.24. This is what I have so far.

What I need is

• [x] Feedback on the design
• [x] Any examples of fonts where 3, З and Э are clearly distinguishable? *
• [x] Any missing characters?
• [x] Russian code samples for the website in one of these languages: markup+css+clike+javascript+python+ruby+swift

*The best I've found is PT Sans but this requires a different 3 - does coding programs generally "know" you're writing e.g. Russian so I could use language based substitution?

PT Sans

i noticed that Monoid appears very thin when viewed on a retina monitor, like the 2015 retina iMac. (Also, I am running OS X "El Capitan" Public Beta 2, and there are some font issues in this build, so it may be related to that, not sure. Unfortunately I don't have another retina mac to test this on.)

I seem to have a harder time reading the thin retina version all day long. The non-retina version seems to flow much better. (I was using Monaco prior to switching to Monoid, because it had more substance to it than other developer fonts seemed to have.)

To illustrate the difference, I took a pic of the same text on retina and on normal using my iPhone (just to be clear if there are any technical ramifications):

Non-Retina:

Retina:

(Not sure why the previews are upside down.)

Tried to install the four fonts (bold, oblique, regular, retina) from http://larsenwork.com/monoid/ on Windows 7, but I can see only bold and oblique.

smells like related to #23 and maybe #22

As people who look in the source may have noticed I've been fiddling with Monoid Bold and just wanted to share a screenshot.

I'm trying to keep it over the same grid so typographically I'm making all sorts of mistakes but I wanted to see if it was possible to make it just as crisp as the normal weight.

The Trema (two dots) above the Umlaute ÄÖÜÏËŸ (capital) are too high, so that they are towering into the previous line. Tested with Monoid downloaded from your website yesterday (LineHeight M, Normal Font, Ligatures off) under Ubuntu/Linux in Atom and GVim (and in Konsole) with lineheight=1.

As one can clearly see in the screenshot, the dots seem to be cut off in the middle by line-highlighting, and clashing with the lower j,g,p,q etc.

Using the XL-Lineheight font seems to "fix" this issue, but then the other Characters are too far apart.

@chase obviously :smile: Is this possible? I just created the 0.55 branch to work on some features and leave the master branch for bugfixes and minor upgrades.

Running with error

But continues instead of stopping

I pushed an update to master immediately after so I didn't get to check the release branch after the 0.55 build ran.

Some research:

font.gsub_lookups =

("'liga' Standard Ligatures lookup 0", "'calt' Contextual Alternates lookup 1", 'Single Substitution lookup 2', 'Single Substitution lookup 3', 'Single Substitution lookup 4', 'Single Substitution lookup 5', 'Single Substitution lookup 6', 'Single Substitution lookup 7', 'Single Substitution lookup 8', 'Single Substitution lookup 9', 'Single Substitution lookup 10', 'Single Substitution lookup 11', 'Single Substitution lookup 12', 'Single Substitution lookup 13', 'Single Substitution lookup 14', 'Single Substitution lookup 15', 'Single Substitution lookup 16', 'Single Substitution lookup 17', 'Single Substitution lookup 18', 'Single Substitution lookup 19', 'Single Substitution lookup 20', 'Single Substitution lookup 21', 'Single Substitution lookup 22', 'Single Substitution lookup 23', 'Single Substitution lookup 24', 'Single Substitution lookup 25', 'Single Substitution lookup 26', 'Single Substitution lookup 27', 'Single Substitution lookup 28', 'Single Substitution lookup 29', 'Single Substitution lookup 30', 'Single Substitution lookup 31', 'Single Substitution lookup 32', 'Single Substitution lookup 33', 'Single Substitution lookup 34', 'Single Substitution lookup 35', 'Single Substitution lookup 36', 'Single Substitution lookup 37', 'Single Substitution lookup 38', 'Single Substitution lookup 39', 'Single Substitution lookup 40', 'Single Substitution lookup 41', 'Single Substitution lookup 42', 'Single Substitution lookup 43', 'Single Substitution lookup 44', 'Single Substitution lookup 45', 'Single Substitution lookup 46', 'Single Substitution lookup 47', 'Single Substitution lookup 48', 'Single Substitution lookup 49', 'Single Substitution lookup 50', 'Single Substitution lookup 51', "'ss01' Style Set 1 lookup 52", "'ss02' Style Set 2 lookup 53", "'ss03' Style Set 3 lookup 54", "'ss10' Style Set 10 lookup 55", "'ss11' Style Set 11 lookup 56", "'ss12' Style Set 12 lookup 57", "'ss13' Style Set 13 lookup 58", "'ss14' Style Set 14 lookup 59", "'ss15' Style Set 15 lookup 60", "'ss16' Style Set 16 lookup 61")

font.getLookupInfo to get tuple with type (first tuple item). Iterate lookup table checking for 'gsub_ligature', 'gsub_contextchain'

font.removeLookup to remove item by name passed to getLookupInfo.

Have you signed up with CircleCI? It doesn't seem to be working, but I can't tell if it is failing if you don't let me know or figure out a solution. It was working for me, but I don't have the ability to test it on this repo as a collaborator.

Typing a word that includes "mm" produces a weird ligature. For example, the word "programming" ends up looking like this:

This is annoying enough when it appears in comments, but it's absolutely maddening when attempting to use a time format that includes something like "HH:mm:ss". This makes the time format appear to be simply wrong even if it's correct and works.

This is using Monoisome, in Xcode, on OS X.

I've installed Monoid on Arch (community/ttf-monoid) but the Retina and Regular weights look exactly identical - despite the Retina one saying Light in pango-list. I was hoping for a thinner weight. Anyone else seeing this, is this correct?

❯ pango-list | grep Monoid
Monoid (monospace)
  Retina:       Monoid Light Semi-Condensed
  Regular:      Monoid Semi-Condensed
  *Bold Italic: Monoid Bold Italic
  Bold:         Monoid Bold Semi-Condensed
  Italic:       Monoid Italic Semi-Condensed

Hi, due to the nature of my work I would really appreciate if U+0307 and U+0308 unicode characters combined well with all letters in the latin and greek alphabet.

I am using SublimeText if that is relevant to the issue.

Hi. This is a very nice font. I am trying to set Retina version in vscode and I am setting "Monoid Retina" as "editor.fontFamily" value but It isn't working. Please help me. Thanks OS: linux, Editor: vscode

Update : After listing installed fonts my machine, If you noticed all of theme has same name but different style and I think in this case editor can not pick the correct font based on font's name : /usr/share/fonts/truetype/monoid/Monoid-Italic.ttf: Monoid:style=Italic /usr/share/fonts/truetype/monoid/Monoid-Retina.ttf: Monoid:style=Retina /usr/share/fonts/truetype/monoid/Monoid-Bold.ttf: Monoid:style=Bold /usr/share/fonts/truetype/monoid/Monoid-Regular.ttf: Monoid:style=Regular

But If you look at firacode font configuration in my machine there are different names for every specific font: /usr/share/fonts/truetype/firacode/FiraCode-Bold.ttf: Fira Code:style=Bold /usr/share/fonts/truetype/firacode/FiraCode-SemiBold.ttf: Fira Code,Fira Code SemiBold:style=SemiBold,Regular /usr/share/fonts/truetype/firacode/FiraCode-Retina.ttf: Fira Code,Fira Code Retina:style=Retina,Regular /usr/share/fonts/truetype/firacode/FiraCode-Medium.ttf: Fira Code,Fira Code Medium:style=Medium,Regular /usr/share/fonts/truetype/firacode/FiraCode-Regular.ttf: Fira Code:style=Regular /usr/share/fonts/truetype/firacode/FiraCode-Light.ttf: Fira Code,Fira Code Light:style=Light,Regular

So for example If I want to set firacode font with retina style, I just use "Fira Code Retina" name. So The question is how to set Retina style for Monoid font?

I downloaded Monoid about a year ago. Today, I noticed at some comments in old code, that the width of some characters actually differs from the width of most other characters. Take the following text and apply the Monoid font to it:

  //     (X+)                            (X+)
  //      ╔══╗                         ╔══╗
  //      X  Y                         X  Y
  //      XObX                         XObX
  //      ║je║                         ║je║
  //      ║ct║                         ║ct║
  //      ║ 3║                         ║ 3║
  //      o══╝─(Y+)─>                  ╚══o──(Y+)─>
![monoid font](https://user-images.githubusercontent.com/18487427/106360158-3d5f8580-6317-11eb-9906-00c722747d18.png)

The alignment here in GitHub, in MS Word and in VS 2019 look well, if Courier New, Consolas or other monospaced fonts are used. With Monoid, the vertical alignment of the boxes is broken (Screenshot from MS Word):

I am using Monoid in Eclipse IDE. Unfortunately error and spelling underlining does not work with Monoid. Probable reason (actually confirmed by playing around) is Underline position being bigger by value than Descent. It's height is also huge when compared to other fonts. As a side note - a fraction bigger line spacing would improve readability of the text.