Comments on: A Guide to Google Font API

By: PeterU

PeterU — Mon, 28 Nov 2011 16:03:37 +0000

Hello.

I’ve been playing with web fontst for a while and love the prospect of that choice!

However, if I try and print a page that references Google fonts, the printer uses ITS default instead.

Clearly the printer can only use what fonts it has installed.

But surely in our modern days, there is a way of “pushing through” the web font through to the printer?

If yes, how do we achieve? I’m a bit lost.

Thanks,

Peter

By: Pablinho

Pablinho — Sun, 20 Nov 2011 20:51:41 +0000

Great selection of fonts they have… and it keeps growing.

Only problem for me is how the different the font looks from browser to browser. For example, most fonts look awful on Safari..

By: Francis Boudreau

Francis Boudreau — Mon, 10 Oct 2011 17:39:04 +0000

Thanks a lot for this article!
I didn’t know about the Google Web Font API, but now I wish I knew it sooner…!

By: Durgesh

Durgesh — Thu, 18 Aug 2011 08:35:54 +0000

great tutorial. Thanks.

By: figman

figman — Sun, 07 Aug 2011 16:07:57 +0000

@ugly
I believe it had nothing to do with the video card.It simply has to do with the way the OS renders the fonts within the browser.

Up to date Windows, even with ClearType enbled is the worst in regards to rendering Fonts and WebFonts alike.

This is very disappointing considering 50% of the population uses Windows

By: ugly

ugly — Mon, 18 Jul 2011 21:17:29 +0000

those google web fonts look pretty on my ubuntu, but pretty ugly with jagged edges on my windows. probably some video card thing.

By: Jazzvox

Jazzvox — Wed, 08 Jun 2011 18:09:02 +0000

I’m using Cabin on this site, other GoogleWebFonts on other sites for a while. There are still issues in Browsers, as they seem to interprete *px size and type=bold in different ways. In addition, I’m not shure if CSS ‘text-indent’ works out for this fonts … in all browsers.

The ‘bold’ issue is resolved by following your advice for the import-in-header link: ‘Cabin|Cabin:bold’
The ‘size’ issue seems to be happening for h1, h2 … IE oversizes them, no matter what I do :(

By: vale

vale — Fri, 27 May 2011 14:25:21 +0000

Hey it seems common ligatures aren’t included in the web-fonts offered for free by Google, on the other hand they also say that paying for them will enable “special features” of the typeface included ligatures. Does anybody tried this out?
PS to let webkit browsers render ligatures the CSS text-rendering: optimizeLegibility;
has to be set.

By: rob

rob — Fri, 01 Apr 2011 00:47:09 +0000

You guys probably don’t care, but it should be noted that this is also another way for google to have a hit-counter on your website, so it can track who your visitors are (by means of the referer that links to their css).

By: Don McArthur

Don McArthur — Sat, 12 Feb 2011 16:47:36 +0000

Have you tried printing a web page that only uses web fonts? Doesn’t work with up-to-date Chrome or Safari on Mac OS X, I’m not sure of other resources.

Am I missing something?