Tim Brown Posted May 15, 2009 Posted May 15, 2009 This topic was imported from the Typophile platform Found the following at Garrick Van Buren's "Kernest" and figured Garrick might have better luck with an answer here at Typophile: Many of the assets browsers understand have specific MIME types to provide hints to the web browser (and email clients) on how to process them. Everything from images to javascripts to Microsoft Word docs have a corresponding MIME type. A basic example of this: PDFs might be rendered via a browser plugin or the browser might hand it over to Preview.app. With the adoption of @font-face and the corresponding proliferation of embedded fonts - is a font-specific MIME type needed? Anne van Kesteren asked this question back in 2008 - and the closest answer I can find is ‘application/octet-stream‘ might be fine (since it already exists) but it definitely doesn’t feel clean. From: http://kernest.com/blog/archive/font-face-and-font-mime-types
Dunwich Type Posted May 15, 2009 Posted May 15, 2009 Isn’t this a question for the browser programmers? They don’t seem to be having any problems implementing @font-face so far.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now