If you are just interested in the use of Access-Control-Allow-Origin:* You can do that with this .htaccess file at the site root. Header set Access-Control-Allow-Origin “*” Some useful information here: http://enable-cors.org/server_apache.html
The issue here is not line height but vertical placement of glyphs, in particular the location of the text baseline. That’s something that the font designer has decided on; the designer draws glyphs and places them in the em square, the conceptual device that has height equal to (or defined to be) the font height. … Read more
You have to add the folder to the assets path (to file config/application.rb), see Rails Guides config.assets.paths << “#{Rails.root}/app/assets/fonts” And you should use the asset_path helper: src: url(‘<%= asset_path(‘Chunkfive-webfont.eot’) %>’);
This could be related to an issue with the Security Settings as described in this bug report. In Internet Options go to: The Security Tab Security level for this zone Custom level Downloads Font Download If it’s Disabled then you need to Enable it.
We had this problem last week – the problem is that your assets will be compiled to have MD5 hashes on them, whilst your standard CSS will still be looking for their “standard” names. This is a problem with images & fonts. @font-face { font-family: ‘akagi’; src: asset_url(‘fonts/akagi-th-webfont.eot’); src: asset_url(‘fonts/akagi-th-webfont.eot?#iefix’) format(’embedded-opentype’), asset_url(‘fonts/akagi-th-webfont.woff’) format(‘woff’), asset_url(‘fonts/akagi-th-webfont.ttf’) format(‘truetype’), … Read more
Since 2017 you have preload MDN: The preload value of the element’s rel attribute allows you to write declarative fetch requests in your HTML , specifying resources that your pages will need very soon after loading, which you therefore want to start preloading early in the lifecycle of a page load, before the browser’s main … Read more
I found a solution but I cannot see the reason why it works (well, only one reason – it’s IE :D). What I did was to put the same site on Apache and test again. On Apache the fonts worked fine even when using Refresh button. Then in the network inspector I saw that Apache … Read more
You have to have an @font-face declaration for each font: @font-face { font-family: OuachitaWayWbw; src: url(‘fonts/Ouachita Way Wbw.ttf’) format(“truetype”) ; } @font-face { font-family: ChromeYellowNF; src: url(‘fonts/Chrome Yellow NF.ttf’); } The single quotes are not required. If you are wanting to use custom fonts for IE9 you will need to also provide an “.eot” font … Read more
As Simon pointed out, the CSS @font-face declaration can be used to implement traditionally non-web-safe fonts on your site. If you want to try it yourself, definitely check out Paul Irish’s now famous bulletproof font face implementation, which links to FontSquirrel’s font file generator. It’s now supported cross-browser with the right implementation, although with most … Read more