View Single Post
Old 10-15-2014, 01:22 PM   #97
Tony_A20
Enthusiast
Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.Tony_A20 knows what's going on.
 
Tony_A20's Avatar
 
Posts: 39
Karma: 25000
Join Date: Dec 2009
Device: Kindle 3
The Answer!

I found this on the web.

"The font-family property is special in the sense that the initial value is not fixed in the specification but defined to be browser-dependent. This means that the browser’s default font family is used. This value can be set by the user."

I believe the above is the underlying cause of the font-family application problems I experienced.

An embedded font is dependent on a CSS or styling description and the font family cannot become a default. Therefore the font-family description must be applied to each individual use either by repeating the font-family class or by forcing the font-family use by means of the "inherit" property.

End of story.

Tony
Tony_A20 is offline   Reply With Quote