Letter "k" defect
Closed this issue · 10 comments
Letter "k" seems to have a little patch in it which I would assume should not be there.
This is in the varfont, right? (This shouldn’t happen with the standard ttfs.)
cc @m4rc1e
Yes, seems to be a varfont problem.
Varfonts of Vollkorn apparently are gonna be reworked currently (but not by me):
#28 (comment)
Hey, just out of curiosity, is this issue going to ever get addressed? It’s now present in whatever font version appears in Google Docs and it’s really irritating (having said that, I’m really digging the new weights and extra characters from version 4.1).
Also, not to pile on, but you can even see it on @FAlthausen’s personal website:
@m4rc1e
This is issue should now be fixed in today's new build. It appears that Glyphs to RF conversion has difficulty with the path directions with the outline structure shown below. Presumably it has to do with the crossover of outlines at the apex which occurs twice in the same contour. All styles should still be checked visually for possible occurrence in other glyphs.
Hey, I really hate to be a pest, and I know this issue was closed, but I do not see a fix on the Google Fonts site. This screenshot was taken just this second. Is the plan to just accept it? The issue has persisted for over a year now.
Confirming the fix was made to the /k on June 5, 2020
The /k in the current roman .ttfs does not have this overlap.
It does not appear in the VF file Vollkorn[wght].ttf with a visual check above 300 pixels.
https://github.com/TypeNetwork/Vollkorn-Typeface
It likely needs another push upstream. Last one was May 6th.
I see one open Issue related to broswers and service
davelab6#8