Quote:
Originally Posted by NIRC
I embed the font in an EPUB file (generated with InDesign). It displays perfectly. Then I used Calibre to convert it to MOBI. The font does not display. Next, I tried Kindle Previewer 3 to convert to MOBI. Again, no go.
Franky, I don't know how to check the code in the MOBI files governing embedded fonts for changes from that in the EPUB. But thanks for asking...
|
Well, Calibre "MOBI" isn't a KF8/KF7 package, a "dual mobi" and that older format is no longer supported by KDP, so that one is explicable. The MOBI file generated by KP3 is completely different than that which is created by Calibre.
When you say that you 'embedd[ed] the font in an EPUB...generated with InDesign," how
exactly are you doing that? Are you opening up the file in Sigil, and adding the font? And ensuring that the font is called correctly, in the CSS?
Or are you assuming that because you call it in InDesign, that it's being embedded correctly in the ePUB? Are you subsetting the fonts, in INDD, when you export them?
If you test an ePUB that you made before, does the font still render, or no? Is the font an otf or ttf file?
Amazon, KDP and the eBook format of "MOBI" is not a static thing. Fonts that worked in, say, 2015-2016 don't necessarily work today and fonts that didn't, do (yeah, I'm lookin' at you, Papyrus!). If you want font embedding to work in MOBI, or for that matter, ePUB, as both are moving targets, you really do need to learn at least enough to read the coding in the ePUB (or HTML source files, etc.) and the resulting MOBI. This isn't a criticism, but we've had to adjust our font embedding more than once, over the years, to change with the altered rendering schema of KDP.
Offered FWIW.
Hitch