Thread: Help: missing embedded fonts after ePub3 transfer to Kindle
View Single Post
Old 03-10-2023, 11:35 AM   #39
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
Ok, thanks also to all your suggestions, I made a new set of tests and can confirm that the "mess" with the CSS code and the embedded font is caused ONLY by the transfer of the ePub3 file through SendtoKindle app/webpage or via email to the Kindle reader's own address.

Our ePub3 currently on sale on Amazon displays all the correct (custom) fonts with any substantial changes to the CSS. The ebook looks quite similar to the preview displayed by Kindle Previewer 3. But the only way we had to be 100% sure was to buy one copy of our own ebook from the Kindle store.

This means that there is apparently no way to sideload an ePub3 onto a Kindle device without risking major CSS changes being applied. I think the only way around is to convert the ePub3 to a .mobi+.azw3 package via Kindle Previewer 3.

Below is how the look of a page changes on 3 different systems:



So, right now I'm stuck at a crossroad: my previous ePub2 template does not comply with WCAG 2.0 AA accessibility requirements, and my recent ePub3 template isn't backward compatible with older ePub2-only reading devices and software.

Any suggestion on what is the best path to follow?

Thanks!
Well, nobody hates to suggest this more than I, but what about simply making two ePUBs? One for ePUB2.x and one for ePUB3.x? The vendors that take each are pretty well delineated. Wouldn't that be easier than your gang trying to learn media queries based on devices, based on screen-sizes, etc.?

Hitch
Hitch is offline   Reply With Quote