View Single Post
Old 09-17-2024, 01:01 PM   #9
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 524
Karma: 8500000
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by JSWolf View Post
I thought Kindles ignored embedded fonts unless you use Publisher Font.
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.
nabsltd is offline   Reply With Quote