View Single Post
Old 09-18-2011, 07:28 PM   #6
pholy
Booklegger
pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.pholy ought to be getting tired of karma fortunes by now.
 
pholy's Avatar
 
Posts: 1,801
Karma: 7999816
Join Date: Jun 2009
Location: Toronto, Ontario, Canada
Device: BeBook(1 & 2010), PEZ, PRS-505, Kobo BT, PRS-T1, Playbook, Kobo Touch
It seems that most readers and browsers don't really check the media type. Which is good, because as far as I can find out, only one obsolete font ever got a assigned media type.
Still, for future compatibility, one needs something, and the most common recommendation seems to be media-type=application/x-font-otf (or ttf, depending on the file type). x is for extension, as there is no assigned type for fonts. While vnd.ms-opentype probably is correct, both otf and ttf are recognized standard types, so I don't think we need to use the vendor specific designation, as long as we use x-font-something.
But font/anything is incorrect, as IANA doesn't have a font mime-type directory.

At least, that's what I'm going to do from now on.
pholy is offline   Reply With Quote