Just to let you know, Google introduced a new API yesterday, making it extremely easy to add none web fonts to your website.
Easier than @font-face and Cufon. Renders beautifully in all browsers. The one downside I found is the limited number of available fonts, but that’ll grow over time.
but… fonts don’t show on ipad, iphone, and firefox 2 so far
David
On 20 May 2010, at 18:19, RobP wrote:
Hi,
Just to let you know, Google introduced a new API yesterday, making it extremely easy to add none web fonts to your website.
Easier than @font-face and Cufon. Renders beautifully in all browsers. The one downside I found is the limited number of available fonts, but that’ll grow over time.
Firefox 2, I’m not surprised. The iPad requires the fonts to be in SVG format to display them. I doubt Google are going the extra mile for that at the moment.
Some of the font packs from www.fontsquirrel.com come in SVG format, and they also supply a tool to help you convert any fonts you are allowed to legally into various formats. My Caxton Action can bring those into Freeway. This has the added bonus of your site hosting the files. You never know how or when they may vanish otherwise.
This move for using embedded fonts is, for me at least, genuinely exciting. I am hoping that embedded fonts will do more for web design than the gradient tool in Photoshop has.
how can these be incorporated into the design process ?
these can’t be downloaded, right ?
you are specifying fonts that reside on a google server … correct ?
which is good because they will be universally available
but how do you work with them in freeway ?
You would make a style (CSS) that references them, and apply that
style to some HTML text on your page. You wouldn’t be able to see the
exact font in the design view in Freeway (unless you picked something
really similar from your own PostScript or OpenType font collection)
but you would see the live font when you previewed in Freeway or a
browser.
Walter
On May 28, 2010, at 9:15 PM, Ian wrote:
under the category of “no question is stupid”
how can these be incorporated into the design process ?
these can’t be downloaded, right ?
you are specifying fonts that reside on a google server …
correct ?
which is good because they will be universally available
but how do you work with them in freeway ?
thanks walter
not an ideal way to work with them
as you say getting a good analogue by shape is the trick
the tradeoff i guess is that you can use some unusual fonts and be certain that everyone has access to them
if anyone has specced out a similar font to any of these especially droid (which will now be everywhere !) it would be nice to know
but of course there is no need to use font stacks because everyone will have these
Everyone with a modern desktop browser. We’ve already determined that
iPhone and (ironically) Android will not see them. So a font stack
would be critical. I thought quite a few of these looked mighty close
to normal Web fonts in their rough outline anyway – there’s one
that’s close enough to Georgia for me to ask “why bother?”.
Walter
On May 29, 2010, at 11:14 AM, Ian wrote:
but of course there is no need to use font stacks because everyone
will have these