View Single Post
Old 07-18-2022, 01:38 PM   #59
bookman156
Addict
bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.bookman156 ought to be getting tired of karma fortunes by now.
 
Posts: 368
Karma: 1000000
Join Date: Mar 2016
Device: none
Quote:
Well, for one thing--the first honker--you're building an old-style MOBI (KF7) which doesn't support embedded fonts. That's the first part.
Ah, interesting. Didn't know that.

So how to load an EPUB onto the Kindle such that it does show embedded fonts?

Quote:
Well, from a KDP standpoint, that practice=bad. Firstly, if you did that with a file you were uploading to the KDP platform, the font would be stripped, immediately.

Secondly, if it did slip past, it would make the body font unchangeable, which is VERBOTEN on KDP.
I don't use KDP at all. Are there any repercussions for putting font-family on the body otherwise? Or will it also interfere with sideloading the EPUB to a Paperwhite?

Is it better to put font-family on the p tag and h tag then? Or is this just KDP weirdness?
bookman156 is offline