Quote:
Originally Posted by DiapDealer
Being ignorant of the KDP process, I feel it's important for those following along to understand exactly what the nature of the file is that you're "pulling back down from KDP." Is it a dual format file (mobi & kf8) like kindlegen produces, or is it either/or -- like what the customer would recieve when purchasing the ebook?
When you use mobi(kindle)unpack to examine the contents of that file, does it produce both a mobi7 folder AND a mobi8 folder? If there is no mobi8 folder, then the file is mobi7-only and will never have embedded fonts included.
There may be other issues in play, but I can't help thinking that the file you're getting back from KDP might not be what you think it is. But I can't know for certain until someone familiar with KDP can explain the nature of the file(s) you "get back" from them.
In short, I think it's possible that you're looking for embedded fonts in a mobi-only file that will never contain embedded fonts because the format doesn't support them.
|
Diap:
No. What he's getting back is the pre-PW (publishing workflow) final mobi. The only thing that happens after this point is DRM and any finagling that Amazon does with the SRL, etc. The preview mobi that he's DL'ing is a complete, fully-formed, source material + K7 file + K8 file mobi.
Quote:
Originally Posted by DiapDealer
Another quick question: the fonts aren't obfuscated in the epub being uploaded (or in the epub being fed to kindlgen locally), are they? Amazon adds their own obfuscation (to all fonts) to the finished product. A process that relies on the fonts being un-obfuscated to begin with.
|
No. If he was, the KG wouldn't gen. It would crash and burn. Whatever it is...it's something else. I thought about this too, but any file with an encryption.xml file in it for ePUB won't Genn via KG or KP.
It's interesting.
Hitch