Quote:
Originally Posted by JSWolf
In the past (pre-Kobo) most problems with Readers were due to errors in eBooks. So as long as i'm editing the code, I may as well check that I didn't make any structural mistakes. Also, I have checked some eBooks before making any changes and yes, there were errors.
|
I have to agree with Jon here. I do check my ebooks for errors and correct any that are found. And yes, many of those errors are found in books from both indie and traditionally published books.
One recent horrible example was a freebie which had a single text document which was a web page—the code for different browsers was a dead giveaway
—which did not display happily on my epub ereaders though the mobi version was not all that bad. A bit of splitting the various text segments, removal of unneeded javascript, etc., using Sigil's tool to convert inline styles to a stylesheet and then coalescing similar stylesheet entries wasted 30 minutes of my time but did give my wife a readable ebook.
The WebKit based renderer used by Kobo for .kepub.epub was not overly unhappy with the original epub though the attempted prettification of the chapter and part headers was a bit hard to take. Basically each letter had a random size making the chapter titles and headers look like a ransom note)