Skip to content
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

Open
davidfurlong opened this issue Sep 4, 2019 · 21 comments
Open

Windows rendering issue: bold 'e' characters #55

davidfurlong opened this issue Sep 4, 2019 · 21 comments
Labels

Comments

@davidfurlong
Copy link

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
image (4)
image (3)

@jpt
Copy link
Owner

jpt commented Sep 4, 2019

Hi @davidfurlong - thanks for opening the issue, I'll look into it. In which browser and version of Windows is this happening?

@davidfurlong
Copy link
Author

davidfurlong commented Sep 5, 2019

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

@jpt
Copy link
Owner

jpt commented Sep 6, 2019

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

@davidfurlong
Copy link
Author

Thanks for looking into it

@jpt
Copy link
Owner

jpt commented Sep 6, 2019

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.

@jpt jpt added the bug label Sep 6, 2019
@davidfurlong
Copy link
Author

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

@jpt
Copy link
Owner

jpt commented Sep 9, 2019

@davidfurlong -- no worries at all, I appreciate bug report! I'll spin up a VM to give it a proper evaluation.

@briandipert
Copy link

I'm having similar issues but it is also effecting the capital "E". This is occurring in IE11, Firefox and Chrome on Windows. I tried your new WOFF2 binaries and the issue is still occurring.

image

@jpt
Copy link
Owner

jpt commented Oct 1, 2019

Thanks @briandipert -- can you give these a try? Also, can you let me know if WOFF (not WOFF2) files have the same problem?

Barlow-New-WOFF2.zip

@briandipert
Copy link

These WOFF2 files fixed the issues for me!

On the WOFF files, the Barlow Regular font does not appear to have the issue but the Barlow Condensed Regular font does it (see image below)
image

@jpt
Copy link
Owner

jpt commented Oct 3, 2019

@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!

@Sopamo
Copy link

Sopamo commented Oct 15, 2019

We have the same issue with the WOFF and WOFF2 files and can replicate it on OSX and Linux (in Chrome):

image

For us this also only happens with the bold style.

@naeon
Copy link

naeon commented Oct 28, 2019

@jpt Could you give an estimate on when this issue might be fixed? Thank you!

@briandipert
Copy link

@jpt do you have a TTF file of the latest version of Barlow?

@jpt
Copy link
Owner

jpt commented Oct 19, 2021

Hinting has been updated in the source, I will generate new TTF binaries soon: https://github.com/jpt/barlow/tree/1.5

@jpt
Copy link
Owner

jpt commented Oct 21, 2021

new TTF files can be found here: https://github.com/jpt/barlow/tree/1.5/fonts/ttf
I will merge them into the main branch once I've finished testing

@agusmba
Copy link

agusmba commented Oct 29, 2021

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.
Windows preview seems to show the new TTF files ok also.

Another testing page: http://webfont-test.com/ is also not working on the new TTFs.

@jpt
Copy link
Owner

jpt commented Nov 27, 2021

Looking into the TTFs, thanks for letting me know

@jpt jpt mentioned this issue Dec 4, 2021
@jpt
Copy link
Owner

jpt commented Dec 5, 2021

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

@agusmba
Copy link

agusmba commented Dec 9, 2021

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
The new TTF files load correctly. 👍
However doing a quick comparison with version 1.422, I see some strange artifacts:

image
Notice the uneven characters at size 18 compared with v1.422

Using the testing page I used before, there seem to be some antialiasing not working properly:
image

compared to version 1.422 which looks better regarding aliasing (sorry if this is not the right term):
image

@agusmba
Copy link

agusmba commented Dec 9, 2021

The OTF is a bit better than the TTF, but still has some quirks:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants