View Single Post
Old 08-16-2022, 11:22 AM   #17
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: 80,044
Karma: 147977995
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 jhowell View Post
After seeing Jon's version of the original CSS, I believe that this book fell afoul of a feature of Amazon's publishing process intended to prevent publishers from overriding the customer's font choice. It looks like they put font-family properties in the style definitions of all of the various paragraph types used in the book. That is against Amazon's rules.
font-family: using sans-serif and.or monospace should not stripped out. It's using the default fonts on the Kindle. There are no embedded fonts. The comments just say what fonts were used in the pBook edition and where.

That's my thinking and I could be wrong here.

Last edited by JSWolf; 08-16-2022 at 11:25 AM.
JSWolf is offline   Reply With Quote