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

Lato medium/500 weight not served. #1415

Open
estaub opened this issue Jan 15, 2018 · 29 comments
Open

Lato medium/500 weight not served. #1415

estaub opened this issue Jan 15, 2018 · 29 comments
Labels
-- Bad rendering Hinting issue mostly, or else -- Needs Upstream Resolution Upstream fix required before moving forward I Font Bug

Comments

@estaub
Copy link

estaub commented Jan 15, 2018

The Lato medium/500 weight is present here on GitHub (https://github.com/google/fonts/blob/master/ofl/lato/Lato-Medium.ttf), but is not documented at https://fonts.google.com/specimen/Lato, and appears to not be served by the api: the request

<link href="https://fonts.googleapis.com/css?family=Lato:300,400,500,700" rel="stylesheet">
provides 400 and 500 weights that are identical; I believe they are both 400/regular.

I've no idea whether this is by design, an enhancement request, or a bug.

@davelab6
Copy link
Member

Hmm, at https://jsbin.com/bedasam/edit?html,output I see that the 500 is actually LIGHTER than the REGULAR:

screen shot 2018-01-24 at 18 22 08

screenshot_20180124-182319

@twardoch is the public face of the Lato project... any tips, adam? :)

@davelab6 davelab6 added this to the Bugs in Font Files 00 Resolution Effort Undetermined milestone Jan 24, 2018
@estaub
Copy link
Author

estaub commented Jan 25, 2018

@davelab6 They look identical to me, fwiw. You might want to verify somehow. Maybe the "5" being larger and less dense than the "4" is fooling your eye?

@estaub
Copy link
Author

estaub commented Jan 25, 2018

I've verified that the font files in this project appear to be correct. The problem is downstream somewhere, but fonts.google.com refers me here for any issues, so I don't know a better place to report it.
screen shot 2018-01-25 at 12 50 26 pm

While I don't know how to confirm it, I expect that medium/500 is not being served at all, and the browser simply falls back to regular/400 when medium/500 is requested.

@davelab6
Copy link
Member

So, the reason is that the 500 weight hasn't been plumbed into the API yet; the files in the HEAD of this repo haven't been pushed to the API, and so there is no 500 weight being served.

It is odd that the Android rendering isn't 1:1, and GF engineering @garretrieger said offline,

That's odd, but I don't think it's related to what we're serving for Lato. Possibly android is doing something weird for weight synthesis?

So, right now we are waiting for @twardoch to sort out the hinting in Lato so we can update the version here and push it all the way through to the API.

@davelab6 davelab6 modified the milestones: Bugs in Font Files 00 Resolution Effort Undetermined, Bugs in Font Files 01 Requires Upstream Resolution Jan 29, 2018
@davelab6 davelab6 added the -- Bad rendering Hinting issue mostly, or else label Jan 29, 2018
@ziyafenn
Copy link

Still not fixed?

@estaub
Copy link
Author

estaub commented Feb 11, 2019

Is this going to be left wrong to avoid breaking apps using 500 with tight spacing? :-(

@ghost
Copy link

ghost commented Feb 12, 2019

any news

@laerm0 laerm0 added the -- Needs Upstream Resolution Upstream fix required before moving forward label Feb 12, 2019
@controversial
Copy link

Google serves only Thin 100, Light 300, Regular 400, Bold 700, and Black 900. Adobe Fonts adds an even lighter Hairline 100 (moving Thin to 200), Medium 500, Semibold 600, and Heavy 800, almost doubling the number of available font weights for Lato. It'd be great if all of the additional weights could be added to Google Fonts as I much prefer the experience Google offers.

@arktds
Copy link

arktds commented Mar 13, 2020

I can't wait😪

@controversial
Copy link

@m4rc1e @davelab6 is there any path forward to resolving this?

@jonasgoddeeris
Copy link

+1

1 similar comment
@liamthorpeyoung
Copy link

+1

@IslombekHasan
Copy link

Ohh, pleaaase! Is it so hard?

@m4rc1e
Copy link
Collaborator

m4rc1e commented Oct 9, 2020

@IslombekMe yes. We attempted to update the family before we had a regression tests and we broke the internet. #644

@IslombekHasan
Copy link

Wow. This is exactly the moment when i can finally say - With great power, comes great responsibility!

@GautierT
Copy link

@m4rc1e any update on this issue ? Thanks.

@mwawrusch
Copy link

3 years???

@piotros
Copy link

piotros commented Apr 7, 2021

Is there any alternative CDN for this font without this bug?

@RosaWagner RosaWagner removed this from the Bugs in Font Files 01 Requires Upstream Resolution milestone Aug 13, 2021
@Noitidart
Copy link

Is there any alternative CDN for this font without this bug?

Same, looking for Lato Alt, is there one available?

@ineshbose
Copy link

Ah yes we all unite

@MatkoMilic
Copy link

MatkoMilic commented Feb 3, 2023

This is causing me issues as well in my React Native project. However after some debugging I realised that Lato Medium can be downloaded elsewhere online and it represents the 500 variant.

@Ajnus
Copy link

Ajnus commented Mar 14, 2023

This is causing me issues as well in my React Native project. However after some debugging I realised that Lato Medium can be downloaded elsewhere online and it represents the 500 variant.

"elsewhere":
https://github.com/google/fonts/blob/main/ofl/lato/Lato-Medium.ttf

@vivek-hs
Copy link

This is causing me issues as well in my React Native project. However after some debugging I realised that Lato Medium can be downloaded elsewhere online and it represents the 500 variant.

https://www.latofonts.com/

@noranda
Copy link

noranda commented Oct 18, 2023

+1 Are we to assume this will never be fixed?

@piotros
Copy link

piotros commented Oct 18, 2023

We assume this won't be fixed. Fixing this problem would change the appearance of thousands of pages.

@DamianGlowala
Copy link

There are ways to address this problem without replacing an existing font set (which is indeed a breaking change).

Lato 2 could be added instead with a complete set of weights.

@noranda
Copy link

noranda commented Oct 18, 2023

There are ways to address this problem without replacing an existing font set (which is indeed a breaking change).

Lato 2 could be added instead with a complete set of weights.

I actually assumed this was the fix and looked for a supplemental Lato font, but no luck. I ended up just using Adobe Fonts instead but be warned the two Lato's differ very slightly (mostly pixel spacing).

@MatkoMilic
Copy link

This is causing me issues as well in my React Native project. However after some debugging I realised that Lato Medium can be downloaded elsewhere online and it represents the 500 variant.

"elsewhere": https://github.com/google/fonts/blob/main/ofl/lato/Lato-Medium.ttf

Yes elsewhere. I presumed programmers can Google :)

@Ajnus
Copy link

Ajnus commented Nov 14, 2023

This is causing me issues as well in my React Native project. However after some debugging I realised that Lato Medium can be downloaded elsewhere online and it represents the 500 variant.

"elsewhere": https://github.com/google/fonts/blob/main/ofl/lato/Lato-Medium.ttf

Yes elsewhere. I presumed programmers can Google :)

What's that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-- Bad rendering Hinting issue mostly, or else -- Needs Upstream Resolution Upstream fix required before moving forward I Font Bug
Projects
None yet
Development

No branches or pull requests