View Single Post
Old 08-10-2016, 08:42 AM   #4
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,099
Karma: 92190113
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by Notjohn View Post
Do you think the Kindle conversion (between Step 6 and Step 7 in the publishing process) is identical to the conversion done by KindleGen and Kindle Previewer? I build an epub and upload to the KDP, and I've never had a problem.
It appears to me that the KFX conversion process that occurs as part of Amazon book publishing is much more reliable than the version of that function in the Previewer. I suspect that it wasn't practical for them to include some parts of the production conversion process in the stand-alone Previewer so they had to re-implement some of the software. The new code has bugs.

Also, the stand-alone version appears to be more strict about what combinations of tags and styles it will allow when compared with the production version. I don't know why.

I am in the process of testing Previewer version 3.4 and it does appear to be better at conversion than the previous 3.x versions. It also produces more useful error messages when a conversion failure occurs. Unfortunately it doesn't display these messages to the user!

I am in the process of updating my KFX Output calibre plugin to support Previewer version 3.4. That plugin has the ability to capture conversion error messages from the Previewer and display them to the user. Even when they are cryptic, something is better than nothing.

Quote:
Originally Posted by Notjohn View Post
A few of my older books however are not Enhanced Typesetting enabled. Do you think that means they are bug-infested?
Older books that haven't yet been converted to support Enhanced Typesetting most likely have something in them that is being rejected by the conversion process. Feeding such a book though the Previewer may be useful in determining where the specific problem lies. You can iteratively cut out parts of the html/css until you narrow down what it doesn't like.
jhowell is offline   Reply With Quote