MacOS doesn't identify CommitMono under Fixed Width/Monospace font when trying to install just the otf files

[vivek-dg]

I wasn't originally able to use CommitMono in Kitty since it couldn't identify the font files installed on my Mac as monospaced. I reviewed the homebrew .rb script, and it included only the OTF files for the latest version. When I downloaded them directly from the GitHub repository and tried pulling the entire folder into Font Book, it then started showing up. It would be great to have the Panose information updated to indicate the 'monospaced' nature of the font for Mac users trying to use package managers to sync workflows across systems. I tested this by opening up individual otf files in fontforge and updating the OS/2 -> Panose -> Proportion set to 'Monospaced' and things started working seamlessly. Thanks.

[dandudzi]

Same problem here. Could it be resolved?

[vivek-dg]

I created some python scripts to fix them but didn't find the time to update my fork/contribute back here. I can share them if you're interested.

[vivek-dg]

There are additional issues related to font family naming, since it splits the files into multiple families —CommitMono and CommitMonoV143, or something. The script fixes all of these.

[vivek-dg]

Please try these files and let me know. You will still need to drag the entire unzipped folder into your fonts. https://github.com/vivek-dg/commit-mono/blob/main/src/fonts/commitmono-1.143-autofix.zip

[vivek-dg]

Fixed the following using fontTools and a Python script and updated the file on the link above. Now the OTFs just load as Monospaced without loading the TTFs. Let me know if you see issues. I later found out that there is a problem with family names even on Linux. So this should fix both for Mac and Linux.

Fixes monospace metadata:
post.isFixedPitch=1
CFF topDict.isFixedPitch=true (for .otf)
OS/2.panose.bFamilyType=2, bProportion=9
OS/2.usWidthClass=5
OS/2.xAvgCharWidth = mode mono width (safe for all)
head.flags |= 0x0002
Reliable style detection (uses name table & fsSelection, weight as fallback).

[vivek-dg]

All of this still doesn't fix the vertical alignment issue in Kitty (and also in MacVim, as reported in a different ticket). For Kitty, the easy way to fix is to add 'adjust_baseline 2' in kitty.conf. For that to be fixed in the font, you would adjust the ascent, descent, etc. I'm planning to get a kitty-specific adjustment with a custom family name so it can be used in these types of TUIs. That's not yet ready.

[dandudzi]

@vivek-dg new font fixed + 'adjust_baseline 2' in kitty.conf resolved the issue and now I can see CommitMono and is read by kitty

[dandudzi]

@vivek-dg however, there is still an issue with mappings for italic and italic bold

There is a workaround that in kitty I can change it manually. This is for your info

[vivek-dg]

Glad it worked out. You're right about the font style names. Please explicitly declare the various font styles. I saw that Kitty didn't derive those names for several fonts, not just this one font.

[dandudzi]

@vivek-dg do you plan to release a new version on Brew?

[vivek-dg]

I haven't worked that out yet. I am yet to generate a pull request. If the maintainer of this repo accepts my changes, then it will be easy. Otherwise brew packages won't redirect to my branch. I have auto sync on my brew packages on various machines using chezmoi. So it'll surely be nice to fix it