View Single Post
Old 10-15-2017, 01:30 AM   #6
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,463
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by AlanHK View Post
In the test epub I uploaded the html has has no divs, or classes.


But I tried again:

if CSS;
p { font-family: sans-serif; }
-- font is locked.

If
body { font-family: sans-serif; }
-- font is not locked.


But I've learnt not to expect everything Kindle to make sense.
Well, this is how they've set it up-and how it's documented in their Publishing Guidelines.

Quote:
I would expect that if anything would lock the font it would be "body", since that contains everything else. But not so, apparently
Right.

Quote:
How about the related issue:
If I have an embedded font for some display text, and to make the embedded font show you have to choose "Publisher Font" on Kindle. That made the body text sans for some stupid reason (surely the default is serif?), so I put "font-family:serif" in the body css. But that forced it to Bookerly. No way for the user to choose one of the other system fonts like Baskerville. I assume I could choose Palatino, Baskerville, etc. in my css, but again that leaves the reader stuck with my choice of body text. Which is better than sans but still not ideal.
This is a known thing. I don't know if Amazon considers it a bug; we first reported it to them several years ago, on the entire family of PPW/Voyage/Oasis devices. If you embed ANY font, any at all, for anything--even just a fleuron--the body font will immediately show as sans serif. To work around this, embed the font you want, for whatever you want, and use the body tag for the font you want them to be able to change. Right?


Quote:
Kindle is convenient but I miss the variety of layout of actual books and after a couple of months of just Bookerly it was palling, so I'm currently alternating between Bookerly and Baskerville for my own reading. So I don't like to take the choice away.

I'm beginning to see why some publishers just use images for special text rather than wrestle with this.
Well, I don't know how many books you've made, so it's hard for me to comment. We do scads--it's thousands now, which surprises me daily when I think about it--and I hardly think about it any more. YES, it can be frustrating, but...just think how boring it would be if it was always the same.

Hitch
Hitch is offline   Reply With Quote