Quote:
Originally Posted by Doitsu
IMHO, that's probably the only approach that'll work.
Try the following:
- Build an .azk file without embedded fonts.
- Build an .azk file without images and embedded fonts.
- Successively delete 50% of the .html files and test the resulting .azk file.
|
FWIW:
You all know I'm not coder, just a poor bookmaker. But in terms of troubleshooting, using fonts, for the purposes of testing an AZK, is worthless, as K4iOS is a KF7 reader. That might at least shorten your troubleshooting efforts. The analysis is truly great, but as you noted--doesn't help you much with the "why" of why your file is failing. Did you take up Doits, I think it was, on his generous offer to try to build the file for you and see if it would then work on your device(s)? Or did I miss that (entirely possible)?
In terms of troubleshooting Amazon build issues--something I do have vast experience in--I highly recommend simple bracket navigation. Start out with something like, rip everything out of your ePUB except, say, Chapter 1. (Or even just the frontmatter, one page/section/file at a time). Build, sideload, and see if that works. If it does, add Chapter 2. It's tedious as crap, but it's the only way I've ever seen really work in narrowing down the problems. I usually manage (except with font issues, which can still remain mysterious, no matter HOW much troubleshooting you do) to find the single item that's screwing up the file that way. Horrifically time-consuming, but at least it's (somewhat) faster than having to load builds from the KDP. (I'm not really posting this for you--you obviously don't need help in troubleshooting. I'm posting this for other, far less experienced folks who come along later and read this thread.)
Speaking of which, for
you, however: have you tried loading the same source file at the KDP, and seeing if the post-build MOBI (Step 7, I understand it is now) works on your iPad? Just as a comparative test?
Hitch