Books

Take Control of Apple Mail

When I set out to write about Apple’s Mail application for the Take Control series, I had several long discussions with Adam and Tonya Engst about how to divide the material into chunks of the right size, since we generally aim for 50-page ebooks and we clearly had much more than 50 pages worth of content. But as I started writing, I quickly discovered that the subject matter didn’t lend itself to the kinds of divisions we had come up with. After several false starts, I gave up on splitting the information and just wrote it as one very long document, hoping that a logical way to split the text would emerge after the fact.

After a great deal of mulling over that manuscript, Tonya suggested that I could split off the portion about fighting spam (roughly 20 pages) and expand that into its own complete ebook. The rest of the material would then be reorganized into a second book. It took quite a bit of additional effort, but the final result was a $5, 59-page ebook called Take Control of Spam with Apple Mail and a $10, 89-page ebook called Take Control of Email with Apple Mail.

Now, after all that tedious splitting, the two pieces have been rejoined into a printed book from Peachpit called Take Control of Apple Mail. It’s a gorgeous book, in full color, and includes our trademark free updates—anyone who purchases the printed book is entitled to free downloads of any future editions of the PDF version we produce. Quite a deal.

The only problem was that the book was printed a few weeks too late to meet the reset deadlines for certain large retail book chains. So although you can find it on Amazon.com and in a few bookstores, most brick-and-mortar shops probably won’t carry it until after the first of the year, at which point its days may be numbered, depending on how dramatic the changes are to the version of Mail that ships with Tiger. (A complete rewrite of the book, for example, would be beyond the scope of the free updates.)

Still, it was very nice to get my name on the cover of yet another printed book with barely any extra effort.

Take Control of Upgrading in Dutch

My first ebook, Take Control of Upgrading to Panther, came out just over a year ago. It has sold incredibly well and received rave reviews; it’s also now available in printed form as part of Take Control of Panther: Volume 1. In addition, it’s the first one of my books to have been translated into other languages. The arrangement the publisher has is that any willing and able party may translate the text into their language of choice but with no money paid up front. The translated ebooks are sold at 150% of the cost of the English versions, so that author, translator, and publisher can all receive equal shares of the profits at the same rate as the original. In other words, a translation becomes worthwhile for the translator only if he or she does enough marketing, and sells enough copies, in the target country to justify the time spent.

The first translation to appear, back in February (four months after Panther’s release) was Japanese, of which a respectable (if not stunning) 181 copies have been sold so far. In June (release + eight months), a German translation appeared; it’s sold only 26 copies, meaning the translator received a paltry reward for his efforts. Amazingly, just last month—a full year after Panther came out—a Dutch translation was released. Total sold so far: 17.

As cool as it is to be able to say my work has been translated into three other languages, I really feel for these folks who have invested so much of their time for virtually no pay. And yet, the reason seems fairly obvious to me: by the time the German and Dutch translations had appeared, the vast majority of potential customers had undoubtedly already completed their upgrades to Panther, with no further need for a book to help them. As it is, I’m only selling about one or two copies a day of the English edition (down from hundreds a day in the first few weeks), because most Mac users who have not yet made the move to Panther are now more likely to wait for Tiger (Mac OS X 10.4), due out some time in the first half of 2005.

Computer books always have a relatively short shelf life, because the products they describe change so rapidly. Thus, any hopes of making significant money from a translation require that the work be done as rapidly as possible after the book’s release. There will of course be an English edition of Take Control of Upgrading to Tiger when the time comes, and though no one has said anything to me yet about translations of that book, I certainly hope that if they happen, they happen quickly. Not just for the sake of the translators, either, but for the sake of the readers!

Take Control of Panther, Volume 1

Yesterday I got my first sample copy of Take Control of Panther, Volume 1, a compilation of the first four Take Control ebooks. These should be appearing on the shelves of your favorite bookstore any day now. It’s nice once again to have my name on the cover of a (more or less) current printed book.

I wrote my portion of this book back in October of 2003, and though I’ve revised it several times since then, it seems kind of strange that it was nearly a full year before it appeared in printed form. Stranger still: I won’t see any money from this edition until January at the earliest, and possibly much later. That’s because of the odd way print publishers still work, even in the 21st century: royalties are computed quarterly (or, in some cases, biannually), but then the publisher generally has another full 90 days to actually send out a check. So in this case, since we’re just at the end of the third quarter, the publisher has until the end of December (i.e., 90 days from the end of Q3) to send out a check for whatever books were sold this month—less a certain percentage as a reserve against returns. The check will actually go to TidBITS, which will in turn send each of the contributors their cut. I don’t think very many copies will be sold in the next two weeks, so if I get a check in January it’s likely to be quite small. Maybe in April I’ll get a bigger check—just in time for the book to become obsolete as Apple releases Tiger!

Book Contracts

More than a year ago, I started working on a book about AppleScript Studio, having signed a contract with a certain publisher—let’s call them Publisher A—stipulating the amount of advance, royalties, schedules, and so on. After I turned in the first batch (maybe one-fifth of the book), the publisher said they’d had a change in their strategic direction and were no longer interested in publishing Mac programming books. So they dropped the project and my manuscript was orphaned.

My ever-diligent agent decided to shop around for a new publisher, and several—let’s call them Publishers B, C, and D—expressed interest. Publisher B made me an offer, but had a condition in the contract I couldn’t live with (more on this in a moment). Publisher C offered high royalties but a low advance (more on that, too, shortly). And then Publisher D offered a reasonable amount of money and a great contract, except for one tiny little phrase that I absolutely refused to agree to and they absolutely refused to change. Thus, after having gone through four publishers, the project is once again orphaned (for now, at least).

The problematic phrase in Publisher D’s contract (which was also one of the sticking points with Publisher B) basically indemnified the publisher against claims of breaches of my warranty that the material is original and free from copyright violations. In other words, it means that if someone were to sue them claiming that I violated a copyright, then even if the claim were completely unsubstantiated, even if I proved in court that I did nothing wrong, and even if the claim were in fact completely frivolous, I would still be responsible to pay the publisher’s legal fees for defending the suit. This cost would almost certainly be far more than I’d ever received for writing the book in the first place.

Although it’s extraordinarily unlikely that such a lawsuit would ever occur, clearly something of that sort must have happened at some point, or the publisher wouldn’t have been so adamant about leaving that language in. I know several other authors who reluctantly agreed to this language because refusing to do so would amount to a career-limiting move. But I said no, because I don’t think it’s ethical to hold an author financially responsible for actions over which he or she had no control whatsoever. Nor is it ethical for me to put my financial security at risk to protect a big company against unscrupulous litigants. I can warrant that my work is original, but I can’t agree to pay legal fees to fight off someone who has a random grudge against the publisher.

The real pity is that I truly like and respect the publishers and editors involved, it’s just that their lawyers are being intransigent and corporate policy dictates that no contract can be signed that the lawyers don’t OK.

Continue reading…