Quote:
Originally Posted by Doitsu
It might be easier if you generated .ePubs with InDesign. KindleGen can compile them and if you rename them to .zip, you can navigate them with Windows Explorer and replace files. (Don't unzip them, though.)
Exporting ePubs might also solve your unspecified font problem, and, depending on the InDesign version that you have, you might even be able to define the Go to Beginning anchor and the corresponding guide item directly in InDesign.
|
In this instance, I know why Tugger is doing it the way he/she is. And it's a valid reason. Creating an ePub with InDesign is going to result in an ePub that
doesn't have the special media-queries already in place that allow you to tweak certain aspects of the mobi format and the KF8 format independently. He would have to know how to manually
add the correct media queries to the epub to fine-tune how kindlegen builds the two halves of the hybrid file
before feeding it to kindlegen.
By using the InDesign Amazon plugin, those media-queries are created
for him, and are already in the source portion of the generated mobi. All that remains to be done is to unzip that source and
tweak—rather than trying to
create those media-query sections—before re-feeding it to Kindlegen.
An ePub produced by InDesign would probably need even
more tweaking before it was in any kind of shape to be considered "good" mobi source-code. This way, at least, the xhtml and css is being created with the mobi format in mind all along. It may not be
perfect, but it's a lot farther ahead of the curve than straight-up, InDesign xhtml/css would be without the Amazon plugin.
