Your rule of CSS at-rule
, to @font-face
, meets with incorrect statements, reason why it is not interpreted by some browsers.
Correct formatting
@font-face {
font-family: 'Calibri';
src:
local('Calibri'),
url('wp-includes/fonts/calibri.ttf');
src:
url('wp-includes/fonts/calibri.eot'),
url('wp-includes/fonts/calibri.eot?#iefix') format('embedded-opentype'),
url('wp-includes/fonts/calibri.woff') format('woff'),
url('wp-includes/fonts/calibri.ttf') format('truetype');
}
Explanation
Specify search by "local source" before any other address:
src:
local('Calibri'), /* local */
url('wp-includes/fonts/calibri.ttf'); /* remoto */
Note that this statement should end with ;
and not with ,
.
Specify sources for other files in the most likely order of use and in a separate declaration:
src:
url('wp-includes/fonts/calibri.eot'),
url('wp-includes/fonts/calibri.eot?#iefix') format('embedded-opentype'),
url('wp-includes/fonts/calibri.woff') format('woff'),
url('wp-includes/fonts/calibri.ttf') format('truetype');
When programming on Windows servers or Linux servers, the tilt of the bar on the web addresses is always /
:
"http://www.example.com/fonts/minhaFonte.eot"
Not absolutely necessary for your particular case, but the names of the source families must be involved by '
or "
for a correct interpretation by the browsers:
The names of source families other than generics have to look like one string cited, that is, within '
or "
. Alternatively, if not within quotation marks or quotes, they should be as a sequence of one or more identifiers.
In your case it turns out to be irrelevant because it’s a single word Calibri
, but it is the note for future readers.
Related
For these cases, we can use the generator of web-font present on the web-site Fontsquirrel which seeks to generate the right files for each browser as well as the ready-to-use style sheet on our web-site.
After all, the source is not found (404) or the browser has a problem with the source (does not render, uses another source, etc)? Which browser versions have you tested? IE, for example, to this day has no full support for TTF and OTF fonts.
– Vinícius Gobbo A. de Oliveira
If the mistake was
404
should not give in Chrome, so can delete this option ..– thecreator
Behold here if this answer solves the problem. Since it is similar to the question..
– thecreator
My Firefox shows the font perfectly (at least I don’t see any differences between Firefox and Chrome). Questions with external links should be avoided, because it is not always possible to reproduce the problem in pages that are being modified.
– Guilherme Nascimento
Rafaella this other question/answer solves your problem?
– Sergio
See if this helps 
 
 http://answall.com/questions/3458/font-face-n%C3%A3o-funciona-no-firefox-mas-no-ie-e-Chrome-funciona
– Claudia Mardegan