-
Notifications
You must be signed in to change notification settings - Fork 39
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
A lot of Kerning inconsistencies #59
Comments
+1 Was about to use this, but "2019" also ended up with poor kerning. Hoping this can be fixed. |
Hi all, thanks for pointing this out. I think this broke because I brought in kerning from iKern but didn't bring in the classes? I will have to look. But honestly it's not a lot of masters, I should just re-kern the whole thing once I fix the other glyph-level issues. |
Thanks for reply. That's what I did in FontLab ;) Manually re-kerned the missing pairs |
this is fixed in https://github.com/jpt/barlow/tree/1.5 - I have rekerned the font. new font binaries coming soon. |
binaries available here for testing: https://github.com/jpt/barlow/tree/1.5/fonts |
Seems to be improved now 👍 |
There still seems to be some issues in the black italic variant. A few of the pairs I think it is a bit off between:
|
I had a quick look among the upright characters as well. Based on the previous listing I find that at least these are quite noticeable there as well:
These are less so:
The slant being applied in the export can be one potential cause, but I would guess there still might be some issues among the upright versions. This is in no way a comprehensive "inspection", just a few I noticed in a current personal design I'm working on :) |
yeah, there are multiple issues with the way I set up Kern On (as based on previously set pairs) — this is all on the list :) |
First of all I love this font, but it breaks my heart when I see that kerning tables are still half baked. At least it's what's FontLab is showing. Freetype2 library is making it even worse at small sizes, unfortunately.
The text was updated successfully, but these errors were encountered: