-
Notifications
You must be signed in to change notification settings - Fork 92
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
Ovepass fonts doesn't look too good in Visual Studio 2017 #60
Comments
I'm having a similar issue on Debian Sid when displaying Overpass Mono Regular at size 9. I have tried all combinations of hinting (none, slight, medium, full) and anti aliasing (none, grayscale, subpixel), with identical results. The problem is not present at size 10 and above. |
I also have this problem on the browser. |
Reapplying the latest version of ttfautohint with the family-wide features
could help.
If that isn't enough, developing a ttfautohint controls file (
https://www.freetype.org/ttfautohint/doc/ttfautohint.html#control-instructions)
will be needed
|
Did you build the font from source on Debian Sid? I'm trying to make a debian package... |
or directly with https://packages.debian.org/sid/fontmake just that it fails for me for the latest font version |
The issue affects also Overpass Italic variants. |
Problem disappears when hinting the OTFs with https://github.com/adobe-type-tools/psautohint. |
I've installed the Overpass Mono font .otf file into my Windows fonts.
When I select Overpass Mono as the font to use in Visual Studio 2017, the end result does not look good at all. If you look at the attached screenshot, you'll notice that the font does not render well.
My question is whether this is because I'm using the font in Windows and nothing can be done, or something else to do with the font itself?
The text was updated successfully, but these errors were encountered: