>"Book publishers have been waiting for a mass-market ebook reader for
>years, the newspaper companies are dying for a new online business
>model, and normal people just want to read on the train to work."
>
>But they aren't waiting any more, because the Kindle ebook reader
>gives them all those things, with the massive marketing power of
>Amazon behind it. Ugly? Sure, but it works, and the last time I
>checked, Kindle units were selling faster than Amazon could build
>them. Yet TidBITS books aren't being read on Kindles. Since you're so
>enthusiastic about ebooks, the obvious question is "Why not?"
The Kindle is "out of stock," but Amazon hasn't released any sales
numbers that I've seen. They may have made 5000 units and stopped
there, for all anyone can tell. If they were serious about producing
it in quantity, one would think four months would have been enough to
ramp up production to meet orders in a timely fashion. Ours is still
on back order, and I still haven't seen one in the wild.
The other reason I'm not that enthusiastic about the Kindle is that
our readers aren't using them or wanting to use them in significant
numbers. In our reader survey, fewer people are interested in our
ebooks in Kindle format than in a form that's better for the
sight-impaired. The most desired alternate format is as a Web page on
a computer, with the iPhone/iPod touch close behind.
>"And of course, I'll be happy to upload to the iTunes Store an entire
>library of Take Control ebooks that are already popular with tens of
>thousands of Mac users."
>
>Once you convert them all from the present unsuitable-for-ebook-
>readers PDF format, that is. Authors and editors love PDF, because it
>gives them totalitarian control over the way pages look.
Yes, and that's because readers prefer books that are well-designed
for reading and for, in our case, conveying complex information. The
trends in book design include color and high-quality graphics because
those are no longer economically unfeasible. Current ebook readers
are like taking the Web back to HTML 2.0 on a black-and-white screen.
>Unfortunately, that same control locks in line and page breaks,
>making PDFs like TidBITS books unreadable on screens smaller than the
>page size they were designed for. I know, because I've tried to read
>the PDF version of Sharon's and my "Take Control: Mac OS X Lexicon"
>on an ebook reader. Even on a 170 DPI screen, it's impossible.
Indeed, most ebook readers do a horrible job with PDF, when they
support it at all. However, that's not necessarily an indictment of
PDF so much as a design issue. If a PDF were designed for that little
screen, it would probably look pretty good (within the slow redraw
constraints and limited grayscale capabilities of the E-Ink screens).
We're investigating PDF options that might help, such as tagging to
make the text reflowable, but it's hard going.
>PDF is looking more and more like a dead end. I think it's time to
>seriously consider abandoning it, before you find yourself completely
>locked into a format that can't be repurposed. Well, actually, that's
>exactly where you are now, isn't it? OK, let's say instead "Before
>you find the market passing you by." Given the runaway success of
>Kindle, that event looks to be imminent.
If the Kindle were a runaway success, I'd expect Amazon to be
trumpeting sales figures to the high heavens. And although I heard it
mentioned a few times at the O'Reilly Tools of Change for Publishing
conference in February, Amazon had no presence there, which seems
like a strange step if they wanted to evangelize publishers into
supporting it.
The advantage of PDF, and the reason we chose it 4 years ago, is that
it provides a graphically rich file format that is well-supported on
the most common reading platforms that existed at the time: the
Macintosh and Windows-based PCs. That still remains true - most
screen reading is done on computers. And most ebook sales across the
industry, as far as I'm aware, are happening in PDF format because
it's something that publishing tools can create well, and in an
automated fashion.
Also, you're avoiding the fact that PDF is merely an output format
for us. Our ebooks are written and edited in Microsoft Word format,
so authors and editors can work with the text directly within the
layout, so we have change tracking and commenting during editing, so
authors can work in a familiar environment they already own (as
opposed to, say, InCopy), and so we don't have to wait for or pay for
an additional production step to lay out each ebook in InDesign.
The real problem here is that to create a scenario where we can
easily output XML or HTML, we need to change our publishing system
entirely, probably to InDesign. That's highly non-trivial, and it's
not a step we can even start to consider unless there's an obvious
business case for why we need to do it. The Kindle has shown no
evidence of being that reason, nor has the Sony Ebook Reader. The
iPhone/iPod touch might be, but we'd certainly prefer to be able to
stick with our current system, which is extremely functional, even
still.
>I'm delighted to hear that you're at least considering putting
>TidBITS books on ebook readers. But while you're waiting for Apple to
>answer your prayers, why don't you upload that same Take Control
>library to Amazon in Kindle format? It's a safe bet that Amazon is
>already a much larger marketplace for ebooks than the iTunes Store
>will be in the foreseeable future. You could cash in on that *right
>now*... and then hit the ground running *if and when* Apple moves
>into ebook readers.
Well, there's a problem with that, and I have looked into it in some
detail. The problem is that the Kindle requires that ebooks be in a
specific subset of HTML that's astonishingly limited - barely past
HTML 2.0, if that.
It's not unthinkable that our source Word files could be converted to
HTML, since Word does export HTML that renders acceptably in modern
Web browsers, but the Kindle can't handle that HTML. And Word's HTML,
while OK for viewing in a browser, is mind-bogglingly complex, and
has resisted my grep-based efforts to convert to something the Kindle
can deal with in an automated fashion.
It turns out that most book conversions to XML (or to HTML, when that
happens) are actually being done largely by hand in India. The
technologist in me is offended at the concept of hand conversions
between formats, but I haven't been able to come up with anything
better yet.
>Put 'em in the Sony Connect ebook store too, while you're at it. The
>Sony PRS-505 Reader has all the "hardware design and user interface
>chops" that are missing from Kindle; in fact, it's a very Apple-like
>device: slim, elegant, easy to use. That's another existing ebook
>reader market you could be selling into right now, rather than
>waiting for Apple to get off the dime.
See, now there's a perfect example. The Sony Connect music store is
closing at the end of this month. The iTunes Store has sold 4 billion
tracks. Which would you want to be in?
(And if you know how one publishes a book in the Sony Connect ebook
store, do let me know; I couldn't find a thing on the Web about how
to get started with the process. At least Amazon made that relatively
obvious.)
>Adam, I get the strong impression that what you're saying in this
>open letter boils down to "We love the ebook reader idea... but we
>won't enter this market unless it's based on an Apple platform." Can
>TidBITS really afford to be that parochial?
Well, sticking with Apple has kept us going for nearly 18 years, and
the vast majority of our readers rely largely on Apple products, so
it doesn't seem like a mistake from where I'm sitting. If Apple were
to do this in the way that makes sense to me, supporting at least all
iPhones and iPod touches, plus any new devices they could, they'd
become the largest ebook reader manufacturer and ebook seller by far
overnight.
cheers... -Adam
--
Look into my head; follow me on Twitter.
http://twitter.com/adamengst
_____________________________________________________________________
Adam C. Engst: I publish TidBITS and Take Control, write books,
ace

tidbits.com and make useful introductions in the Mac industry.
My work:
http://www.tidbits.com/ and
http://www.takecontrolbooks.com/