|
To summarize:
The font-family attribute should be identical in each of the @font-face declarations for all of the font-style variants for a particular font. And because of that, there's no good reason why the font-family attribute shouldn't match the font's internal name (since doing so will guarantee functionality on fringe device/apps, or fringe fonts--with zero downside for doing it).
It's the url attribute that should point to distinctly separate files (blahblahblah-normal.ttf, blahblahblah-ital.ttf, blahblahblah-bold.ttf, blahblahblah-bolditalic.ttf, blahblahblah-smallcaps.ttf, etc...)
Out of curiosity; what is your rationale for wanting to use something other than the font's internal name for the font-family attribute?
Last edited by DiapDealer; 06-29-2017 at 11:44 AM.
|