Thread: Fonts won't embed on Kindle Fire
View Single Post
Old 10-27-2020, 11:36 AM   #35
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,389
Karma: 107076273
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by Hitch
What Doits says^. Don't subset on the way "in." Subset when it's done. Works a treat as does Doits' font subsetting plugin.

Hitch
Quote:
Originally Posted by Quoth View Post
I'll try that as almost everything on Calibre works best with an epub2 source!
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!
Quoth is offline