W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-fonts] new editor's draft

From: John Daggett <jdaggett@mozilla.com>
Date: Wed, 21 Jan 2009 21:32:13 -0800 (PST)
To: Michael Day <mikeday@yeslogic.com>
Cc: www-style <www-style@w3.org>
Message-ID: <13335344.6287251232602333639.JavaMail.root@cm-mail01.mozilla.org>

Hi Michael,

> > This seems simple, but to really make this work you're going to need
> > four rules to cover each of the four common style variations -
> > normal, bold, italic and bold italic, since a single @font-face rule
> > only defines a single *face* within a family.
> 
> The default value for font-weight and font-style is "all", or at least
> it was, has this been changed?

Even if defined with font-weight and font-style defaulting to "all",
that means you're going to ignore bold and italic faces and use the
normal face in all situations. That's not really a good way of defining
what 'serif' means.

> > If you defined the src descriptor the way you propose, user agents
> > that implement SVG fonts would *always* need to download the
> > TrueType font, even if you separated these out into three separate
> > @font-face rules and used MyFutura1, MyFutura2, MyFutura3 in all
> > your font-family lists.
> 
> Only in the case that the SVG font did not include a glyph that was
> needed by the page, in which case it makes sense to download the
> TrueType font. If the earlier fonts in the list provide all the
> necessary glyphs, later fonts will never be loaded.
> 
> > With src defined to iterate over the list during font fallback, the
> > OpenType version of Scheherazade would always be downloaded, even
> > though it wouldn't be needed on the Mac.
> 
> Again, I don't see why it would be loaded if the AAT version provides
> the necessary glyphs, which it presumably would if the site author has
> chosen it specifically for that purpose.

Using your original font-family list, let's say you wanted to override
the Arabic glyphs used in Times New Roman with Scheherazade instead.

@font-face {
  font-family: Scheherazade;
  src: url(ScheherazadeRegAAT.ttf) format("truetype-aat"), url(ScheherazadeRegOT.ttf) format("opentype");
}

body: { font-family: Scheherazade, Times New Roman, OpenSymbol, ...; }

In this situation, if the src descriptor is defined to load *all* fonts
rather than the first valid font, then you would always load the
OpenType version before rendering Latin text, even though it wouldn't be
needed on the Mac. By not distinguishing load behavior from font
fallback behavior, you're taking control away from the author.

Cheers,

John Daggett
Mozilla Japan
Received on Thursday, 22 January 2009 05:32:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:15 GMT