Scrivener Step 4: Importing & Compiling

by Mary Sutton / @mary_sutton73


Note: I am using Scrivener for Mac. If you are using Windows, please allow for differences.


So here we are, the end of my Scrivener musings. I want to talk briefly about two remaining features: importing documents and compiling output.

First, importing. It's a breeze, seriously. Create your project. Choose File > Import and select the thing you are importing. Normally, this will be a file. Scrivener can handle .doc, docx, .rtf, .txt and maybe some others. If you are importing things with images or footnotes, you'll get a warning about those things. That's okay.

After the import, you wind up with one single Scrivener Text document. Here's the hard part. Well, not hard, but tedious. You have to break this into individual scenes using Document > Split. Okay, you don't have to do that. But to really get the full power of Scrivener, you really should.

I did this twice with two shorter works: a novelette and a short story. Both times I used the short story project template. I had offset my scenes in Word, so I just scanned my import for the "#" symbol and split the file there. Along the way, I found a couple of other places I wanted to split, so it was a helpful exercise.

Once you have all the scenes split, you can multi-select and set labels and status if you want. And that's importing. Pretty simple.

Once you're done, you can compile your manuscript. Again, pretty easy. Click the big "Compile" button on the toolbar, or choose File > Compile. Set all your options or accept the defaults. Those defaults will result in a standard manuscript submission template. One note: If the "Compile For" field says "Print" it means print - as in sending to your printer and results in a hard copy. If you want a file (say a .doc file for submission), change the Compile For field value. Scrivener does support the .docx format. You might get a message about certain characters being stripped. If you want to change your output format, you can do so.

I compiled for a submission and got a .doc file that was, almost without tweaking, in standard manuscript format: 1 inch margins all around, Courier 12pt, first page with title and address block, and header. I did have to make a few tweaks, but they were minor. Of course, I then noticed that you can change the front matter template, so I won't have to do it again.

And that's it. I'm sure there's more to Scrivener, and if I stumble across something I think is really valuable, I'll let you know. But these four steps are all you really need to be productive. Someone asked about learning curve. I think someone who is reasonably proficient with computers or Microsoft Word can be using Scrivener comfortably in a week or less. So yeah, not a big learning curve.

I already like Scrivener a lot. I think I'm going to love it. So what about you? Ready to take the plunge?

Expanding the Toolbox

by Mary Sutton / @mary_sutton73

There are many tools in a writer's toolbox, but none quite like the applications we use for our craft (unless you still write long-hand, in which case God bless you). Like many writers, I have always used just a word processing application to do my writing. I use Microsoft Word, some people may use Word Perfect, but same concept: open application and type. That means you have to find another way to keep track of all those pesky things that writers of fiction must have: character notes, plot synopses, scene descriptions, etc. I used Evernote. Some writers use Microsoft Excel, some just use a separate Word file.

This all works, but it's a bit clunky. After all, when your novel manuscript is 90,000 words and 47 chapters, finding one particular scene - the one you have to move - can be a little tricky.

For a couple years now, I've heard about this alternate application - Scrivener. Break your manuscript into scenes. Easily move them around. Keep your character notes right there. Pin things to your virtual cork board. I have friends who swear by this application.

I've always been intrigued by the web site description, but have been afraid to try it. What if I don't like it? How much time am I going to invest in learning a new tool (I've used Word for almost two decades, I'm pretty good with it)? But I saw Scrivener and got to touch it with my friend on our research field trip last weekend (more on that in another post). And I liked it. Or I was at least intrigued by it.

So I'm taking the plunge. I've downloaded and installed Scrivener. I'll be blogging about my initial experiences - say the first week or so - for anyone who is similarly interested and wants a first-hand account.

Here goes nothing.

Note: I'll be using the Mac version of Scrivener for this experiment. If you are using the Windows version, please allow for slight differences.