View Single Post
Old 01-13-2012, 10:57 PM   #307
murg
No Comment
murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.murg ought to be getting tired of karma fortunes by now.
 
Posts: 3,240
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
Quote:
Originally Posted by JSWolf View Post
Embed a font. Put the font-family line to activate it in the body CSS style and if it displays, it's fixed. If not, it's broken still. This is where you'll find most eBooks hat have embedded fonts put the font-family to activate the main font.
I have noticed that when declaring fonts (@Font-Face, usage) in a CSS file in an ePub, the Kobo Touch seems to be case sensitive, in that either the file path and name has to be in the same case as on the device, or the font name casing has to match what is in the font file.

While the font name casing issue is definite, I'm not so sure about the file path casing issue (I was changing too many things at once).
murg is offline   Reply With Quote