Include the meta name="cover" in the OPF Metadata section
Why not just have it there in the first place?
Heu ... OK. Why not.
As this navmap was playorder 1, the script also renumber the other navmaps starting with 1
Not really necessary, but OK.
?? What is the other alternative? Something a la KDP Guidelines 3.2.3 Cover Image Guideline #3 ? I am curious, please.
Optionnaly create a new NCX with only the chapters headings (reduced navmap without nested subchapters)
Why? Amazon encourages nested ToCs.
Last time I used the app Kindle for PC on one of my mobi, It didn't care about my sexy nested TOC and flattened everything. It was a big eBook with a lot of headings, the toc (in the left of the screen) was unusable.
So I decided to put an option box to check/uncheck in the GUI to modify the INI file.
Another reason is that I took note somewhere that ... "The Kindle does not navigate well with the 5-way controller on multiple-level navPoint entries".
Is it (still) true?
Modify all HTML files to make reference to the new css file
Why not just change the name of one css file to match the name already referenced in many html files? Or have one master css file referenced in all html files and then use easily changeable @import statements to pull in the directives for whichever version (epub or kindle) you're currently working with?
The one referenced CSS file in almost 100% of my xhtml files looks like this:
Code:
@import url(../Styles/epub.css);
/* @import url(../Styles/mobi.css) amzn-mobi;
@import url(../Styles/kf8.css) amzn-kf8; */
I just comment out the first line and uncomment the next two come kindle time.
Yes. I agree that this is not a clean solution. I was thinking about another way to avoid to have to modify all HTML files. I only have 1 css file for mobi/kf8. So If I include in all files the line
Code:
<link href="../Styles/styles.css" rel="stylesheet" type="text/css"/>
The only thing I have to do is to replace in ../Styles the ePub styles.css by the mobi/kf8 styles.css. This way I don't need to modify any HTML file.
Now, I noticed you use 2 different mobi and KF8 css files. It is ok but, is there a reason I should be aware of? Or is it just your way of organizing your job?
Thanks.