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

Add Lato v2.0 #6

Closed
eternal-sorrow opened this issue Apr 9, 2015 · 81 comments · Fixed by #479
Closed

Add Lato v2.0 #6

eternal-sorrow opened this issue Apr 9, 2015 · 81 comments · Fixed by #479
Assignees
Labels
-- Needs Upstream Resolution Upstream fix required before moving forward

Comments

@eternal-sorrow
Copy link

eternal-sorrow commented Apr 9, 2015

Since version 2.0 Lato has started providing cyrillic symbols along with ones of some other languages. So, please add a new version of this nice font.

(Note accents not working per http://jsbin.com/momova/edit?html,css,output)

@rsheeter
Copy link
Collaborator

rsheeter commented Apr 9, 2015

Ty for the heads up, will investigate.

For my own reference, http://www.latofonts.com/2014/02/27/lato-2-0-released/.

@davelab6 davelab6 self-assigned this Apr 13, 2015
@codeman38
Copy link

Lato 2.0 was tested a while back but rejected due to bad hinting that caused glitchy rendering on Windows. However, the hinting bug has since been fixed upstream: http://www.latofonts.com/2014/09/03/lato-family-updated-version-2-010/

@davelab6
Copy link
Member

@twardoch has promised to publish the sources on Github eventually :)

@twardoch
Copy link
Collaborator

Yes, I will. But they're in a VERY chaotic state right now due to the complexity of the project. Mixture of FontLab Studio 5, manual stuff, hardcoded Python snd some unpublishable 3rd party tools. I'm the only person who can build them right now but I definitely plan to upgrade them to a more portable form this summer.

@nqst
Copy link

nqst commented Nov 17, 2015

Is there any news on this issue?

@akhatskevich
Copy link

Need cyrillic symbols of Lato so much! So, is there any progress?

@simonsarris
Copy link

Happy issue anniversary, any word on getting Lato 2 support?

@ogheo
Copy link

ogheo commented May 24, 2016

up

@davelab6 davelab6 self-assigned this Jun 8, 2016
@davelab6
Copy link
Member

davelab6 commented Jun 8, 2016

Soon!

@davelab6 davelab6 modified the milestone: Update Families Jul 16, 2016
@omerziv omerziv added the z_Lato label Jul 27, 2016
@vladshcherbin
Copy link

vladshcherbin commented Sep 9, 2016

The 2.0 version was released in February, 2014 and was asked to update to it. It was 2.5 years ago. There are not so many good cyrillic fonts and Lato is a nice one to have.

What's the status of this, why can't this be done for such a long time?

@MartinZubek
Copy link

Hey guys, anything new on this?

@random-stranger
Copy link

What's happening with this one, why it is so hard to do? Early 2016, soon in June 2016. It's almost December, the end of the year.

Do people in Google use another understanding of time? Lato 2.0 was released in February, 2014, almost 3 years ago. It's 1000 days ago. Is it so hard to finally dedicate a day or two and update the font?

@davelab6 Can you finally keep your promise and update this font at least in 2016?

cc @m4rc1e, @alexeiva can someone help him as this promises can take forever. ?

@fitojb
Copy link
Contributor

fitojb commented Nov 16, 2016

@random-stranger Do any of them owe you anything at all, so that you're entitled to make such exigences? What is stopping you from simply self-hosting the font if you need it so desperately?

@davelab6
Copy link
Member

@fitojb to be fair, some places require Google Fonts API to be used for their own reasons.

@random-stranger when I pushed this the hinting had a problem, so I need to verify the hinting from this vendor is good in the latest release, and I didn't do this. However, @m4rc1e may be able to check this for us.

I can't commit to a specific date.

@m4rc1e
Copy link
Collaborator

m4rc1e commented Nov 21, 2016

I'll look into this today, if they pass our QA, I'll send a pr. However, it will take more time to get them served from the api.

As @fitojb says, self hosting is not a bad option for the time being.

Cheers,
Marc

@twardoch
Copy link
Collaborator

I haven't heard any reports of Lato 2.015 failing on screen rendering, but I did hear of printing problems, even with the most current version, which most likely are related to hinting and ttfautohint — but it's next to impossible to debug those problems.

@mrtungdev
Copy link

Wow, soo long

@RichardMisencik
Copy link

4 years and font is still not updated?
Nice job Google

@m4rc1e
Copy link
Collaborator

m4rc1e commented Apr 17, 2018

Search in the issues bar and read the other threads. You'll discover we rolled out v2.0 and it caused too many regressions so we rolled back, #644 (comment)

@RichardMisencik
Copy link

@m4rc1e What about version 2.015?

@m4rc1e
Copy link
Collaborator

m4rc1e commented Apr 17, 2018

@RichardMisencik that's what we attempted to pr, https://github.com/google/fonts/pull/479/files

@RichardMisencik
Copy link

@m4rc1e I see, so is there no way Lato v2 will be available on G Fonts?

@m4rc1e
Copy link
Collaborator

m4rc1e commented Apr 17, 2018

Read this thread

@rinart73
Copy link

rinart73 commented Jun 7, 2018

How could Lato v2 cause any issues if standalone version from official site works perfectly?

@m4rc1e
Copy link
Collaborator

m4rc1e commented Jun 7, 2018

@rinart73 #644 and just read the threads

@emilio-martinez
Copy link

@m4rc1e thanks for mentioning those threads! From my understanding then this is strictly related to a shift from Lato's design, correct? The x- height amongst other details are largely different, so you've opted to remain on v1 to avoid visual regressions?

@m4rc1e
Copy link
Collaborator

m4rc1e commented Jul 16, 2018

@emilio-martinez almost :-)

There's two issues.

  • V2 hinting changed because ttfautohint was updated and it now produces a different result.
  • The original designers/engineers are probably busy with other work and personal issues.

@Cooluck
Copy link

Cooluck commented Mar 15, 2020

Any news on Lato update on Google Fonts?

@KiwiBird97
Copy link

This is affecting Canvas LMS on platforms other than macOS. Lato is one of my favorite fonts!

@augustu5
Copy link

in the meantime, is a polyfill possible?
https://github.com/latofonts/lato-source/issues/6

@davelab6
Copy link
Member

https://github.com/latofonts/lato-source/#version-3100dev2-2020-08-16

V3.x is nearly ready

@m4rc1e please add to your queue after Roboto and Open Sans

@roychowdhuryrohit-dev
Copy link

roychowdhuryrohit-dev commented Feb 6, 2021

@davelab6 Which Google font supports the character U+20BF (₿)? Any idea?

@RosaWagner RosaWagner removed this from the Family Updates milestone Aug 13, 2021
@RosaWagner RosaWagner linked a pull request Oct 28, 2021 that will close this issue
@Maia-Everett
Copy link

The Lato font seen on Google Fonts is still missing Cyrillic. Was v2 really added?

nathan-williams pushed a commit that referenced this issue Apr 16, 2022
  - Simplify API by removing the `lang_support` module. Now one does `from gflanguages import LoadLanguages` instead of `from gflanguages.lang_support import LoadLanguages` (issue #6)
  - Also, all `Load_*` methods now accept base_dir as optional argument. (motivated by: googlefonts/gftools#511 (comment))
  - This will be the v0.3.0 API.
@adrianvintu
Copy link

Soon will be 10 years. No update?

@brendon
Copy link

brendon commented Aug 14, 2022

This issue makes for some interesting reading. I was wondering if it was just my imagination, but didn't the Lato font on Google Fonts used to support macrons: āēīōū (specifically used in Māori). I'm sure I remember choosing this font in our web app because of that support, and then earlier this year I noticed that those characters were falling back to the system font. Is my memory faulty?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-- Needs Upstream Resolution Upstream fix required before moving forward
Projects
None yet
Development

Successfully merging a pull request may close this issue.