You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In macOS Font Book, there's a smart collection for Monospaced (Fixed Width) fonts.
I've tried to look into how this is determined, and I'm not sure. FontForge docs seems to say that it (FF) should decide for itself when the font is monospaced, although it also mentions some (OS/2?) setting for this, and I don't know if this would have an impact.
tl;dr it would be nice if Monocraft was automatically added to the Fixed Width smart collection in Font Book, and I'm not sure why it doesn't show up there.
The text was updated successfully, but these errors were encountered:
It seems that IntelliJ also does not recognise it as a monospace font.
In Settings -> Editor -> Colour scheme -> Console Font there is an option to only show monospaced fonts, and if that is on Monocraft does not show up.
Problem is due to #77. I'm having a bit of difficulty trying to determine how to emulate the character replacement that fonts like FiraCode use to get around this problem so I will likely need external help there. Let me know if this causes any problems with using the font.
IdreesInc
added
bug
Something isn't working
blocked
Blocked by another issue
and removed
potential-bug
This issue needs more context before it can be confirmed as a bug with this project.
labels
Dec 28, 2022
In macOS Font Book, there's a smart collection for Monospaced (Fixed Width) fonts.
I've tried to look into how this is determined, and I'm not sure. FontForge docs seems to say that it (FF) should decide for itself when the font is monospaced, although it also mentions some (OS/2?) setting for this, and I don't know if this would have an impact.
tl;dr it would be nice if Monocraft was automatically added to the Fixed Width smart collection in Font Book, and I'm not sure why it doesn't show up there.
The text was updated successfully, but these errors were encountered: