Open GoogleCodeExporter opened 9 years ago
Have you got the fonts installed locally? If so, please uninstall them and try
again. Lato was updated in the last 24 hours, and I can't reproduce this.
Original comment by dcrossland@google.com
on 21 Aug 2014 at 6:38
Lato is not installed locally (at least I do not see it at Control Panel\All
Control Panel Items\Fonts). I have cleared the cache to verify it is
downloading it fresh and still same result on that page. Seeing this on many
different PCs.
Original comment by pthor...@gmail.com
on 21 Aug 2014 at 6:52
I can reproduce this on Firefox and IE. Example here:
http://jsfiddle.net/cbenard/p4oao7tr/
And on my real site: http://chrisbenard.net/contact/
Original comment by cben...@gmail.com
on 21 Aug 2014 at 7:49
I can verify that within the last few hours Lato has been screwed up. Many of
our Windows customers are suddenly complaining that our font is very hard to
read.
Original comment by philfreo
on 21 Aug 2014 at 8:02
[deleted comment]
Also seeing this in IE and FireFox, however Chrome seems to be fine. Font just
appears to be missing characters. Switching to a fallback font fixes the
problem.
Original comment by rated...@gmail.com
on 21 Aug 2014 at 8:14
Seeing the same thing here with Firefox; Chrome and IE seem to be OK.
If I disable hardware acceleration in FF the letters appear. On another system
I am not having the issue with any browser.
Original comment by bguth...@billyguthrie.com
on 21 Aug 2014 at 8:37
Here's an example of the "t" being unreadable on Windows Chrome on this
Typecast page:
http://typecast.com/preview/google/Lato
which is linked from:
https://www.google.com/fonts/specimen/Lato
Original comment by philfreo
on 21 Aug 2014 at 8:44
Attachments:
Adam Twardoch, font developer, says, "In Lato 1, I used FontLab Studio to
autohint the two thinnest weights and ttfautohint for the rest. In Lato 2, I
used ttfautohint for all. This seems to not have been a good idea. I'll see
what I can do about it very soon."
Meanwhile, the Google Fonts API will rollback the update today.
Original comment by dcrossland@google.com
on 21 Aug 2014 at 8:46
Issue 332 has been merged into this issue.
Original comment by dcrossland@google.com
on 21 Aug 2014 at 9:12
The rollback should now be complete.
Original comment by dcrossland@google.com
on 21 Aug 2014 at 9:52
[deleted comment]
If this is of any help in troubleshooting, this seems to only occur with
Windows' DirectWrite renderer. If the GDI renderer is forced, it works fine--
but the hinting looks kind of awful, because it seems to be somehow optimized
for DirectWrite.
Original comment by codeman38
on 22 Aug 2014 at 4:21
[deleted comment]
Still major problems with IE9. Individual letters are missing when I use Lato
from our own server with @font-face. Any solution guys?
Original comment by freshfru...@gmail.com
on 26 Aug 2014 at 9:29
freshfruitmail, what version of Lato are you using?
Original comment by dcrossland@google.com
on 26 Aug 2014 at 4:59
Working fine for me following the rollback.
Original comment by pthor...@gmail.com
on 26 Aug 2014 at 7:28
PM, I have the latest one downloaded from latofonts.com (Lato 2.0). Can I get a
newer version with fix from somewhere? Or rollbacked one?
Original comment by freshfru...@gmail.com
on 3 Sep 2014 at 6:31
You can download the version served by Google here
http://www.google.com/fonts/download?kit=NdjKCQMCiQM2g3qf94rrwQ
Original comment by dcrossland@google.com
on 3 Sep 2014 at 10:37
Thanks. Any chance to download .woff and .eot versions too?
Original comment by freshfru...@gmail.com
on 3 Sep 2014 at 12:18
Original issue reported on code.google.com by
pthor...@gmail.com
on 21 Aug 2014 at 6:21Attachments: