Writing about Tiger

I begin work on my Mac OS X book revision.

I started working on my Tiger book this week.

So far, I have three of the 21 chapters done. I skipped Chapter 1, which is about installation and configuration. I always do that one last. Instead, I dove right into the Finder chapters: Finder Basics, File Management, Advanced Finder Techniques.

I added some new information to the File Management chapter about a new and undocumented feature called burnable folders. This was a challenge. Although I could figure out how to use this feature and write sufficiently about it, there wasn’t a single mention of it anywhere in online help or Apple’s Tiger Web pages.

What burns me up about this is that although I couldn’t find any official documentation about the feature, there was an article, with screen shots, on someone else’s Web site. Why does that burn me up? Because I had to sign a nondisclosure and swear up and down that I wouldn’t share anything about Tiger — especially screen shots — with anyone until the software was released. Technically, if my husband looks over my shoulder while I’m writing, I’d be in violation of this agreement. So that prevents me from giving my readers a sneak preview of the software and getting them all fired up for what’s to come. Yet someone else can publish articles on the Web, for the world to see, without getting in trouble. Does that sound fair?

Anyway, about burnable folders, to make matters worse, since I’m working with pre-release software, the feature isn’t perfected yet and is a bit buggy. Or perhaps it just set up conflicts with my screen shot software. In any case, my eMac was acting up and had to be restarted periodically. So it took me the better part of an afternoon to write two new pages and rewrite two others.

The Advanced Finder Techniques chapter was completely reworked. I pulled a lot of material out of this chapter to make a new chapter (Chapter 6) about customizing the Finder. This required complete renumbering of all figures throughout the chapter. A tedious task, but someone has to do it.

Next week, I continue writing with a brand new chapter about Apple’s new Spotlight and Smart Folders features. I hope to be able to knock that one off in two days.

Do It Yourself Layout

How and why I lay out my own books.

I do layout for most of my books. That means I submit finished pages to my editors. What they see on the page is what the book will look like when printed.

I write the book as I lay it out, in Adobe InDesign CS. InDesign is an incredibly powerful page layout program, but I use only a fraction of its features. I start with a template that has all the elements of page design. I use text boxes to position text in the appropriate place. I actually type the text right into the text box — I don’t use InDesign’s separate text editing window. I use styles for paragraphs and characters. I’ve even taken advantage of InDesign’s nested styles to automatically format text like numbers in numbered steps and bullets in bulleted lists. That saves a lot of time and ensures consistent formatting.

I create figures using screenshot software on my “test mule” computer. That’s the computer I run the software on while I write about it on my production computer. My Macintosh test mule is an eMac; my Windows test mule is a Dell Dimension PC. Both are networked to my production computer, a dual processor Macintosh G5. I pull the screenshots over to the G5, open them with Photoshop, and run an action on them to convert them to grayscale (or CMYK, depending on the book) and save them as uncompressed Macintosh-format TIFF files with 72 dpi resolution. Then I literally drag the image icons from a Finder window to the InDesign document. I downsize them to fit, which also enhances resolution, and drag them into position. Then I use InDesign’s library feature to insert a pre-formatted caption, which I fill in for each screen shot. This is probably the most time-consuming part of layout. No, that’s not true. Callouts — those little lines that run from labels to exact positions on a screen shot — take far more time to do. I have InDesign library elements for other items, too, like thumbtabs (for my Visual QuickStart Guides) and callout lines (for my Visual QuickPro Guides).

I write each book a chapter at a time. When a chapter is finished, I create a PDF format file of its pages that includes printers marks such as registration marks and cut marks. (Can’t remember the exact names of these things.) I then upload the PDF file to an FTP site where my copy editor and production editor can download them. There’s a workflow over at my publisher’s place that varies depending on the editors assigned. What I see at the end of the process is printed pages that have been marked up by both editors. I get them a few chapters at a time via UPS. I normally take care of the edits in the afternoon, after submitting a chapter for the day. (I try to do a chapter a day for revisions and a chapter every two days for new titles.)

I review the edits and make about 98% of the changes that are requested. Most changes are of a typographical nature — I have a habit of repeating words and leaving characters out of words — but some are of a layout nature — rewrapping text to prevent widows, moving a callout up two points to improve spacing, etc. And of course, there are always a few grammatical errors that need fixing. (I wasn’t an English major!) Any time I don’t make a requested change, I note the reason why on the marked up pages. I don’t ignore a change without good reason. Then I print the manuscript and send it back to the editor with the markups. If the production editor is a freelancer, I usually have to print up a second copy for him or her. It usually takes about 30 minutes to turn around edits for a chapter, so I can knock them off quickly. The final InDesign and TIFF files get FTPed to the production editor or, if he or she requests it, put on a CD. The production editor sometimes puts a few finishing touches on the final files.

When I finalize a chapter, I also create a finalized PDF and upload it to the FTP site for the indexer. Sometimes, if the book is on a tight deadline, the indexer will work on draft pages. This is usually pretty safe, especially for revisions, since pages rarely have significant changes from draft to final. When the indexer has indexed all chapters, she submits a Word or RTF file to me via e-mail. I then pour the index into an Index template and reformat it to fit the number of pages allotted. Sometimes that means making the font size really small — my last book had 7.2/8.2 font for index entries. Other times, that means making font size and leading normal but increasing the spacing between paragraphs or above headings. The book’s total page count has to be evenly divisible by 8, and it’s my job to make sure I submit exactly the right number of pages. Fortunately, Peachpit is not normally page count driven. A book can be as long or as short as it needs to be — as long as the total number of pages is divisible by 8. That’s great for me, because I can write just what I need to.

Generally speaking, it takes about a week from the time I finish all chapters in my first draft to the time the final files and index are ready to send to the printer. It then takes about three weeks from the time the files get to the printer to the time I see a printed copy of the book. Add another week for copies to get to stores and you have a 4-week turnaround from finished manuscript to book available in stores. Obviously, this is the greatest benefit of doing my own layout. Let’s face it, computer how-to books are extremely time sensitive. To get a book out quickly, you have to prepare it quickly. I have a knack for doing my job quickly and since I don’t have to depend on someone else at the publisher to do time-consuming layout, each book can be turned around very quickly.

There are other benefits to doing my own layout. It’s great for me because I have a lot more control over my work and can write in a way that takes advantage of the book’s layout. I also get a bit higher royalty rate to compensate me for my additional work and the cost of labor I’ve saved my publisher. It’s great for my editors because they can see the “final” product as they are editing. So if the layout isn’t quite right — for example, a figure would be better on one page than another or could be improved with a callout — they can tell me and I can fix it as part of the editing process. Otherwise, the book would have to go through multiple editing processes, each of them handled by someone different who may or may not care about the quality of the book. I’m the author of my books and I care about all of them, so I do my absolute best to make sure they’re something I’d be proud to have my name on.

Peachpit, to my knowledge, is the only publisher that allows authors to handle what they call “packaging.” And they won’t let all authors do it. You have to prove that you have the ability to handle layout to their standards. I’ve been doing layout for my own books since 1996 and have produced over 40 titles for them, so I’m proven.

Other publishers don’t work this way at all. In fact, they are completely opposed to the suggestion that an author layout out the book. The reason: they are worried about losing control over the book’s contents. They don’t seem to understand that they do get final possession of the manuscript’s files and can make any changes they like before sending the manuscript to the printer.

One of my other publishers, in fact, has an extremely complex production process. First the author writes the manuscript using a Word template that has macros built in for formatting. Some of the macros work, others don’t. The author is required to insert special codes in the manuscript to signal certain types of styles. Meanwhile, the author creates screenshots, which are supposed to be submitted as full screen images. The author is supposed to print each one and mark where the image should be cropped. (I refuse to do that because it wastes time and paper and relies on a production person to get the cropping right. I send cropped images and I don’t even bother printing them anymore. Nobody complains. Frankly, I think they’re relieved that I’ve spared them this extra work.) From the author, the Word file and images go to a copy editor and a technical editor. The copy editor uses Word’s change tracking feature to mark up the manuscript and insert all the codes the author has either neglected to insert or inserted wrong. The Word file then goes back to the author for review. The author further messes up the file by using the change tracking feature to accept or reject changes. The author also gets comments from the technical editor and changes the Word file to make necessary corrections. A production editor gets it next and incorporates the copy editor and author changes to finalize the file. Then it goes into production, where it’s converted into a Ventura Publishing file (I kid you not) with the images inserted. The images are usually in-line images, meaning that text doesn’t wrap around them. It also means that the images might not appear where the author thinks they should. (But that doesn’t seem to matter much.) The author gets “proofs” of these pages, in print, and is required to mark them up and send them back to the publisher. About 10% of the author’s suggestions are incorporated into the final pages. To be fair, any change that corrects an error goes in but any change that tweaks the layout is basically ignored. The book eventually makes it to the printer where it is printed and sent out. Time elapsed from completion of first draft to printed copies: 8 to 12 weeks.

Is the quality of a book better when a professional publishing staff takes it from manuscript draft to printed book than when an author takes it most of the way? I don’t think so. But I also think that quality isn’t the most important aspect of book production to some publishers. But that’s a topic for another blog entry.

Books of 2004

I bring readers up to date with the titles I churned out over the past year.

I realized, in writing my last blog entry, that the last book I’d mentioned finishing on these pages was my Mac OS X 10.3 Panther: Visual QuickStart Guide last October. Don’t think for a minute that I’ve been idle since then.

It’s been just over a year and, believe it or not, I had to consult a list of the titles I’d put out to see just what I’d been up to. I just couldn’t remember them all. Here they are:

Microsoft Office Excel 2003 for Windows: Visual QuickStart Guide was the most recent revision of my Excel for Windows book. Not much new in the way of content because there’s not much that Microsoft can already add to that feature-packed program. It came out in December 2003.

QuickBooks Pro 6 for Macintosh: Visual QuickStart Guide was a brand new title for me (and Peachpit). I’d proposed it early in the year, when I was looking for work and it took several months for them to say yes and come up with a contract. By that time, I had other work lined up. (Feast or famine.) The book underwent a lot of content changes as I wrote. For example, it was originally going to include payroll coverage, but since payroll is done with a separate program bundled into QuickBooks and the future of the bundling was questionable, we decided to drop it. (Frankly, I think payroll is so confusing that a whole book could be written about it, but don’t think I’m volunteering.) The book came out in May 2004 and is doing surprisingly well. So well, in fact, that Peachpit wants me to revise it for the recently-released new edition.

Quicken Premier 2005: The Official Guide is the sixth revision to my original Quicken Official Guide. It was finished in June 2004 and published in August 2004.

Creating Resumes, Letters, Business Cards, and Flyers in Word: Visual QuickProject Guide was a brand new title in Peachpit’s brand new Visual QuickProject Guide series. The series is great for beginners or people with computer phobias because it shows every single step in a process, with callout lines and numbered instructions. It makes a VQS look like a technical guide for MBAs. And it’s in full color! It’s 160 pages long and costs only $12.99. A great deal. The only thing I don’t like about it is the title — it’s way too long! It came out in September 2004.

Creating Spreadsheets and Charts in Excel: Visual QuickProject Guide is another brand new book for me. This one offers the basics of working with Excel spreadsheets and charts in a format anyone can understand. It’s eight chapters took me eight days to write and lay out. (That’s not the record. My record is a 350-page book that I knocked off in 10 days back in 1993. Of course, I didn’t do layout for that title.) I think it’s a great book and I’m extremely pleased with the way it came out. Like the Word book, it’s cross-platform. It came out in October 2004.

Microsoft Word 2004 for Macintosh: Visual QuickStart Guide is the latest revision to my Word for Macintosh book. It has a bunch of new stuff inserted throughout the book and a brand new chapter covering Word’s new Notebook Layout view feature. I finished it two days ago and it’ll go to the printer today. I expect to see it by the first week in December and, of course, it’ll be at Macworld Expo.

So in the course of a year, December to November, I finished six books. Of these, three were revisions and three were brand new titles. (That’s not a record. My record is 10, set a number of years ago, and I hope I never do that again. Talk about burnout!)

In addition to writing all those books, I also managed the Wickenburg Airport’s FBO (for a short time, anyway), did helicopter tours in the area, got a part-time job flying at the Grand Canyon, and wrote a handful of articles. So anyone who says I have an easy life obviously doesn’t have the big picture.

I’m not complaining — certainly not! I usually take a week or two off between books and spend that time catching up on things like bills, surfing the ‘Net, shopping, and writing in my blog. If I had a helicopter, I’d be flying, but I’m between ships right now and grounded. This week, I’m trying to write three or four articles that I owe various editors. I knocked off one yesterday and started a second one. I’ll finish that and write at least one more today. Tomorrow, my brother, his wife, and my sister are coming in for a week, and my mother and stepfather are showing up on Tuesday for a week, so I’ll spend time with them.

Then it’s back to the salt mines for me. Mac OS X 10.4 Tiger is on its way and I have to revise the existing book to turn it into Mac OS X 10.4 Tiger: Visual QuickStart Guide. I always have the first Mac OS book out in stores and I’m not about to ruin my record this year.

After that, it looks like a QuickBooks revision, but if I’m lucky, they’ll let me write one or two more Visual QuickProject Guides. I proposed a bunch of titles, and they finally seemed to like one of them. Cross your fingers for me. I’m also writing an eBook about iBlog 2.0 for Spiderworks. I’ll probably finish that sometime in December, if I can find time for it between my work on the Tiger book. I’m also working on a book about the Grand Canyon with a photographer and hope to have that ready for publication in May. It’ll be nice to have a book that doesn’t need revising every one or two years. (The Canyon doesn’t change much.) And I’ll always be writing articles. Informit.com likes my work and I like writing for them. FileMaker Advisor also wants me to write for them, but I’m always having trouble coming up with fresh ideas for them, so we’ll see how I do.

That’s it in a nutshell: the past year and the next four to six months. Busy, busy, busy.

Another Chapter Done

I revise book number 59 or 60 — I’ve lost count again.

These days, I’m hard at work on a revision to my Microsoft Word for Macintosh book. Officially titled Microsoft Word 2004 for Macintosh: Visual QuickStart Guide, the book covers the latest and greatest version of Word for Macintosh.

The book I’m revising (which covers Word v. X) is only about 300 pages long. It has a companion book that covers more advanced features. For this edition, I’m rolling the two books into one big fat book. That’s what I did earlier in the year for the Windows version of the book (which covers Word 2003). That book is 450+ pages long.

Revisions are not as easy as they sound. Books in the Visual QuickStart Guide series are extremely screenshot-intensive, with 3-6 images per page (on average). The tiniest little change in Word’s interface requires that any screenshot of that interface element must be redone. Since Microsoft changed the way the ruler looks, for example, any screenshot that includes the ruler — basically any shot of a screenful of text — must be redone. Rather than try to determine what elements have changed and run the risk of missing something, I just redo every single screenshot in the book.

Of course, not only do I write the book, but I lay out its pages using InDesign software. When I’m done with a chapter, I create a PDF and e-mail it to my copy and production editors. They print out the pages, mark them up, and mail them back to me. I then make changes as they requested, finalize the files, and send them to the production person on CD or via FTP. The book is in print 3-4 weeks later. The whole process, from my start to book in stores usually takes 6 to 8 weeks. But as soon as I’m finished with one book and have taken a week or two off to clear my head, I’m starting work on the next book.

I’ve got revisions down to a science. For this book, I’m starting with the InDesign files for the Windows version of the book, which has most of the content I need, organized in the right order. I’ve printed out an outline of that book’s contents with a few Macintosh-only features inserted in the appropriate areas. For example, Chapter 13 will be a brand new chapter covering Word’s NoteBook Layout View feature. Then I open a chapter file and go through it, page by page. I edit the text for correct Mac OS terminology and instructions. I replace the screenshots, removing some completely while adding new ones. I modify all the figure references and caption numbers as needed. (This is, by far, the most tedious part of the revision job.) When I’m done, I have a finished chapter, all ready for review and edit.

I try to knock off a chapter a day. Sometimes, when the chapter is short, that’s easy. Yesterday’s chapter was only 20 pages. But Wednesday’s chapter was 28 pages. That may not seem like a big difference, but it is. This will be a 20-chapter book, so I’ll have it done in 20 working days. If I get two short chapters in a row, I’ll try to do them both in one day to speed things up.

The deadline for this book is roughly around Thanksgiving time. I’d like to get it done sooner, since I have out-of-town guests coming in that week. More important, my Mac OS X book is due for revision shortly. That book takes priority over all others. If it’s ready for revision before I’m done with Word, Word will go on the back burner until I’m done.

I wrote somewhere that I sometimes feel like a machine. When I work on revisions like this one, I do. But I’m a well-oiled machine with the parts worn in just right to get the job done smoothly.

On Being a Professional Writer

Some thoughts on writing for a living.

I make my living as a writer. And I make a very good living.

When people ask me what I do, I tell them I’m a writer. The next question is usually, “Oh, have you had anything published?”

Hello? How can you make a living as a writer if you haven’t had anything published? After all, the money comes from the publishers. It doesn’t come out of thin air just because you spent time putting words on paper or in a word processor. Or in a blog, for that matter.

I’ve written 58 books since 1990. True, most of those books were revisions. Like my Mac OS books, which have been bestsellers since the very first edition. That was about Mac OS 8 back in 1998. I revised it for 8.5, 8.6, 9.0, 9.1, X, 10.1, 10.2, and 10.3. I’m going to start work on the 10.4 edition soon.

I learned very early on in this field that if I wanted to make a living as a writer, I had to write a lot and get it all published. So I learned to write my computer books extremely quickly, giving my publishers just what they wanted pretty darn close to the day they wanted it by. Publishers like that. They don’t want to work with prima donas who won’t do things their way. They don’t want to work with writers who can’t deliver on time. Because I met the needs of my publishers, they gave me a lot of assignments. I always had work to do. And since these books only last 12 to 18 months (on average), I needed to keep working. Even a bestseller doesn’t pay a dime when it’s out of date.

I had two bestsellers: the aforementioned Mac OS books and my Quicken books. The Mac OS books continue to do well. I’m extremely proud of the latest edition, which is over 600 pages long and full of great information. The next edition will be even better. The Quicken books aren’t doing as well these days. I think the market is saturated. I have other thoughts on this, but I’ve been advised to keep them to myself and I agree it’s probably a good idea.

Bestsellers are nice. They generate big checks. I wish I could have 10 bestsellers, all at the same time. Then maybe I’d have a little house on top of Howard Mesa instead of a camper with a pair of bad batteries.

If you’ve been reading these blogs, you know that I have a summer job as a pilot. It isn’t quite over yet, but it will be soon enough. Some people think I got the job because I needed the extra money. In all honesty, the job is a money sucker. The pay is terrible and I probably spend as much money commuting to work by helicopter as I earn each day. (But heck, it sure beats the 40-minute drive in the Jeep.) And every day I’m away from my office is a day I can’t work on a book. So I’m losing money when I’m flying. Good thing I enjoy doing it.

This summer, I worked a 7 days on/7 days off schedule. But I fiddled with that a bit and got it set up as 5 days on/9 days off for much of the summer. As a result, I was able to go home and work on books. I revised my Quicken book in June. I worked on my new Word Visual QuickProject Guide in July and August. And this month, I started my new Excel Visual QuickProject Guide. I have another Word book (a revision) and my Mac OS X book (a revision) lined up after these. So there’s plenty of work to do.

I also got some work writing articles for a Web site. I can write those when I’m away at my summer job. I use my laptop. They don’t pay as well as a book, but I can knock one off in a few hours. And it’s kind of nice to write about a bunch of different things rather than just one main thing.

There are lots of people out there who want to be writers. I’ve met many of them. I was even pretty good friends with one or two. But they just didn’t get it. They didn’t understand that if you want to write for a living, you must write what the publishers want so they’ll buy it. If the publishers don’t buy it, you won’t make any money on it.

And don’t talk to me about self publishing. I have a friend who went that route and still has a garage full of books. Five different titles! Self publishing is risky. There’s a huge cash outlay involved and if you don’t know how to market (or sell) your book, you’ll never make any of that money back.

Yes, the key word here is sell. Sell your writing, sell yourself.

If you do it well enough, you can have a very nice lifestyle. After all, it’s nice to be able to make your own hours, work in your pajamas, take vacation anytime you want. Those are the perks of being self-employed. But you have to work to earn those perks. Pay dues, so to speak.

What a disjointed blog entry this is! But sometimes it’s nice to write something that you don’t have to sell. I guess that’s what these blogs are all about.