View Single Post
Old 10-15-2017, 02:59 PM   #9
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by AlanHK View Post
I have a book with CSS like:

Code:
body {font-family: serif; }
@font-face { font-family: 'Fraktur'; font-weight: normal; font-style: normal; src: url('../Fonts/OldEng.ttf'); }
.Fraktur { font-family: 'Fraktur', serif; font-style: normal; }
And apply it with a span:
<span class="Fraktur">Christmas Greetings!</span>

I can choose a font on Kindle, but then the Fraktur style doesn't show. If I choose "publisher font" then everything else becomes Bookerly. So the reader can choose the body font, at the cost of screwing up the display text.
Is that what you meant?
You have two problems. One is the font-family in body. That has to go. The other is the use of Fraktur. The way the Kindle works is you either use a font from the list or you use Publisher font and get whatever the default is.if you don't need Fraktur, remove it too. If you do need it, then you may be screwed. Embedded fonts is one thing Amazon botched big time.
JSWolf is offline   Reply With Quote