View Single Post
Old 09-18-2023, 09:16 AM   #8
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,375
Karma: 20212733
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by WV-Mike View Post
I don't understand. The name of the font has a dash in it. So why remove the dash in the font name reference?
src: url(../Fonts/Fontin-SmallCaps.otf);
h1 {
font-family: "Fontin-SmallCaps"

Thanks,
WV-Mike
There is an internal name built in to the font (like metadata) that does not match the name you gave it in the font-face declaration.

filename: "Fontin-SmallCaps.otf"
internal metadata name: "Fontin SmallCaps"
@font-face declaration: "Fontin-SmallCaps"


Filename doesn't matter. What matters is the font-face declaration does not match the internal metadata name. This MAY cause an issue on SOME readers. To be safe though it is better to make them the same by changing the declaration and any references to match the internal name:

Code:
font-family: "Fontin SmallCaps", sans-serif;

Last edited by Turtle91; 09-18-2023 at 09:22 AM.
Turtle91 is offline   Reply With Quote