-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
TTFs not recognized as monospace by mintty in Cygwin #474
Comments
Yep, that's exactly the issue. Looking at just RobotoMono-Regular.ttf:
(The letter "f" is 1 unit wider than other letters! This is definitely a bug...) |
Here's a slightly cleaned-up version of the script that I used to generate the above table: |
@markuspeloquin and @codeman38 thanks for reporting and triaging this issue! |
@davelab6 I can hotfix this via ttx, but then I'll be doing unknown visual things to some of the glyphs. I opened it up in Glyphs to take a look, and a handful of glyphs – i.e. dcaron – are going to be outside the bounding box. I'm just going to fix them in Glyphs so I can nudge some outlines around if necessary. |
Discussion in #1832 suggests that fixing this will be a bad idea as it will likely break other sites using Roboto. Sorry for the slow response @markuspeloquin and @codeman38: best plan appears to be a fix/fork of your own. |
I cannot select the Roboto font for Cygwin. I found this, indicating the problem is that mintty cannot detect it as monospace:
http://superuser.com/questions/887300/how-to-install-a-font-onto-cygwin-terminal#answer-1075786
I'm not sure how mintty decides a font is monospace. I noticed that fontconfig's
fc-query -f '%{spacing}'
is different for RobotoMono. All fonts with values for spacing:My guess is that the TTF contains at least one character with different spacing, so the TTF didn't get the monospace metadata.
The text was updated successfully, but these errors were encountered: