Not Signed-In
Which clippings match 'Font-face' keyword pg.1 of 1
22 OCTOBER 2013

CSS Fonts Module Level 3: the @font-face rule

"The @font–face rule allows for linking to fonts that are automatically fetched and activated when needed. This allows authors to select a font that closely matches the design goals for a given page rather than limiting the font choice to a set of fonts available on a given platform. A set of font descriptors define the location of a font resource, either locally or externally, along with the style characteristics of an individual face. Multiple @font–face rules can be used to construct font families with a variety of faces. Using CSS font matching rules, a user agent can selectively download only those faces that are needed for a given piece of text."

(World Wide Web Consortium, 3 October 2013)

1
2

TAGS

2013CSS3 • Cufon • design for the screen • design goal • End User Licensing Agreement • EOT • EULA • font • font choice • font descriptor • font embedding • font family • font linking • font matching • font resource • font-face • font-face rule • fonts • inline SVG • Open Font License (OFL) • openfonts • Opentype • OTF • platform independent • selectively download • sIFR • style characteristics • SVG • TTF • typetypefaceTypekittypography • Typoteque • ubiquitous web fonts • user agent • W3Cweb design • web design typography • web technologies • web type • web typography • webfont • WOFF

CONTRIBUTOR

Simon Perkins
18 JUNE 2009

Ubiquitous web font embedding just got a step closer...

"A short while ago, Mozilla announced that Firefox 3.1 will, along with Safari which already does, support the @font–face mechanism for linking to online TrueType fonts. Internet Explorer already supports (and has done so for years) @font–face font linking, but here's the catch, not to TrueType fonts – only to EOT font files. EOT, now a proposed W3C specification, incorporates anti copying technology, helping to assuage the fears of font foundries that font linking in browsers would unleash a wave of unlicensed copying of their fonts. Chris Wilson, Platform Architect for Internet Explorer has made it clear that he's strongly opposed to simple font linking

we (Microsoft) should NOT support direct TTF/OTF embedding, unless 1) there is some check that the font intended that use to be allowed, which I don't think there currently is (as it needs to refer to the license agreement), AND 2) other browsers also implement a system that actually ENABLES commercial fonts – those that are allowed to be embedded, but cannot be legally placed directly on a server – to be used

So, is this a return to the stalemate of the 1990s, when both the major browsers supported font linking, only of a completely incompatible type? From a technical point of view, no. Since the same mechanism, @font–face rules, is used to link to TrueType, EOT and other font formats, then it is quite simple to define multiple fonts, and the browser can use the font format it supports."
(John Allsopp, 19 October 2008)

1

TAGS

copyrightEOTFirefoxfont embeddingfont-facefontsInternet ExplorerMicrosoftMozillaownershiptechnology • TrueType • TrueType fonts • typeubiquitousubiquitous web fontsweb

CONTRIBUTOR

Simon Perkins
Sign-In

Sign-In to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.