- From: Chris Lilley <chris@w3.org>
- Date: Sat, 4 Oct 2014 05:45:38 +0200
- To: David Kuettel <kuettel@google.com>
- CC: Jonathan Kew <jfkthame@gmail.com>, "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotype.com>, WebFonts WG <public-webfonts-wg@w3.org>
Hello David, Friday, October 3, 2014, 7:38:28 PM, you wrote: > With advanced features (such as unicode-range) it becomes even > harder (to impossible) to write one CSS snippet that works properly > across all browsers/versions without significantly regressing the > end-user experience. For example, there are browsers that simply > download *all* of the referenced fonts, rather than the minimum > required set. Given that a font with full pan-unicode language > coverage can easily top 20MB+ (and given that rich pages typically > use multiple-styles weights), one could quickly break the web. We > are far from the goal of supporting all languages for each font, but > definitely would like to get there in time. Well put. The relevant Firefox bug is https://bugzilla.mozilla.org/show_bug.cgi?id=475891 and the lack of unicode-range support does, as you say, potentially break the Web. However, it looks as if this is close to being fixed. -- Best regards, Chris Lilley, Technical Director, W3C Interaction Domain
Received on Saturday, 4 October 2014 03:45:43 UTC