-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Overnight my Lato looks quite different #644
Comments
I've got the same problem. But I currently don't have any solution for this. |
@dominiklaube self-hosting? |
@websevendev The change is not personal. Lato hadn't been upgraded in several years. We've upgraded it recently to the latest version, 2.015. Lato 2.015 uses a newer version of ttfauothint which had x-height pixel rounding applied. We didn't add this ourselves but the creator of the font. @davelab6 Since this issue keeps cropping up, we should by default match the previous version's settings. I'll look into how we can write a test for this. |
Same problem here. |
@lowwa132 I understand your frustrations. This is a fine balancing act between being backwards compatible with the previous version and allowing modifications. When preparing fonts, I try and stay as faithful as possible to the original source. I usually end up modifying just the name table. My process to convert Lato 2.0 so it's GF api friendly is here. I didn't modify any hinting settings. The x-height rounding was introduced in the original source. I've done some further tests between the version we have uploaded and the newest version available on the official site. The rendering is identical. The hinting difference was introduced in the original sources. left tab: fonts.google.com Lato 2.0 right tab: Latofonts.com 2.0 |
I also use the version hostet by google //fonts.googleapis.com/css?family=Lato:400,400italic,700italic,700 |
Same problem here, my website looks completely off now ... |
Another issue found in the update pushed yesterday:
|
I'm experiencing issues with Lato as well. Woke up to see our site's main navigation looking terrible. Seems like the font is stretching vertically when at small sizes (12px-16px) and at weight 700. Please roll back or provide a legacy version. I'd rather not swap our main font, but at least in our case it looks very awkward. |
We also had issues with this update (in fact, images were being pushed out of their proper containers as a result of the CSS changes). However, just as I was about to fix our UI issues from my end, I noticed that the change had been reverted. Thanks for the fix! |
Roll back has been completed |
I noticed the Lato on my site looks different than it used to.
I had some older tabs open overnight, so I compared.
Open in tabs and flick back and forth:
Before:
http://i.imgur.com/boAj26Q.png
After:
http://i.imgur.com/w6yCaVd.png
In dev tools, under Sources, a new source has appeared: fonts.gstatic.com
To me, the change has taken place on other pages using Lato too: http://semantic-ui.com/elements/header.html
So can anyone help me understand this?
Is the change personal to me only?
I have Lato installed on my Windows. Has my browser been using it for the past 6 months and then suddenly decided to request it from fonts.gstatic.com instead? Or is my local Lato never used when a website specifically imports a Google font?
I like the old version better, so how would I go about achieving the old look, if the font size and variant are exactly the same?
The text was updated successfully, but these errors were encountered: