-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
post.isFixedPitch #132
Milestone
Comments
Ah, another downside of the way the ligs are formulated here (substitude two glyphs to one glyph with increased width) is Changing the ligature formulation would probably solve both (but I feel the pain in reformulating the ligs). |
Closed
Split off the notdef glyph width into #159 |
Fixed in ca8015b |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably you want the font to be detected as monospaced.
Apart from the missing Panose values
the font is not really monospaced, although it could be.
The width of the font is generally 1240.
The most obvious errors in being monospaced are:
.notdef
-> width 965uni2123
-> width 7440 (!!!)Apart from the wrong width (you could in principle just make the advance width standard and have a very big right side bearing), the glyph itself is questionable (see #51).
All the other non-conforming widths are from the ligatures.
Here a complete list of all glyphs with a differing width (patched the
fontforge
font generation code):The ligatures substitute multiple 1240 wide glyphs with one extrawide liga glyph.
That could also be formulated differently, so that the ligature glyph itself has the standard width but a
wide right side bearing, here a comparison for example with Cascadia:
They substitude
(
and*
byparenleft-asterix.liga
andLIG
, where bothparenleft-asterix.liga
andLIG
are of standard width,LIG
is just empty.You have a different approach. I'm not sure what is better; most fonts I have examined have the 'all glyphs have the same width' approach. At least with that approach it gets
isFixedPitch
set.The text was updated successfully, but these errors were encountered: