Comorant Garamond Incorrect path direction in 'e'
mrecord opened this issue · 12 comments
In Comorant Garamond, the crossbar on the 'e' has the wrong path direction and is showing holes in the letter.
It's visible in Mac Firefox and Safari, but not in Mac Chrome. (I didn't check in Windows).
Screenshot (from this page):
Weird, I’ve never seen that before, even on pages using Cormorant Garamond (and there are many of those!). Are you using the Google Fonts version?
My computer is currently broken, unfortunately, so I can’t look into it right now.
Cheers, Christian
Yes, it's the Google Fonts version.
Visible on the specimen page in 'e' and all components.
Ok, that’s bad. I’ll look into it.
In Comorant Garamond, the crossbar on the 'e' has the wrong path direction and is showing holes in the letter. It's visible in Mac Firefox and Safari, but not in Mac Chrome. (I didn't check in Windows).
Screenshot (from this page):
Are you using macOS 10.xx?
It has issues with rendering overlaps properly.
Sorry for dropping the ball on this. I can't see anything wrong with Cormorant's /e.ss02/, which is used in Cormorant Garamond. I hope it's a rendering fault as proposed by kenmcd.
Any new insights from your part?
Cheers, Christian
The font files from Google Fonts appear fine for me, but the font files from this repository have the issue with the "e" — perhaps you could update the font files in this repository with the ones that are on Google?
The font files from Google Fonts appear fine for me, but the font files from this repository have the issue with the "e" — perhaps you could update the font files in this repository with the ones that are on Google?
The fonts on Google Fonts have overlaps (like on the e above).
The fonts available here in the repo do not have overlaps.
So if you are seeing an overlap issue something else is wrong.
Exactly which font are you using?
What operating system?
What application?
Please provide a screenshot.
After looking a little closer, it appears there is no difference in this affecting the Google Fonts version vs. this repo's font version†, or even Cormorant Garamond vs. Cormorant; but rather the difference is between the .otf files and the .ttf files, at least on my macOS 12.6 computer.††
The .ttf files appear to have the correct "e" and "A";
The .oft files appear to have the wonky "e" and "A"
TTF — Cormorant-Bold.ttf
OTF — Cormorant-Bold.otf
This appears to be the case with all the other Cormorant versions, too.
† At least for me, since my experience seems to be different than previous posters.
†† Google Fonts version only provides the .ttf files which is why I didn't catch this initially — I was comparing the Google Fonts .ttf files to the .otf files from this repo.
OK. I see what happened.
The fonts in the repo were regenerated 8 months ago (May 6, 2022) by a GF rep using the GF tools.
The GF tools do not remove the overlaps (generally).
So the fonts in this repo now have overlaps still in them.
Which is usually not the case for upstream repo fonts.
Previously the fonts were generated from the font developers' font editor and the overlaps were removed when the fonts were generated.
I have been looking at these older repo fonts which have no overlaps.
These are the older fonts without the overlaps:
fonts.v3.614.(2021-10-20).from.master.zip
So those should work for you.
But I am surprised you have an issue with overlaps in macOS 12.6 - I thought this overlaps issue was fixed in macOS 11.
@CatharsisFonts Hi Christian,
You may want to regenerate the fonts with the overlaps removed.
Many users/applications still need overlaps removed.
Very interesting! I suppose the GF tools should be updated to remove overlaps, then...? (@davelab6)
@kenmcd @wavygecko New commit is available.
I checked the new .otf files and they look resolved now. Thank you! 🙂