Thread: Help: missing embedded fonts after ePub3 transfer to Kindle
View Single Post
Old 03-03-2023, 10:04 AM   #25
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 Nightjar View Post
Nope. I said right from the start that we created a new ePub3 version from scratch. And this came after having successfully published ePub2+mobi versions for more than a decade. If you want to know the average number of fonts we used, I can say that on average we used 12 font files with no problems at all on Kindle readers.

I was looking for an answer just to understand why when I create a mobi+azw3 package using Kindle Previewer 3 to convert my ePub3 file, the ebook does look perfect on any Kindle reader. However, when I send the very same ePub3 file using SendtoKindle or email to the Kindle reader address, the results are horrible, with missing fonts and other CSS flaws that ARE NOT PRESENT on the mobi/azw file converted from the very same ePub3 source.

This means that something is getting modified or stripped out by Amazon in the process. But you all know that Amazon is dismissing mobi/azw file loading, so I'm back to square one.
Yes, but we've used ePUB2 for mobi-building since...IDK, 2013, I think and we've still run into massive issues with that many fonts. I don't know if you're embedding fonts that you don't actually call--that could easily be it--or what, but I've seen the font-stripping thing more than a few times and we counsel our customers now to keep the font overload to a minimum. (and of course, for design reasons, it's best anyway.)

Amazon is dismissing email-to-kindle MOBI loading, certainly. Given that they are still supporting MOBI for FXL, I would suspect that until that's changed, sideloading a mobi will still be viable.

I still have NO idea why your CSS consultant or whatever he is made that recommendation to you. Seriously.

I would point out that as vexatious as Jon (Wolfie) can be, he's not wrong about ePUB2 backwards compatibility for the non-Amazon vendors. FWIW. Probably still a LOT more ePUB2-reading devices in the wild out there than there are ePUB3.0. if that code is indicative of your ePUB-vendor offering. I know, that's not what you asked--but he's not wrong.

Hitch
Hitch is offline   Reply With Quote