I was experiencing this same symptom – 404 on woff files in Chrome – and was running an application on a Windows Server with IIS 6. If you are in the same situation you can fix it by doing the following: Solution 1 “Simply add the following MIME type declarations via IIS Manager (HTTP Headers … Read more
The solution seems to be to add multiple @font-face rules, for example: @font-face { font-family: “DejaVu Sans”; src: url(“fonts/DejaVuSans.ttf”); } @font-face { font-family: “DejaVu Sans”; src: url(“fonts/DejaVuSans-Bold.ttf”); font-weight: bold; } @font-face { font-family: “DejaVu Sans”; src: url(“fonts/DejaVuSans-Oblique.ttf”); font-style: italic, oblique; } @font-face { font-family: “DejaVu Sans”; src: url(“fonts/DejaVuSans-BoldOblique.ttf”); font-weight: bold; font-style: italic, oblique; } By … Read more
You can implement your OTF font using @font-face like: @font-face { font-family: GraublauWeb; src: url(“path/GraublauWeb.otf”) format(“opentype”); } @font-face { font-family: GraublauWeb; font-weight: bold; src: url(“path/GraublauWebBold.otf”) format(“opentype”); } // Edit: OTF now works in most browsers, see comments However if you want to support a wide variety of browsers i would recommend you to switch to … Read more
This could be done via CSS: <style type=”text/css”> @font-face { font-family: “My Custom Font”; src: url(http://www.example.org/mycustomfont.ttf) format(“truetype”); } p.customfont { font-family: “My Custom Font”, Verdana, Tahoma; } </style> <p class=”customfont”>Hello world!</p> It is supported for all of the regular browsers if you use TrueType-Fonts (TTF), the Web Open Font Format (WOFF) or Embedded Opentype (EOT).