Yeah, Scrivener, Part One

The more I use scrivener, the more I love it. There are so many reasons for the love, I can hardly count them.

Scrivener logo

I got my final clean version of Children of a New Earth back from my editor last week. I spend the rest of my writing time that day, nearly two and a half hour, re-importing it scene by scene into Scrivener and making sure all the scene breaks and other formatting stuff was correct.

Why spend that much time on it? One reason is version control. The other is that I spent another two hours or so doing formatting, and created both the ebook and paperback in that time. For those of you who have created ebooks manually using a word processor, or fought to get Word to create a proper print ready pdf, you know how much time I am saving.

Version Control

For both prolific writers and avid rewriters, version control soon becomes a major challenge. I learned this early on in my writing career when I was writing articles for a local LGBT paper. I had the editor take me to task for numerous errors in one submission. I couldn’t see the errors on my side. I later discovered I had accidently submitted a rougher version of the same article.

My issues with version control stem from three sources and each carries its own liabilities an solutions.

Tech

Back up your computer! If you haven’t had this drilled into your head, all it takes is a couple of major data losses and it will be. I’ve been through dozens of backup methods over the years. I used to print hard copies of everything. I still have stacks of moldy paper in my basement with crappy stories I thought were gold once upon a time. Then I saved things to floppy disks (yes, I am that old) and USB drives.

The problem with all these backups is they aren’t the same. Twelve different versions of the same story might be secure, but it’s also confusing. Trying to find the one you are currently working on can drive you nuts and lead to mistakes, like submitting the wrong version of an article. If you backed up an early version of your novel, it will be there after you lose the current version but you still lose hours of editing.

The solution: I now use an automatic cloud storage. I’m on a Mac right now, so I use time machine, synced to a personal cloud device. The device cost me a hundred and fifty dollars but it was money well spent. It sits next to my router, uses the same wifi network and acts just like an external hard drive except I don’t have to worry about backing things up, it does it automatically. It also re-saves the most recent version of every document, so I don’t have to worry about old versions floating around.

Editing

As a younger more hesitant writer, I had to save a version of everything before editing. I had novel A draft one, Novel A draft two, etc. I was worried that I would regret rewriting and want the old version back. Then I started getting involved in writers group. So now I have Novel A draft eight with x person’s comments. It got so I each novel had it’s own folder and even then those folders were packed with extraneous files.

Now I am more confident. If I change something, its because the change will improve the novel. I don’t care so much about keeping older versions. In fact I’ve gone to the other extreme. I hate having older versions of my writing around. It fill up your hard drive. And it’s drivel. I hate to be blunt, but it’s true. Do you really want an early draft of your novel with seven thousand typos floating around? And no, ten pages of run on sentences isn’t “your voice.” It’s bad writing. Clean it up and get rid of the old version.

The solution: Scrivener. I keep all of my writing projects in scrivener these days. I use the snapshots feature to save anything I am going to do a deep rewrite on. If I am moving or getting rid of whole scenes, I drag them out of the manuscript folder but leave them in the project in case I need them later. If I am workshopping something, I either import people’s comments directly into a separate scrivener file or make the suggested changes directly on the scrivener document. The Scrivener manuscript always remains the most recent, cleanest version of that project. And that is a thing of beauty.

Indie

The third source of too many versions is simply being an indie writer, though traditional writers may have their own version of this same problem. You get your clean edited manuscript back from your editor and you start formatting. Print formatting and ebook formatting are different beasts, so the first step is to create two new versions of the clean document, one for print and one for ebooks.

Every author, whether indie or trad, knows the horror of seeing your book in print for the first time and spotting a typo. Argh! If you are trad, you complain to your publisher and then grumble in your writers group until they finally get around to fixing it. (And if it’s not POD, don’t expect them to be able to do anything.) If you are indie, you go back and change it yourself. Oh, but did you also change it in the mobi file? the epub? The original document? Personally, I am way too ADHD to get to them all. It’s a struggle.

Traditional authors aren’t immune to this problem. Every publisher/editor/agent has their own set of submission guidelines. By the time you have spent a year and half trying to sell a manuscript, submitting it to dozens of agents, you will have a pile of version, each formatted to this or that person’s taste.

Multiply each of these three issues by several novels and you will see what I am dealing with.

Solution: Become a scrivener power user. This brings us full circle to the original intent of this post, formatting and compiling in scrivener. This post has grown to the point where it might be best broke into two. For now, learning to use Scrivener’s compile feature means that you can create multiple versions, all based off the same document. A year from now when you need to update something, you do it in Scrivener. When you resubmit, you do it from Scrivener. You never have to wonder which version of your novel is the most current, and did you correct those pesky little mistakes in all versions or not? It’s all in one place.

Coming next: Becoming a Scrivener compile power user

Tagged , , , . Bookmark the permalink.

One Response to Yeah, Scrivener, Part One

  1. ion-christopher says:

    Totally agree.

Leave a Reply

Your email address will not be published. Required fields are marked *

(Spamcheck Enabled)