|
The OPF is the key.
Think of it as both being like a combination shopping list/recipe instruction which says "pick up 1 jar of pickles from aisle 7, 2 tubs of ice cream from the Frozen Foods department, and a 200mL bottle of Pepto-Bismol from the Pharmacy", then "eat one small dill pickle, eat one spoonful each of Maple Walnut Swirl and Wasabi Butternut Crunch, if queasiness results, take 10mL of Pepto-Bismol".
All your html and image files must be declared in the <manifest>. Otherwise the parser won't know they exist and they don't get included in the book. If your images are in a subfolder, that has to be reflected in the href you put in the <item> so it knows where to find them.
Then your <spine> has to list your html files (images not necessary) in the order you want them to appear in, like chapters in a book.
To get the TOC showing, you have to put a line in the <guide> section to let the parser know it exists. I can't remember the exact syntax off the top of my head, but it's pretty simple and the Amazon Kindle Publishing Guidelines has some detailed info on how to do it.
The .mobi is just the "baked" version of the book once you've assembled and fed all the ingredients into the "mixer" which is KindleGen (sometimes "scrambler" might be more appropriate).
The location progress bar in KPreviewer is non-clickable. To simulate the 5-way controller flicking, use the double-arrow buttons on the toolbar.
Hope this helps and wasn't too incomprehensible an analogy.
|