Thread: Fonts won't embed on Kindle Fire
View Single Post
Old 10-27-2020, 01:48 PM   #36
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,503
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 Quoth View Post
That didn't work either. Subsetting an epub to epub.

I looked at the log and concluded the location of Courier was odd.
It was an ancient GST/GSP supplied font from the 1990s. I replaced it with a different Courier/Monospace style font in the proper system font location by changing the paragraph style that used it.

Subsetting works now on converting docx or epub to epub.

I was suspicious it had to be a dodgy font as otherwise there would be other reports.
It saves about 1/5th of the file size using subset fonts. Which is significant, but as I thought not show stopping either. I should look at the cover images in the advert burb rear matter.

Now I'll have to check EVERY document!
The size does matter, indeed, particularly vis: delivery fees, but the real gain, to my way of thinking, is that you've subset the font so that it can't be lifted or used, from within the eBook. Practically and legally, it matters.

Hitch
Hitch is offline