4 ms·
If the license supports website usage, I can't see that it would matter which mechanism you used to deliver the font to the browser.
by steveax 13y ago
If the license supports website usage, I can't see that it would matter which mechanism you used to deliver the font to the browser.
- kibibu 13y agoI can easily imagine that some fonts may be licensed for distribution through one provider only, and may not be redistributed under any other means. Typekit terms of use explicitly prohibit using this method (emphasis mine): --- (a) You may Use the Licensed Content to design and develop Your Published Websites or webpages (and must Use any Kit We require for such purposes) and You may reference or encode a link to selected Licensed Fonts within Your Published Website design so that when others view or interact with Your Published Websites, they will see Your content displayed with the Licensed Fonts as You intended; and (b) You may only Use Licensed Fonts within Your Published Websites as described in this Section 3.1.2. from http://www.adobe.com/products/eulas/tou_typekit/ http://www.adobe.com/products/eulas/tou_typekit/
- steveax 13y agoSure, but if the fonts are licensed for being downloaded from your website (which isn't the case with typekit) it should not matter. I think the crux of the biscuit here is does the license allow you to host and serve the fonts, or must they reside on another server (which is the case with typekit and most -- perhaps all -- of the font subscription services). How the browser downloads the font file from your server is not really the issue.