Currently 97% of iOS users are on version 7 or 8, so I can see why Google Fonts omit it.
SVG is the only format supported in iOS pre 4.2, after which TTF then WOFF kicks in. Outside of Google Fonts you may also encounter SVG, I’ve seen it used in webfont stacks to catch legacy iOS. Though it is something to monitor, as WOFF2 file sizes are ~30% smaller than WOFF. WOFF2 support is currently limited to Chrome 36+ and Opera 23+, so its usefulness in email is negligible right now. EOT is IE only which is why it renders in older Outlook, not essential but it doesn’t hurt. WOFF has wide support in modern browsers, with TTF filling in some gaps on mid-range Android. All in head includes EOT, TTF, WOFF & WOFF2 If you open up the or url, you’ll see the code that corresponds to your browser.Īll in head 1. Placing the code directly into the head takes more work, we opened up the Orbitron link in various browsers to collect each URL. All three of these methods ultimately rely on support. If using the later two, Google Fonts automatically serves the right font format to the right browser. Using the Google font Orbitron, we tested each format with directly in the head, via and.
Google webfont in email full#
So we ran some tests in the device lab - view full QA - using the four formats Google Fonts currently serves: EOT, TTF, WOFF2 and support by format & method Although I knew WOFF was the emerging standard with a W3C Recommendation, I hadn’t looked closely at email client support for each format. As each format has varying browser support, they asked if this would give us enough coverage in email. I believe it was WOFF, EOT and SVG, but not TTF or OTF as they are considered desktop formats. While trying to find out which webfont services are compatible with email, one type foundry mentioned that their license only covers certain font formats.
0 kommentar(er)
