Tag Archives: Apple

About Style Guides…and a Tip for Writers

Posted on by
10

A writer’s cheat sheet — and how I maintain mine.

One of the challenges facing writers — especially tech writers — is maintaining consistency and proper usage of words and phrases that describe the things we write about. Is it toolbar, tool bar, ToolBar, or Tool bar? Is it Fonts panel, Font panel, Font window, or Fonts Pane? Is it iBookstore or iBookStore? Is it inspector or Inspector?

This might seem trivial to most folks, but for writers and editors, it’s very important. Inconsistent or incorrect use of established terms is one of the things that mark the work of an amateur. Professional writers do everything in their power to get things like this right — and editors help.

Style Guides

Chicago Manual of StyleStyle guides help, too. A style guide is a collection of words or phrases that might be used in a work, all presented as they should be in writing. You may have heard of some of the more famous style guides, including The Chicago Manual of Style and The Associated Press Stylebook. These are style guide books published for professionals who write about a wide range of topics.

But there are also style guides for more narrow topics. Apple, for example, publishes a 244-page document called the Apple Publications Style Guide. This is one of the books I turn to when I write my Mac OS books and articles. Written for developers and Apple’s in-house documentation teams, it lists the right and wrong ways to use hundreds of words, product names, and phrases. Not only does this include a correct list of all Apple trademarks, but it goes into tiny details. For example, did you know that you can “click the icon” but you can’t “click on the icon”? Page 37 of the latest (2009) edition is pretty specific on that point.

Microsoft Outlook 2011Individual publishers also have style guides. For example, when I wrote Microsoft Outlook for Mac 2011 Step-by-Step for Microsoft Press, I was handed not one but two style guides. They covered all of the product names and program terms I might use, as well as rules about usage. For example, I wasn’t allowed to write a sentence like this: “Outlook enables you to send and read email.” Why? Well, the word enables (in that kind of usage) was verboten. (The average reader has no idea what writers deal with when writing technical books for well-established publishers.)

My Style Guide Needs

Microsoft Outlook 2011Although I never used to have trouble remembering the proper forms and usages of the words and phrases I included in my books, as I’m aging — and as my life becomes more complex — I’m having trouble remembering the little things. So this past summer, when I worked on Mac OS X Lion: Visual QuickStart Guide for Peachpit Press, I developed and maintained my own style guide for the book.

The trick was to put the style guide in a place where it was easy to consult as I worked. I wrote (and laid out) the book on my old 24-inch iMac. I was living in my RV at the time, comfortably parked at an RV park with full utilities, but my workspace wasn’t large enough for the luxurious dual 24-inch monitor setup I have in my home office. I experimented with keeping the list of words and phrases in a Word document file, but the amount of overhead — Word running all the time, big window with all the trimmings, etc. — made it an awkward solution. Ditto for Evernote. All I needed was a tiny window where I could list the words I needed to use — these applications made maintaining and consulting such a list multiple times throughout the day a real chore.

The Solution: Stickies?

Stickies IconI stumbled onto the solution while writing the book. One of the apps that comes with Mac OS X is Stickies. This is an app whose sole purpose is to put virtual sticky notes up on your screen.

I never liked the app. I thought it was kind of dumb. After all, who would use an app to put a sticky note onscreen when you can just put a real sticky note on your screen?

But then I realized that the tiny windows Stickies creates were perfect for the simple lists I needed to consult. I could easily fit them on my screen, beyond the area I needed to work with InDesign.

Style Guide in StickiesAnd so I began creating and maintaining my style guides in Stickies.

And I continue to do so today.

There are a lot of benefits to using Stickies as a solution for this problem:

  • The contents of Sticky Notes are saved, even if you quit the application.
  • Stickies are easily modified and updated.
  • Stickies supports formatting, so if I want to remind myself about a word or phrase that should never be used, I can format it as strikethru text.
  • Stickies can be exported as plain text, so I could, theoretically, save a style guide list before closing the Stickies window when the book is done.
  • Stickies take up very little room onscreen.
  • All active Stickies notes open automatically when you open the app.
  • It’s easy to set up my computer so Stickies automatically opens at startup.

Sounds good, no?

For me, it’s a win-win. I get a solution to my problem. But what I also get is a reason to use a silly little free app like Stickies.

My Experiences (So Far) as a Self-Publisher

Posted on by
4

Making it up as I go along.

I’m in the middle of my third self-publishing project since October and, of the three projects, this is the most challenging. But what’s more interesting, perhaps, is what I’ve experienced and learned along the way.

Project One: The Test


This is actually the revised cover for this book; the first one was just too awful.

The first project, Making Movies: A Guide for Serious Amateurs, went remarkably well, despite the twists and turns along the way. From the start, I’d wanted to publish the book in both ebook and print formats. I built an InDesign CS3 template and used it to lay out the book. The text and illustrations were already written; they’d been published online and I got rights back for them. I struggled a bit to create the epub and Kindle mobi formats I needed to publish the ebooks on the iBookstore, Amazon.com, and BN.com, but with the help of an excellent Lynda.com course by Anne-Marie Concepcion, I succeeded.

I took a wrong turn with the print edition of that book. For some reason, I thought MagCloud would provide a good solution. MagCloud is a print on demand (POD) printer which also sells through its website. The quality of MagCloud’s work is excellent — they print in full color and the work really does look good. But they’re also terribly expensive. My 64-page book cost 20¢ per page to produce, making it far too costly for its size. It would not be possible to sell at a retail price that included a cut for me. And, frankly, the book that resulted didn’t have the kind of look and feel I wanted.

Clearly, I had to either give up on the idea of printing the book or find another POD printer.

So the first book, which was done as a sort of proof of concept to see if I could actually get a self-published title out there, was a limited success.

Finding a New POD Printer

I had already done some research on POD printers. I did not want to go with Amazon’s CreateSpace service because it was acting as a publisher instead of a printer.

There’s an important distinction there:

  • A publisher pays an author a royalty percentage on every book sold — even if the author buys the book.
  • A printer charges the publisher a fee for each book printed; the publisher earns money based on the difference between the book’s selling price and the amount it cost to print.

I felt that the CreateSpace percentage was not very generous; they were obviously set up for self-publishers who needed a lot of help with manuscript preparation. I didn’t need help. I’ve been preparing camera-ready book pages since my first Visual QuickStart Guide back in 1995.

CreateSpace also offered a free ISBN for those who didn’t have them. That’s a huge stumbling block for many self-publishers. Apparently the prices for ISBNs have risen to cash in on the self-publishing craze. Fortunately, I set up my publishing company, Flying M Productions (formerly Giles Road Press) back in 1994 and have all the ISBNs I need. So that didn’t attract me to CreateSpace, either.

Finally, I just wasn’t willing to jump into bed with Amazon.com — unless I had to.

Lulu wasn’t an option. Too costly and I’d heard rumors that Amazon.com wouldn’t sell Lulu books. (Wish I could remember where I’d heard that so I could link to source for you.)

I wanted a more professional-level POD printer, one that worked with real publishers and not the average self-publisher. What I wound up with was Lightning Source. This is a real printer, one that assumes you know what the hell you’re doing. Best of all, they’re part of Ingram, the company that catalogs books for resellers and libraries. Publishing with them would automatically get my book listed for sale in all retail outlets. They had a great deal of flexibility with book sizes and styles, from small to large, from softcover to hardcover, from black and white to full color.

And their prices were reasonable.

As a test, I redid my Making Movies book as a black and white title, redesigned the cover, and sent it in. The proof came back looking great and the book cost about 1/4 what it did through MagCloud. I was very happy. I’d found my POD printer.

The Logo

I had developed a series of books — Maria’s Guides — and I felt that I needed branding to go with it. So I started looking for a designer to come up with logo.

I already blogged about my Elance nightmare. My advice: don’t waste your time.

A friend of mine, learning of the problem I had with Elance, mentioned on a list she subscribes to that I was looking for a designer. I was contacted by one. I looked at his Web site. I liked what I saw. We chatted back and forth. We came up with a budget. I signed a contract. I paid him 1/3 up front. And then the trouble began.

He’d spend days laboring over what should be a simple task, like choosing a font I liked. I loaded up a bunch of fonts, picked about 10, and sent him samples in a PDF. He then proceeded to make sample “word marks” using four fonts I didn’t have. I liked only two of them; buying those fonts would have added another $150 to the project budget. I told him to pick one of my fonts and that I’d send him the typefaces to work with. He did so, grudgingly. Two weeks gone.

Then it was time to come up with the graphics to go with the word mark. No matter what I suggested, he pushed back, telling me I was wrong. I was getting pissed off very quickly. Finally, I emailed him, told him to keep my 1/3 deposit, and to forget the project. I never heard from him again. I’m beginning to think that’s how he earns a living: 1/3 of a job at a time.

Maria's Guides LogoIn the end, I took one of the fonts I liked and threw together a simple graphic word mark. It would have to do for now.

My Deal with the Devil

I guess it was around Christmas time that Amazon announced a new program for its customers. If you were an Amazon prime member and you owned a Kindle (not another device with the Kindle app), you could borrow ebooks for free.

This freaked out a lot of authors and publishers — at least at first. After all, if people could read our books for free, how would we sell books and make money?

It soon became clear that only a limited number of publishers would allow Amazon to use their titles this way. My publishers were not among those participating. Amazon had obviously used this well-publicized offer to get more people to buy Kindles.

Of course, when publishers made it clear that they weren’t interested because there wasn’t any money in it, Amazon stepped up to the plate and created the Kindle Direct Publishing (KDP) Select program. They’d put $500,000 in a special account each month. Publishers that put titles into the KDP Select program and allowed Amazon Prime members to borrow them for free would get a cut of this big pie based on the percentage of borrows their books got. So suppose there were 1000 borrows during the month and a publisher’s book accounted for 16 of them. The publisher would get 16/1000th of the $500,000. Of course, the numbers would be much bigger than that and the percentages much lower. But the potential for sales was there.

Of course, there was a catch: you’d have to give Amazon an exclusive on ebook sales. That means it could not be sold as an ebook anywhere else. And you’d have to commit for three full months.

A friend of mine who self-published the novel Soléa, decided to give this a try. Since my book sales weren’t exactly stupendous, I figured what the hell? I’ll try, too.

So I took the book off the iBookstore and BN.com. And I turned off the PDF ebook option on MagCloud. And I enrolled Making Movies into the KDP Select program.

That’s when things started getting weird on my sales reports. The report would show sales with an average selling price of 9¢ per copy. (I’d priced the book at $3.99.) When I contacted Amazon about that, they said it was due to price matching. I responded that (1) they had an exclusive on the title, so there was no one to match with and (2) the book had been (and would again be) available at the same price everywhere; no one discounted it. I’m still waiting for an update on that.

And then there was the positive sales with the negative royalties. WTF?

Oh, and about Amazon’s royalty percentage…the 70% is only for sales in 6 countries that, for some reason, have favored status. If you sell to any of the other countries in the world, your rate drops to 35%. I’m still trying to figure out how they can justify that.

Needless to say, when the 3 months is up, my book will be yanked out of KDP Select so I can get it back in the iBookstore and BN.com. And no, none of the other titles will ever be part of KDP Select.

Project Two: Fine-Tuning the Process


I fine-tuned the cover design to make the book name larger.

My second project, Sorting Excel Data: The Basics & Beyond, went more smoothly. Encouraged by what I’d read about InDesign CS5.5 and its ebook publishing features, I upgraded. I ported my InDesign template to the new version, fine-tuned it, and wrote a 114-page book with dozens of illustrations.

The writing took about four days and went very smoothly. I felt good about the template design, especially since I watched the CS5.5 version of Anne-Marie’s Lynda.com video and adjusted my template to take advantage of new features.

Once the InDesign file was done — including title page, copyright page, table of contents, and index, I was ready to publish. I budgeted two days: one for the print edition file submission and one for the ebook file submissions to Amazon.com (Kindle mobi), Apple iBookstore (iBooks epub), and BN.com (NOOK epub).

I had the print edition’s files, including the cover, submitted before noon. After lunch, I knocked off the three other submissions. It went that quickly.

The iBooks edition was available first. It appeared in the iBookstore less than 2 hours after submission. The Kindle version appeared the next day. The NOOK version appeared the day after that.

I got my proof from Lightning Source a week later. I approved it the same day.

At this point, I felt that I had the process down to a science. Only a bit more fine-tuning and it would be perfect.

Project Three: The Challenge

I knew as soon as I heard about iBooks Author that I wanted to do a book about it. I downloaded the software the same day. I learned it over the next two days.

I spoke to one of my publishers about doing a book. They were interested — at first. Then they got spooked about the EULA that everyone is whining about; I addressed some of those issues in this blog post. By the time they confirmed that they weren’t going to do a book about it, I was already 1/4 into my own book. You see, I never really thought we could come to an agreement on the book, so I’d started writing it for Maria’s Guides.

This is going to be a much longer book — likely 200 pages. I’m about 1/3 finished now. Although I’m trying to stick to the basics, I don’t want to disappoint readers by leaving important information out. So it will be quite a complete guide.

I’m thinking of changing the dimensions of the printed book to bring it more in line with trade paperback titles I’ve written in the past. This won’t affect my ebook editions, however. It won’t even delay them; they’ll go out first — likely sometime next week.

There will be a “multi-touch” version of the book available for iBooks readers. That’ll have a separate ISBN and likely more multimedia content. I’ll do that after the print edition goes to the printer.

Motivation…and Uncertainty

The real challenge, however, is motivation. As I’ve aged, I’ve developed a remarkably short attention span. I get bored with any project that takes more than a week or so to complete. Normally, there’s an editor out there, waiting for the next chapter. This time, there isn’t. It’s just me. I’m the author, the editor, and production person, and the publisher.

No one — except me — will know if I slack off and put this project aside.

But the worst part about it is the complete uncertainty. When I write for another publisher, I get an advance on royalties. If the book doesn’t sell well, they don’t take that advance away. In other words, I’m compensated for my work no matter what.

Not so with self-publishing. You only get paid when your work sells.

So I could be working my ass off on a book that no one will buy. A book I’ll never make money on.

It’s a terrible gamble, one that nags at me. In the back of my mind, I’m constantly wondering if I’m wasting my time.

But to help prevent me from slacking off, I’ve publicly announced the book — not only here but on a variety of other places. I’ve had potential readers contact me, telling me that they’re waiting. They’re motivating me to finish.

So I’ll finish.

And maybe in a few weeks or months, I’ll blog an update to this story to let everyone know what else I’ve learned.

iBooks Author and Apple’s “Evil” EULA

Posted on by
6

My response to the negative commentary.

iBooks Author IconI need to start by saying how surprised I am at the negative opinions regarding Apple’s EULA for its free app, iBooks Author (iBA). In general, the concerns can be broken down into two main areas:

  • If you plan to sell a book created with iBooks Author, you can only sell it through Apple’s iBookstore. Apparently, some people think this is Apple’s attempt to claim the rights to the content. So not only are they accused of “forcing” publishers to pay their normal 30% commission, but they’re being accused of making it impossible for the same content to be published elsewhere.
  • Apple has the right to reject any work submitted for publication on the iBookstore. This is making people accuse Apple of censorship. It’s also raising concerns about publishers spending hours preparing documents that they might not be able to sell at all.

This is typical anti-Apple fear mongering, being spread primarily by people who haven’t taken the time to look at the software, see how it works, and see some of the amazing documents it can create. I was pretty much ignoring all of it until today, when I read a post by Liz Castro titled “Ten reasons I can’t recommend or use iBooks Author.”

My Response to Liz’s Comments

I greatly respect Liz. Her HTML Visual QuickStart Guide was a major learning tool for me as I began developing websites. She has been working with ebooks for a while and should have a lot more insight on ebook publishing than I do. So when she came out so strongly against iBooks Author, I had to read what she said.

And sadly, I didn’t agree with a lot of it.

I composed a lengthy response to her 10 points. Unfortunately Blogger (her blogging platform of choice) does not accept more than 4000 characters. So I cut it in half and the first half was lost. Fortunately, I’d composed it in a text editor (so I could see her points as I addressed them) so I still had a copy. I reposted it. The result on her blog, however, is a disjointed mess.

So I thought I’d present my response here.

If you haven’t read Liz’s blog post, please read it first and come back. I’ll quote pieces of it here, but you really do need to read the whole thing to get her complete point of view.

And please don’t think this post (or my response on Liz’s blog) is an attack on Liz. It’s not. I still respect her and her opinion. I just think that she and so many others are missing the point of iBooks Author. And it really saddens me that they’re going on the offensive to attack Apple when I don’t think Apple deserves it.

1. Apple has the final say in what can be sold on the iBookstore.

I see Apple’s approval process as a GOOD thing. Right now, there’s nothing stopping anyone from publishing any crap they want as an ebook and distributing through services like Amazon Kindle. This is a far cry from publishing as we’ve known it, where only authors and works approved and edited by an experienced, professional publishing company team would be published. Apple’s review process helps weed out the crap and make its library of content more valuable to iBookstore shoppers. While some folks might be fearful that Apple will not approve their work, I’m not — and you shouldn’t be either. People who can turn out quality work should have nothing to worry about as far as the approval process goes.

Now there is some concern over Apple using this power to censor content. For example, perhaps they refuse to publish a book that says negative things about Apple or its founders. (Remember how they pulled all of a certain publisher’s books out of the Apple Store after they published an unflattering biography of Steve Jobs some years back?) I’m not terribly worried about that, but I do admit that it is a possibility. Obviously, if there are documented examples of Apple not approving something that should be approved, I’d be willing to revisit this point. For now, however, I don’t think it’s an issue.

2. It’s not at all clear how far Apple’s control of an iBA book’s content goes.

I’m certain that Apple’s ELUA does not cover the content of an ebook. For them to do that would be akin to taking copyright. I have every intention of continuing to publish my own ebooks on Kindle, NOOK, and other distribution methods/formats, as well as in print using Print on Demand. I do, however, plan to create special iBooks Editions that showcase the special features. I have absolutely no concerns about Apple trying to stop me from publishing the same content in other formats elsewhere or taking action once I do so.

3. It’s not at all clear that Apple’s exclusivity benefits kids, schools, or teachers.

No argument there.

(You need to understand that I have little or no interest in developing for the K-12 educational market, mostly because I know nothing about it. Best for experienced educators to approach that market.)

4. iBA ebooks will work only on iBooks on iPad.

I think this point gets to the reason why the exclusivity doesn’t matter. If you use iBA, you are automatically accepting the fact that what you create with it will only be usable on one platform. So where else would you sell it if not the iBookstore? Yes, this does make more work for publishers who want to take advantage of the capabilities of iBA and continue to publish elsewhere — I understand completely that this will increase my workload and I have accepted that. I think others will, too.

I don’t agree that Apple wants control of the content. They’ve created a proprietary file format — that’s all. I addressed this point earlier.

As for iBooks not supporting traditional epub — that would be a serious error on Apple’s part. I already prefer Kindle for ebooks because of its multi-device flexibility. If Apple removed flexibility from its ebook reader app, they’d only make it less attractive. I can’t see Apple being that stupid.

I do want to point out, however, that if a book I considered buying on Kindle was available as an enhanced ebook in the iBookstore for a similar price, I’d probably buy it in the iBookstore. I see that as a competitive edge for publishers willing to do that extra work.

5. It fragments the ebook ecosystem and requires new publishing tools and workflows for publishers.

Agreed — this new tool will increase the amount of work we need to do to get our content on multiple platforms.

Right now, my workflow is pretty simple: create in InDesign, export to epub for iBooks and NOOK, convert to Kindle. This is a very smooth process for me. Once I finalized content in my latest ebook, for example, I sent it to my POD printer and submitted it to Amazon, Apple, and NOOK all in one day.

When iBA came out, I immediately began converting that title to iBA format. I’ve put more than 12 hours into the process and am only half finished. I see at least 3-4 days of extra layout work for each of my titles. Is it worth it? Well, until I get a title out there and see how it sells, how will I know?

6. Apple’s iBookstore currently serves only 32 countries.

Apple’s iBookstore may serve a limited number of countries, but let’s all consider how Amazon, for example, handles royalties. If a book is sold a country other than the six or so on a special list, your royalty rate drops from 70% to 35%. Apple doesn’t screw around with the royalty rate. It is what it is. I don’t know about you, but I write and publish in English only and don’t see a huge international market for my work. So this is a non-issue for me.

7. Apple iBookstore is not that great.

Agreed. Apple’s iBookstore isn’t as good as it could be. I think that’s because of its limited market. As I mentioned earlier, even I prefer Kindle — and I’ve been a loyal Mac OS users since 1989! Apple could certainly get more people using the iBookstore if they introduced apps for more platforms and allowed cross-platform synchronization. More users would result in more reviews, more recommendations, etc. But I do agree that the whole system needs to be revamped to make it easier to use.

8. It’s bossy.

I think this is a silly point.

9. It’s unnecessary.

Not sure what you mean by this one.

10. Books are special. This is about books (for teaching our children!) which in my opinion should not be controlled by any company or government.

I really don’t agree with your concerns on this given everything I’ve said above.

A Few Parting Thoughts

I’ve read a lot of what people are saying about Apple’s “evil” EULA for iBA and although there are plenty of valid points, I think the software and its ability to create amazing books really makes most of those points moot.

I say embrace iBA as a tool to set your work apart from the competition and attract new readers. At least on a trial basis. Rather than get angry about this free software’s limitations as far as distribution goes, consider the new market it opens for you by providing an easy to use tool for taking ebooks to the next level.

Remember — technology continues to move forward. This may be a great tool for today, but who knows what will come up in a month or two? Perhaps new epub standards will emerge with universal support, making something like iBA completely worthless.

That’s my two cents, for what it’s worth.