-
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
Windows rendering issue: bold 'e' characters #55
Comments
Hi @davidfurlong - thanks for opening the issue, I'll look into it. In which browser and version of Windows is this happening? |
Chrome & windows 10 - thanks for looking into this. We've experienced this across multiple devices and you can directly reproduce on deedmob.com on these versions if you'd like |
Hi @davidfurlong -- thanks for the additional information, I'm looking into it. I wonder if this fix works as a temporary solution? https://coderwall.com/p/9tecwq/fix-poor-font-rendering-in-chrome-on-windows |
Thanks for looking into it |
Hi @davidfurlong -- it looks like there was an error with the "virtual masters" for the letter "e" in the source file that I think caused some bad autohinting-related metadata. I've fixed the source and generated new WOFF2 binaries -- can you let me know if the attached files fix your problem? Click to download -- woff2.zip If this works I'll go ahead and push out a new version of Barlow. Thanks again for opening the issue. |
hey @jpt I appreciate you looking into this and finding a possible resolution. I'll be honest, we decided to switch out barlow for another font due to this issue and I don't have access directly to a windows environment -- therefore its prohibitively time consuming for me to now try to see if the above font download fixed the issue. I hope you can find another reproduction environment and I'm sorry to drop this on you |
@davidfurlong -- no worries at all, I appreciate bug report! I'll spin up a VM to give it a proper evaluation. |
Thanks @briandipert -- can you give these a try? Also, can you let me know if WOFF (not WOFF2) files have the same problem? |
@briandipert thanks so much for the report, you've helped me identify the problem: the latest version of Barlow's WOFF and WOFF2 files are using OpenType outlines instead of TrueType outlines, so ttfAutoHint is not being applied / Windows compatibility has suffered. I'll get a new version up shortly. Thanks again for the help! |
@jpt Could you give an estimate on when this issue might be fixed? Thank you! |
@jpt do you have a TTF file of the latest version of Barlow? |
Hinting has been updated in the source, I will generate new TTF binaries soon: https://github.com/jpt/barlow/tree/1.5 |
new TTF files can be found here: https://github.com/jpt/barlow/tree/1.5/fonts/ttf |
I've tried to test the TTF files on http://www.cyreal.org/Font-Testing-Page/ (drag-n-drop) but they are not loading correctly. The OTF versions seem to load ok. I don't know if its Cyreal's page fault, or something in the TTF is strange. Previous Barlow TTF versions load correctly in that page. Another testing page: http://webfont-test.com/ is also not working on the new TTFs. |
Looking into the TTFs, thanks for letting me know |
Hi @agusmba — can you give the latest TTF files here a try? I think it will fix the issue. Thanks all in this thread for reporting Barlow1.5-RC1.zip |
Will do. I'll edit this comment with my results. Thanks! UPDATE
Using the testing page I used before, there seem to be some antialiasing not working properly: compared to version 1.422 which looks better regarding aliasing (sorry if this is not the right term): |
It appears that the bold version 'e' characters are being rendered incorrectly only on windows. Self hosted woff2. Tried updating to newest version and that didn't resolve it


The text was updated successfully, but these errors were encountered: