Quote:
Originally Posted by Doitsu
The only thing that KindleGen looks for in epub2 books is the cover metadata entry. E.g.
Code:
<meta content="cover.jpg" name="cover" />
and this entry can be easily added in the Book Browser. IMHO, it would be difficult to automatically add this entry, if the Image folder contained multiple images. |
True, but "in the beginning it was not so." Kindlegen used to have trouble with double or no cover images; now it seems to do the right thing most of the time if the above metadata is present. In fact, I always put this in the epub as well. It doesn't need to be changed for the mobi precursor.
I also do a couple of other tweaks:
To prevent the "double cover" issue, I point the "cover" guide element to the actual cover image (not the cover.xhtml file) and delete the cover.xhtml file:
Code:
<reference type="cover" title="Cover" href="Images/cover.jpg"/>
and change the title of the "text" guide element to "Start Reading":
Code:
<reference type="text" title="Start Reading" href="Text/Chapter001.xhtml"/>
The above is probably just superstition, but at one time it was thought that it helped to ensure the book opened at the intended place.
Beyond that, I don't do anything special to the mobi-precursor epub, other than avoiding CSS selectors such as :first-line and :first-letter that don't work reliably across all or most of the kindle variants.
Quote:
|
If you have ideas for new KindleGen plugin features, please post them in KindleGen plugin thread. I might add them in the next version.
|
Well, the only new feature I can think of off the top of my head would be the ability to configure it to save the mobi to the same path as the epub being edited, and use the same filename with mobi extension. E.g. if I'm editing
~/ebooks/MyNewBook/PigsInSpace.epub then the mobi would be
~/ebooks/MyNewBook/PigsInSpace.mobi. (That is, configure it to do so automatically, without having to edit the plugin's config file each time.)