We are happy to announce improvements to our Kindle Publishing Tools - KindleGen, Kindle Previewer and Kindle Plugin for Adobe InDesign.
The updated KindleGen 2.5 software includes:
Improved transparent PNG conversion: Transparent PNG images are now converted to JPEG and will use a white background.
Unintended line breaks in Mobi7 when using some CSS properties ("margin-top: 0px" and "margin-bottom: 0px") has been fixed.
Resolved indentation issues in Mobi7 related to bullets and numbered lists.
Allows creation of Mobi7 book with Indexes (e.g. dictionaries).
CSS property "display: none" no longer induces an additional space in Mobi7 for inline tags.
The updated Kindle Previewer 2.5 software includes:
Kindle Touch preview mode.
Support for rendering KF8 content in Kindle Touch preview mode.
Multiple bug fixes
The updated Kindle Plugin for Adobe InDesign 0.97 (Beta) includes:
Support for Adobe InDesign CS6
Improved Table of Contents exporting - choosing styles from any document to apply to the table of contents; extended generation of navigational controls (NCX) for custom Table of contents.
Ability to specify alignment for all images.
Support for text styles for hyperlinks.
Ability to set the language metadata for the Kindle book.
Ability to export consecutive whitespace and newline characters.
All Kindle Publishing Tools and the Kindle Publishing Guidelines can be downloaded from http://www.amazon.com/kindleformat. Please refer to the Kindle Publishing Guidelines for help on using the Kindle Publishing Tools and for information on creating content for Kindle devices and apps.
For the detailed list of features and bug fixes for all tools, please refer to the specific tool's Release Notes.
Changes that I have noticed in KindlePreviewer 2.5:
Now it can find the cover image under "Kindle Fire" if your mobi file was created by KDP.
Output of KindleGen 2.5 does not show non-existent problems in clean HTML code (improvement over KG2.4 and KG2.3).
But some problems remain:
1) Under "Kindle for iPad" settings KP2.5 says that this program does not support fixed-layout ebooks. In actuality, Kindle for iPad supports fixed layout.
2) If you have a division tag with a background color after a pagebreak, you see this color before the pagebreak (under "Kindle Fire" and "Kindle Touch" settings of KP2.5).
3) With different settings in the "Devices" menu you see the cover as a full screen image on some devices but not others. Furthermore, you get different results if you build an ebook using KindleGen 1.2.
4) KG2.5 cannot create a full screen cover for Kindle for PC (the cover always has margins). This does not happen with KindleGen 1.2.
5) If you create a start location properly, Kindle Previewer 2.5 shows two "Beginning" items in the "Go to:" menu. This can be confusing for some users.
Output of KindleGen 2.5 does not show non-existent
problems in clean HTML code (improvement over KG2.4
I've never encountered such a problem myself. What markup would cause it?
4) KG2.5 cannot create a full screen cover for Kindle
for PC (the cover always has margins). This does not
happen with KindleGen 1.2.
Kindle for PC handles the cover image differently for Mobi7 and KF8 content. This is unrelated to KindleGen. You'll notice the cover displays the same for a Mobi7 produced with both KindleGen 1.x and 2.x.
The biggest problem I've run into is that the Kindle device mode displays in a window that is too tall leaving a large amount of white space at the bottom. Not really an issue for me, except that I find it annoying, but I'm sure it's going to concern a number of people when/if they encounter it.
Auto-flip is super nice, however. I will certainly be using that a lot.
Open the console, type "kindlegen" (without quotes, obviously), and strike Enter. This of course assumes that kindlegen is in the active folder or in your system path. I would [i]highly[/i] recommend setting it up in your system path.
[i]"1) Under "Kindle for iPad" settings KP2.5 says that this program does not support fixed-layout ebooks. In actuality, Kindle for iPad supports fixed layout."[/i]
I noticed that too. However, several people have complained that the new Kindle For iPad app isn't showing fixed format mobi books correctly on their iPads either. So...maybe there's still some fly in the ointment at this juncture where they don't really have the fixed format thing perfected for viewing on either the Previewer's ipad mode or on an actual iPad yet. They probably should have held off on that announcement last month untill they had all the bugs worked out. At least that's how it's looking to me.
There are a huge number of errors in that HTML file. What's surprising is how few warnings KindleGen 2.3 raises, not that it raises them at all.
I'm not sure it was a great idea to suppress this information, as was apparently done in 2.4, but I suppose it doesn't matter that much either way since KindleGen is very forgiving and it never provided comprehensive validation anyway.
**Open the console, type "kindlegen" (without quotes, obviously), and strike Enter.**
Alas, all I get is a statement of the Kindlegen build and the possible commands, even the simplest of which is too complex to render here. Apparently I am expected to enter the path to the book file and the name of the output file, something like:
Sure. A few specific examples of errors that are well represented throughout.
Line 266-267: italic tag outside of containing block
Line 258-278: span element containing paragraphs
Line 258: unterminated div element
Line 279: line break (<br>) outside of containing block
While you can get away with a lot of things that are technically errors on Kindle, clean HTML is always going to ensure the best results. Specifically I'd recommend conforming to XHTML very strictly. Pretty much eliminates surprises, as long as you're aware of Kindle-specific quirks that can trip things up.
All those kinds of errors are really typical though when saving from Word or any other word processor app as HTML. You have to look close at every single line to see what the conversion fouled up because there's always lots of tags in the wrong place (typically outside of paragraph tags). And then I run the file through the W3C validator so it can find anything I missed, and there's always something.
The best way I've found of doing it so far is to save the Word .doc (or whatever) as a .rtf and then copying the entire contents to the clipboard and pasting into MS Expression Web. You'll still have some errors but not nearly as many. But it takes a good hour to clean-up any novel length file before you can even begin to format it usually.
A span tag containing paragraphs is bad HTML, I agree, my mistake. But virtually all of the above-mentioned warnings from KG2.3 have to do with an opening tag and a closing tag located on different lines of code. Or a line break tag at the beginning of a line of code. Isn't it a bit of a stretch to call this an "error"? Can this cause a problem in any web browser or Kindle device?
Most web browsers and Word save web pages with the code split into many short lines of code. This inevitably causes the above-mentioned situation. Word2cleanhtml website produces this sort of code as well. Besides, it easier to read HTML code if you, for example, press the "Enter" key before each paragraph inside a div tag.
Admittedly, this sort of markup will cause problems with epubcheck, but who needs it anyway, unless you are trying to publish your ebook on a website that has 100 unique visitors per year?
Screw that crap. If you really are desirous of using KG, simply install it, and then drag and drop the file you want to use (OPF, HTML, whatever) on TOP OF THE Kindlegen.exe program in your directory. Literally. Just drag it and let it go. The mobi will build in the same DIR.
@man2010: if it's producing that type of code, then it's not producing "clean" code. Use Toxaris' macro from MR--works well. Hell, for that matter, use BookCreator macro and save the result as an RTF. You won't get that type of garbage. As K8 edges ever closer to ePUB (hell, it IS epub with very small exceptions), errors of this nature will become more problematic, IMHO. We don't put anything on KG or Previewer unless it epubchecks first.
We produce ebooks
Listed as an Amazon Professional Conversion Service: http://bit.ly/uFwMwb
An INScribe Preferred Conversion Partner http://www.booknook.biz/
Follow me on Twitter: @BookNookBiz
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur."