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

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

From: Michael Day <mikeday@yeslogic.com>
Date: Thu, 22 Jan 2009 09:51:24 +1100
Message-ID: <4977A6EC.2060701@yeslogic.com>
To: John Daggett <jdaggett@mozilla.com>
CC: www-style <www-style@w3.org>

Hi John,

> 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?

> 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.

Best regards,

Michael

-- 
Print XML with Prince!
http://www.princexml.com
Received on Wednesday, 21 January 2009 22:52:17 GMT

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