-
Notifications
You must be signed in to change notification settings - Fork 36
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
What is wrong with digits? #23
Comments
I guess it's a hinting problem. Are you using otf files or ttf files? I remember ttf files render better on Windows, while otf have some uneven numbers as shown in your picture. But it was from an old version though. Not sure how the latest one render on PC. |
I use Manjaro Linux. And I downloaded latest zip archive of this repo and unpacked it in my ~/.fonts folder. |
Can you check whether you're using the otf files or ttf files? This repo has both of them. TTF files are under the WEB directory. If you're using the otf version, try the ttf version. |
Soviet Man, we’re not going to change automatic TT hinting settings of Fira Sans for the final version, 4.3. But Fira GO will have basic manual TT Hinting. Your issue should be solved by that. |
Wow! What’s Fira Go? |
FiraGO is the new branch of Fira Sans. |
@atheistray, yes, you were right. Using TTF version fixes the problem, although I use Manjaro Linux, not Windows. |
@carrois, new font? Very interesting!
|
Only the normal-width Sans/Italic for now. But it is definitely a goal to go for more widths, styles, language support etc.
Very soon. We’re currently finalizing our new company/website/shop: bboxtype.com. |
FWIW, the problems shown here are probably from FreeType's autohinter being very strict about number glyphs needing to align to the same font unit height to be properly hinted. As in, the flat tops and round tops in 0123456789 need to be on the same height each. Seems fine in Fira Go from what I can see on a quick scan. |
What is wrong with digits? This is awful.
Zoom: 10x
Font = Fira Sans.
Size = 10
The text was updated successfully, but these errors were encountered: