- From: Yuzo Fujishima <yuzo@google.com>
- Date: Thu, 19 May 2011 12:49:35 +0900
- To: David Singer <singer@apple.com>
- Cc: John Daggett <jdaggett@mozilla.com>, www-style list <www-style@w3.org>
Received on Thursday, 19 May 2011 03:50:29 UTC
FYI. The latest Editor's Draft 28 April 2011 has a section for this. http://dev.w3.org/csswg/css3-fonts/#font-face-loading Yuzo On Wed, Jan 19, 2011 at 1:25 AM, David Singer <singer@apple.com> wrote: > On Jan 17, 2011, at 18:52 , John Daggett wrote: > > David Singer wrote: > > > >> what I meant by 'as similar as possible' was not precise matching, but > >> roughly 'gee if your custom font is monospace, at least choose a > >> monospace font with about the same advance/font-size ratio as the > >> fallback, and if your custom is condensed, try to find a condensed face > >> as the fallback, and so on, so that text lays out roughly in the > overall > >> same-ish amount of space'. Obviously matching all the metrics, > >> line-breaks, word positioning etc. would mean, as you say, you've > almost > >> got the same font, so why bother with the custom one? > > > > As long as that's authoring advice and not user-agent behavior you're > > talking about, I think it would be fine to include a discussion in the > > spec. > > > yes, exactly, it's authoring advice. many authors have the font locally > or > can download it fast; they may never see the temporary fallback behavior, > so > I think it worthwhile pointing it out to them that they should give it a > moment's thought. > David Singer > Multimedia and Software Standards, Apple Inc.
Received on Thursday, 19 May 2011 03:50:29 UTC