eBooks rant

posted by Rob on September 27, 2011 08:30 AM

EpubLogo.jpg

Commercially speaking, ebooks are huge, but I'm continually struck by how unready they are for the spotlight. There's a long list of things that need to happen before ebooks are ready for widespread popularity - despite the fact that moment has already passed. Bear in mind I've been saying 'the ebooks are coming' for years - and I've been fairly happy about that prospect. But currently we're in an awkward transition phase full of problems which I think should have been ironed out five years ago.

I've blogged before about how some high-profile e-titles are sold in their hundreds of thousands full of formatting and text problems which would be considered a scandal in a print edition. For instance, Kindle editions of Stieg Larsson books contained characters which wouldn't display properly on iPads and iPhones. Can you imagine a situation where a paper edition of a global bestseller had an ellipsis replaced by a row of square boxes? Reviewers would be disgusted and proofreaders would be fired - and possibly sued. The situation is of course far worse in lots of lower profile ebooks.

Ebook pricing is still pretty questionable too - giving rise to situations where a canny shopper can sometimes order a paper book for less than the equivalent download. We're still trying to decide what rights are granted to an ebook owner (and whether we even consider it 'ownership' from a legal standpoint or merely rental) but one thing is for sure: ebook terms will be more restrictive than the paper equivalents, so the current price parity seems counterintuitive. In the UK we also have the nonsense of VAT applying to ebooks but not to paper books. This is apparently because an 'ebook' is not considered to be a type of book. That's an assertion which clearly needs challenging in court (and I know just the barrister to do it, if anyone wants to put up the cash.)

Moreover, our ebook standards are riddled with holes: epub 2.0.1 is full of inconsistencies and failings, some of which threaten to make successful titles unusable and the Kindle format has similar problems too. For instance, some of the earliest adopters of technology such as ebook readers are programmers, and these people will naturally want to buy programming manuals in electronic form. Unfortunately I've owned several tech books where snippets of example code make no sense because part of the comment from the previous line wraps around and appears on its own line, making you think it's a separate command. This only goes away when the text size is set to its tiniest size which is much smaller than the default most people will see. When you're learning a new language you absolutely need to know what's a command and what's a comment. This is never a problem with paper editions (people would demand a refund) but it's cropped up several times in just my tiny technical library. We're talking about full-price books by reputable publishers which risk not being fit for purpose.

And our DTP software - InDesign being a prime example - handles the creation of ebooks as though it's some obscure feature that the programmers don't really expect anyone to use - and consequently it doesn't matter if it fails often and requires ingenuity and doggedness to use. Ebook creation is non-existent or broken in earlier versions of InDesign and barely usable in the latest CS 5.5 version. And when you preview your ebooks in the software Adobe provides you get minimal feedback about potential problems and can easily sign off on a file which will fail to display perfectly in other e-reader software.

And finally, electronic e-readers still aren't as good as they could be. The super-popular current generation Kindle has a horrible experimental browser built into it which you sometimes need to use to connect to public wifi. I've failed to make a connection on many occasions. And no backlight? I regularly end up using my iPad to read ebooks rather than turn on a light so I can use my Kindle. And of course it needs a way for you to actually buy ebooks that doesn't seem like an afterthought - or doesn't assume you have a laptop handy, thus undermining part of the point of a Kindle. But maybe that will change soon, because...

The new Kindle reader is due out any minute and if it's any good Amazon will presumably sell millions over the Christmas period. I do hope when the lucky recipients of a Christmas Kindle download their first ebook the title they want has actually been made available and they don't discover a weirdly priced, weirdly formatted disappointment. We set our standards so high when it comes to printing on paper; I do hope we'll get our act together on the digital side of the industry before we sell too many more millions of ebooks and take much more of our customers' money.

spacer

Comments: 3


Hello. Grateful if you can explain (in layman's terms) why ebooks contain so many formatting and text problems. Presumably the file that is digitized is a PDF, which is identical to the printed (and 'error-free') book. Are the errors introduced because the PDF has to be reformatted to fit on, for example, a Kindle's screen? Or ... Many thanks, Steve


Hi Steve. Well, I don't claim to be an expert on why these problems creep in, but I do know some of the reasons. I've already mentioned that getting ebooks out of industry-standard typesetting software like InDesign (typically into epub format) is complex and tricky.
Then you have to convert your epub book to something you can sell in the Kindle store (where the vast majority of ebook commerce takes place). That conversion process can introduce problems.
Then you have to realise that the final file will be displayed on a number of platforms. Amazon clearly haven't made sure that they have identical functionality across all Kindle devices and the Kindle software running on various phones, computers and tablets - partly understandable given that iPads have colour touchscreens with backlights and Kindle devices have passive, read-only monochrome. (The row-of-square-boxes problem looked to be a font which was supported on Kindle devices but not on iOS devices running Kindle software - the sub-division of Random House which produced it presumably only checked it on some, not all, Kindle platforms (understandably)).
Plus you've also got the fact that there are lots of user-controllable settings at each stage of the creation process, and the people who know what the finished book should look like are often not the people wrestling with file conversion - or if they are, they may not have done all the research they need to about all the settings they need to control. For instance, a few very unfortunate ebooks have full justification turned on, but hyphenation turned off. That's a recipe for layout fugliness. Similarly, there are ways to prevent line-wrapping of text, but for most text you want it to wrap (because you want the text to reflow for different screen sizes). It's just in a few cases (e.g. code examples in techie books) where someone should have prevented line-wrapping but clearly didn't think it through (or didn't spot it was a problem on whichever platform they proofed the file).
You've also got the problem that the printed page has a lot more layout possibilities than are supported in any current ebook format. Moreover, any time the size of the traditional printed page changes, we re-typeset the whole book. With ebooks we're attempting to typeset once for all screen sizes and types - that's a very tricky thing to accomplish. (Another example of problems I've noticed is that some ebooks use a picture of a table of figures and numbers rather than live, reflowable text in order to preserve a given layout, but that picture needs to be created with a background. Change the background colour of the Kindle app to ivory instead of white and suddenly all these tables look very odd with their white backgrounds). And to give another example, many ebook formats can't support multiple columns so what do you do if your book contains them? In effect what I'm saying is that every ebook currently created is a bespoke effort (often done badly); we're not yet at the stage where a book that's been typeset for the printed page can be automatically reformatted for, say, reading on a Kindle without a risk of problems creeping in.


Rob, Very kind of you to take the time and trouble. Many thanks, Steve

spacer

Post a comment

We love hearing from our readers, but please stay relevant and pleasant. The comments are for responding to the specific blog post above. If you have any other queries, please contact Snowbooks via email. Off-topic or offensive comments will be removed without notice.

To screen out automated spam, please answer the following very easy question:

What colour is nice, new snow?

(please use all lower-case characters for your answer; no capitals)


Back to the blog »