Chhavi221 / googlefontdirectory

Automatically exported from code.google.com/p/googlefontdirectory
0 stars 0 forks source link

Lato Broken in Chrome and IE #39

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Viewing Lato in Chrome or any version of IE will display a serif font that is 
not Lato. 

Lato should load cross-browser as most other google fonts do. Chrome and IE 
think that Lato is loading so even a font stack such as 'Lato', Trebuchet MS, 
Arial, sans-serif; does not work, you always get the serif font. This is the 
same behavior on the official google fonts Lato page so I know it is not a site 
specific problem.

Lato seems to load fine in FireFox and Safari.

Original issue reported on code.google.com by Steve.Mu...@gmail.com on 9 Feb 2011 at 1:45

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I'm having the same issue with the Lato font in IE. It's rendering in other 
browser fine, even Chrome. I've attached images of how it's rendering in IE vs 
Firefox

Original comment by j.kurczo...@gmail.com on 17 May 2011 at 11:01

Attachments:

GoogleCodeExporter commented 9 years ago
I am seeing the same results.  I have stopped using Google fonts for any 
production work.

Original comment by tom.subl...@gravitytank.com on 18 May 2011 at 12:42

GoogleCodeExporter commented 9 years ago
I used the workaround described in Issue 9 -- calling the different font 
variants separately in an IE-only style sheet -- and Lato is working fine for 
me in all major browsers now.

http://code.google.com/p/googlefontdirectory/issues/detail?id=9&can=1&q=italic

Original comment by jess...@sheerandesign.com on 18 May 2011 at 3:54

GoogleCodeExporter commented 9 years ago
Lato doesn’t even work on the Google Web Fonts site in Chrome. 

It actually crashes the page most of the time. Especially if you click "View 
all styles."

Would love to see this fixed. 

Original comment by allan.c...@gmail.com on 24 Aug 2011 at 8:51

Attachments:

GoogleCodeExporter commented 9 years ago
The behavior that I see is closer to what is described in comment #2. Lato 
appears as a sans-serif font in chrome and firefox, but the rendering is "off" 
in chrome. I've included sample text for reference.

Original comment by a.calh...@gmail.com on 13 Feb 2013 at 4:16

Attachments:

GoogleCodeExporter commented 9 years ago

/*******************************************************************************
*********************

BAD

    This is what the Google Webfont directory gives us. WOFF!  Looks bad on Chrome.
    No antialiasing.. :p  

****/

@font-face {
  font-family: 'Droid Sans';
  font-style: normal;
  font-weight: 400;
  src: local('Droid Sans'), local('DroidSans'), 
       url(http://themes.googleusercontent.com/bla/bla.woff) format('woff');
}

/*******************************************************************************
*********************

GOOD

    This is what it should be. 
    Problems are that the fonts are hosted on the server.. no cdn.. makes sad panda's.

    I downloaded the Fontsquirrel Droidsans webfont kit. Uploaded it to my server. And change the 
    CSS file so it looks exact like this: 

****/

@font-face {
   font-family: 'DroidSansRegular';
   src: url('DroidSans-webfont.eot');
   src: url('DroidSans-webfont.svg#DroidSansRegular') format('svg'), <------ MOVED SVG ON TOP
        url('DroidSans-webfont.eot?#iefix') format('embedded-opentype'),
        url('DroidSans-webfont.woff') format('woff'), <-- PLACED THE WOFF, WHERE THE SVG WAS
        url('DroidSans-webfont.ttf') format('truetype')
   font-weight: normal;
   font-style: normal;

}

@font-face {
   font-family: 'DroidSansBold';
   src: url('DroidSans-Bold-webfont.eot');
   src: url('DroidSans-Bold-webfont.svg#DroidSansBold') format('svg'),
        url('DroidSans-Bold-webfont.eot?#iefix') format('embedded-opentype'),
        url('DroidSans-Bold-webfont.woff') format('woff'),
        url('DroidSans-Bold-webfont.ttf') format('truetype');
   font-weight: normal;
   font-style: normal;
}

Original comment by xandersmalbil on 22 Jul 2013 at 7:00