I've been getting fairly regular questions about publishing on Kindle so I finally decided to go ahead and publish my own Kindle ebook, just to be in a better position to respond. It turned out to be far more work than I'd hoped for a mediocre result, and a bit frustrating as well since the Amazon previewer doesn't test whether or not table of contents links are working. I asked a fellow publisher, Kim Greenblatt, to check it out for me since he owns a Kindle. That he needed to "dig it out" and charge it up suggests that it hasn't become is primary reading device:-)
The biggest problem I ran into was formatting tables. The reason it's a problem is that Kindle doesn't support HTML table tags. Since HTML doesn't support tabs or repeated spaces, my "fix" was to use underscore characters "_" and periods "." to try to line up the data, and then set the color to white. On the smaller tables it's not horrible with the default font, on the larger tables, the columns get pretty squiggly. There's also the issue with page breaks in the middle of tables, but rather than force page breaks for every table, I decided to repeat the column labels in the bottom row. The picture below is from the preview tool which apparently is a fair representation of the Kindle screen, from a large table that came out OK.
A glimpse of HTML to accomplish this:
The reason I left table tags in there was so that I would have some way of aligning the columns in my HTML editor as I was working. It would be funny if Kindle started recognizing HTML table formatting one day, and all of a sudden my tables got even screwier. The other main formatting notes for Kindle are that you have to put in an HTML anchor for the Table of Contents itself, in addition for the links and anchors to all of the chapters, if you want a clickable TOC. There's a guy who's started a Kindle formatting site where I found the name of the pagebreak tag, "mbp:pagebreak /" (goes inside less-than greater-than signs like all HTML tags) which given the "mbp" was probably developed for MobiPocket.
One of the reasons I didn't bother publishing any books on Kindle when it came out is the business model. The contract Amazon requires publishers to sign for Kindle is pretty out-there. I wouldn't have signed if not for the clause allowing either party to opt out on 60 days notice, though I probably should have checked with my lawyer as well. The royalty to the publisher is 35%, which means, of the five ways I sell my publishing title, I earn the least on the Kindle version by a factor of at least two. I set the list price at $9.95, the same price for which I sell my PDF e-book version direct. Amazon discounts the $9.95 Kindle version by 20%, so they are now the cheapest way somebody can legally acquire an ebook version of my publishing book, though you do have to pop $359 for a Kindle to save the two dollars. Since I earn around $7.50 per copy on the paperback sold through Amazon, each Kindle sale to somebody who would have bought the paperback otherwise will cut my net in half. For the time being, I don't think it will break my bank.
While it would be nice to earn a higher share as the publisher, I assume that Amazon is paying a hefty fee to the cellular operators who host their Whispernet, and for all I know they'll lose more than I make on every copy they sell. But I see Kindle as part of Amazon's grand plan to compel publishers to supply Amazon with electronic files for all their titles for Amazon to package and sell as they see fit. I'm not on-board with that future, but I decided to go ahead with this one Kindle version just to learn what it's all about. If anybody is interested in how Kindle e-books are selling, see the comments from Steve Windwalker on my earlier ramblings about Kindle sales ranks.
A side note, I just noticed that Google has me at #1 for searches on Publisher TV, so I think that justifies my summer of video reruns!