This is the @font-face
declaration I have used:
@font-face { font-family: SolaimanLipi; src: url("font/SolaimanLipi_20-04-07.ttf"); }
This is working perfectly in Firefox but not in Chrome. After "inspect element" I got the following message:
Resource interpreted as font but transferred with MIME type application/octet-stream.
Any suggestions will be appreciated.
TTF/OTF - TrueType and OpenType font support is Fully Supported on Google Chrome 71.
TTF font files has the following MIME type: font/ttf . Before February 2017: TTF does not have a MIME type assigned. You'll have to use the more general application/octet-stream , which is used to indicate binary data with no assigned MIME type.
go to google.com/fonts select all fonts that you will use by adding them to your collection, then click "use" - scroll down.
As usual, different browsers have different needs. Here is a cross browser @fontface declaration, taken from the Paul Irish blog -
@font-face { font-family: 'Graublau Web'; src: url('GraublauWeb.eot'); src: local('☺'), url('GraublauWeb.woff') format('woff'), url('GraublauWeb.ttf') format('truetype'); }
.eot is for IE, the rest of the browsers use either .woff or .ttf If you need to generate the different types from the source font, you can use Font Squirrel's font-face generator
You also need to an .htaccess to the location of the fonts adding the following types:
AddType application/vnd.ms-fontobject .eot AddType font/ttf .ttf AddType font/otf .otf AddType application/x-font-woff .woff
You can ignore the warning and may want to consider this post on the topic, Proper MIME type for fonts
Which also mentions the following:
"Note: Because there are no defined MIME types for TrueType, OpenType, and WOFF fonts, the MIME type of the file specified is not considered."
source: http://developer.mozilla.org/en/css/@font-face
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With