- From: Jon Hanna <jon@hackcraft.net>
- Date: Wed, 03 Sep 2014 15:07:26 +0100
- To: www-style@w3.org
Apologies if this has already been covered and I missed it in the archives. Some current user-agents fail to either support unicode-range or to invalidate the @font-face rule due to their failure to support it. While this is neither adhering to the current spec, nor any previous, perhaps Example 14 should consider this: /* fallback font - size: 4.5MB */ @font-face { font-family: DroidSans; src: url(DroidSansFallback.woff); /* no range specified, defaults to entire range */ } /* Japanese glyphs - size: 1.2MB */ @font-face { font-family: DroidSans; src: url(DroidSansJapanese.woff); unicode-range: U+3000-9FFF, U+ff??; } /* Latin, Greek, Cyrillic along with some punctuation and symbols - size: 190KB */ @font-face { font-family: DroidSans; src: url(DroidSans.woff); unicode-range: U+000-5FF, U+1e00-1fff, U+2000-2300; } /* fallback font again, selected for a single non-character to be ignored by all unicode-range supporting browsers, used by some user-agents that fail to invalidate the rule. */ @font-face { font-family: DroidSans; src: url(DroidSansFallback.woff); unicode-range: U+FFFF; }
Received on Wednesday, 3 September 2014 14:07:52 UTC