Thread: Body font best practice for flexibility
View Single Post
Old 09-20-2024, 01:42 PM   #10
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,891
Karma: 146918083
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 nabsltd View Post
Modern Kindle software never ignores embedded fonts...they are used when properly referenced.

OTOH, if there is a font-family attribute in the styling for the body element, this is considered a "publisher font", and the Kindle uses it by default as the "body font". When reading a book with a "publisher font", "Publisher Font" is added to the list of fonts to choose from, and the user can switch to/from "Publisher Font" just like any other font in the list.

A book sent to Amazon via KDP (and possibly even Send to Kindle) has extra constraints about fonts during the conversion process, but the Kindle itself perfectly adheres to the CSS spec when encountering font-family pointing to an embedded font.
Is this the way it is with KF8 and/or KFX?
JSWolf is offline   Reply With Quote