- From: Yuzo Fujishima <yuzo@google.com>
- Date: Wed, 13 Oct 2010 09:28:42 +0900
- To: John Daggett <jdaggett@mozilla.com>
- Cc: www-style@w3.org, Beth Dakin <bdakin@apple.com>
- Message-ID: <AANLkTinx7MxcdFca56NZSBZNGE7c-YGuyetjAz8m9UMs@mail.gmail.com>
Hi, John, Thank you for the reply. Do you mean [OtherFont], rather than [LocalFont], should be used to draw text temporarily while [URL] is loading? (If you meant otherwise, what font should we use for the temporary drawing?) Yuzo On Tue, Oct 12, 2010 at 11:41 PM, John Daggett <jdaggett@mozilla.com> wrote: > Hi Yuzo, > > 15 Example: > > 16 <style> > > 17 @font-face { > > 18 font-family: samplefont; > > 19 src: url([URL]), local([LocalFont]); > > 20 } > > 21 </style> > > 22 <span style="font-family: samplefont, [OtherFont]">Hello</span> > > 23 > > 24 If [LocalFont] is a valid local font, it is used as the fallback. > > 25 Otherwise, [OtherFont] is used. > I don't think this is such a good idea, it confuses load fallback with > character fallback. The src list describes load fallback, the order in > which font loading is attempted until a load succeeds. The font-family > list defines character fallback order, the order in which fonts are > searched for a given character. > Your example could just as easily be written as: > <span style="font-family: samplefont, [LocalFont], > [OtherFont]">Hello</span> > The intent of local() is to allow the downloading of a given font to be > skipped if a local equivalent is available. That's not possible with > just a font family list because of the way character fallback happens. > > (BTW http://dev.w3.org/csswg/css3-fonts/ is the latest draft.) > Thanks for mentioning that! > Cheers, > John
Received on Wednesday, 13 October 2010 00:29:44 UTC