Showing posts with label The Process. Show all posts
Showing posts with label The Process. Show all posts

Tuesday, June 24, 2014

Critique Methods Part II, by Matthew MacNish

Okay, this should hopefully be the last post in my series about critique and advanced use of MS Word. You can find the previous posts here:
Last time, in Critique Methods, I talked about the difference between copy-editing, line-editing, and developmental editing. This time, I'm going to cover ways to convey those methods, and some other types of feedback, to the author of the manuscript you're critiquing.

Comments


First, and probably most important, is the function built into MS Word "leave a comment." It's been there since at least Office 2003, and I'm sure much longer, and it is probably the most useful tool when providing another writer feedback on her work.

To leave a comment, highlight a bit of text, or even a space, a punctuation mark, or formatting character (if formatting is revealed), and press CTRL+ALT+M. You can also use your mouse to click REVIEW-NEW COMMENT, but who has time for that, amiright? You can also leave a comment on another comment. This is done by highlighting the comment instead of a piece of text, and again, pressing CTRL+ALT+M. This can become extremely useful when passing a critique back and forth for a few passes, or when doing a tandem critique, or when co- or multi-authoring a text. Comments left by different user will be color-coded and start with that user's initials [in brackets].

NOTE: In the below screenshot, the comment color by user/author wasn't working, and I didn't have time to figure out why (Review - Track Changes - Dropdown Menu - Track Changes Options - Comments By Author - Didn't Help).

Anyway, comments can be used for all sorts of things. I think one of the most important things you can do during critique is to leave a comment on a particular turn of phrase or line of dialog that as a reader, you really loved. Encouragement is its own form of critique, and it can be just as crucial to the development of a manuscript as constructive criticism.

Highlighted Text


Another thing I try to do when critiquing a manuscript is to point out overused words. In my own manuscripts, these would be all the JUSTS and ANYWAYS and ONLYS. Everybody has different crutch words, and of course sometimes an author uses and repeats particular words for particular reasons, whether they might be narrative voice or even a verbal tic of a certain character that they use in dialog.

So I find that the best thing to do is to highlight these words, and therefore point out to the author how often those words are appearing, and let them decide for themselves whether it was on purpose, are whether perhaps the volume grew so high by their falling into autopilot while drafting. It's their manuscript, so it's up to them to decide what, if anything, to change.

Tracked Changes


Then again, sometimes you want to illustrate a change or point out a clear mistake. As discussed in my previous post, you want to be careful about copy- or line-editing someone's work who didn't ask for it, but if the need or lack thereof is not specific, and if we haven't worked together before, I will generally do some light copy-editing when critiquing a manuscript.

Some of the changes I will track are simple and obvious mistakes like typos, mispellings, comma splices, and other general grammar snafus, but sometimes, I will also track changes in stylistic choices. This is not done to tell another writer how they should tell their story, but rather to suggest options that cannot be conveyed by a simple highlight. Oftentimes, this is to discuss a specific question the author had when they requested the critique, such as "Does my male teen protagonist sound like an actual teenage boy here?"

This is the kind of thing critique partners should definitely discuss up front, so that a clear understanding of what's needed and what's expected will be in place before the work begins (critiquing an 80,000 word manuscript is a lot of work). Once you have worked together several times, there should be a clear understanding and solid foundation of trust established.

Inserted Text


Sometimes, comments just are not enough. Different people work in different ways, but I find that it's most often when discussing big-picture topics like pacing, plot arc, or character development that it becomes necessary to insert a large chunk of text as pictured here (actually, usually much larger, but this is just an example).

Of course, as I will describe below, you can technically fit as much text in a comment as you need to. I'll get to how that works in a moment, but the problem is that there is only so much real estate in the comment sidebar, and eventually you will run out of space.

So when I have something very complicated to say, I simply insert a large chunk of text directly into the existing text. As long as TRACK CHANGES is enabled, it will automatically appear colored (again, this should by default appear in different colors for different users, but something was off with my settings).

Comment Sidebar


Something you may eventually notice (this is rare when doing a solo critique unless it gets passed back and forth several times, but can be quite common when co-authoring) is that when so many comments are added (or a few comments that are very long) you will eventually run out of space on the right sidebar. When this happens, some of the comments will be truncated, and a small ellipsis will appear at the bottom right corner of those comments.

You can click on the ellipsis (it's barely visible in the bottom right of that screenshot above) to have the entire comment appear (scroll-able if necessary) in the left sidebar that usually makes up the document map when you have that option displayed. This setting is extremely useful in comment heavy documents like co-authored works.

NOTE: As I mentioned above, I created this example (I would never edit Melville, but it was the first free text that came to mind) on two different computers, with two different users. Normally, Word will color code the comments by user. I'm not sure why it didn't do that here, but if you click the image to zoom in, you should be able to see that the [BRACKETED] initials are different for the two users. You can also tell when a comment is commenting on another comment, rather than the text, because the bracketed text references the number of the original comment. It sounds much more complicated than it is.

* * *

And with that, this post has probably gone on far too long already, especially considering most of this is pretty basic stuff that the vast majority of you know already. Personally, I consider myself somewhat knowledgeable in Microsoft Word, but I am by no means an expert, and there is always more to learn.

Do you have any questions? See anything I missed or got wrong? Please share your thoughts in the comments!

Saturday, May 24, 2014

Critique Methods, by Matthew MacNish

There are lots of ways to critique a novel, most of them pretty useful. But ... they do not always have clearly defined definitions among the writing community. I'll be covering what I understand them to mean, in this post and probably one other, but I don't mean to imply that I know everything, or can't be wrong, because I definitely don't, and certainly can.


Before I get started, you should definitely read:
These topics are all related, trust me.

Now, you back? Good. I've exchanged a lot of pages with a lot of writers. Some of them are famous authors, some of them are regular authors, some of them are aspiring authors, and some of them are just starting out. There is great value in all of those examples, for both writers involved.

In exchanging all those pages, I've learned a lot of things. For one, no two writers work exactly the same. Probably when drafting and revising too, but I'm talking about critiquing here. A lot of times, when exchanging work with another writer, there isn't time for what I like to call "a deep critique," and so we go through a quick "beta read," and end up exchanging an editorial letter, that usually averages around 2-5 pages, and really only covers big picture topics. Character Arc, Theme, Plot, Pacing, and so on.

These are great, and they certainly help, but personally? Nothing helps me polish my manuscripts more than a good deep critique. One that is so full of highlights, and tracked changes, and comments, and inserted colored text that it looks like a burst pinata at a third grade birthday party.

Nothing inspires me more than really digging in. And I mean both with feedback someone has given me on my work, and in doing the same for someone else.

So, a deep critique. What goes into it? Like I said, it can be different for every writer, but this is what I do:

Copy-Editing

I'm no professional, and it isn't quite this simple, but basically copy-editing is looking at the text (copy is text of any kind before it gets typeset in preparation for printing, binding, and publishing) on the most microscopic level. Is everything spelled right? Is the grammar correct? Are words properly capitalized? Is the punctuation correctly used and properly placed?

Basically, copy-editing is pointing out mistakes. Again, it's not that simple, but that is the basic concept.

I usually try to do a little copy-editing when I critique. A lot of times, the things I point out will be stylistic choices, and the writer knows what I'm pointing out is just a suggestion, so much of the changes are eventually ignored, but the important thing is to point them out, and let the author decide for themselves whether they made that choice on purpose.

Some writers vehemently do not want you to copy-edit their text during critique. They will usually clue you into this in one way or another. For example, "I'm sending you this in .PDF format, so you can turn your inner editor off."

That's generally a hint that means don't send me back a document that has more red on it than black and white.

When working on critique exchanges with a fellow writer, it's important to know what they're looking for, and not to waste your time giving them feedback they aren't interested in, and honestly might offend them.

Line-Editing

For a long time I did not understand the difference between line-editing and copy-editing, and to be honest, as far as I know, there is still some overlap, and a few gray areas. That said, if we're sticking with the microscope metaphor, line-editing is generally considered a level above copy-editing on the big picture scale, but the two are tied together closely enough that sometimes the same person can do them both.

In informal critique exchanges, I certainly try to. Line-editing, like copy-editing, still deals with sentence structure, and does not concern itself with macro-level concepts like pacing and plot. The main thing line-editing seeks to achieve is consistency. If you called the love interest's dad Jon with no H in chapter 3, did he suddenly gain a letter in the spelling in chapter 10? If the antagonist has a verbal tic in which he refuses to speak in contractions, does he suddenly say "ain't" in chapter 12?

Passive voice, syntax, repeated words, subject/verb agreement. There are many things to look for, but the job of a good line edit still considers a manuscript one sentence at a time.

Developmental Editing

Why is there no hyphen in this one? I'm not sure either.

Anyway, developmental editing is the highest level gaze a manuscript gets. Oftentimes, major changes of this kind are best left to a developmental editor who works for a publisher who is actually paying you to publish your manuscript, but when exchanging pages with other writers, there is nothing wrong with making suggestions, knowing that your critique partner will only implement those that resonate with her vision for her story.

Developmental editing concerns itself with the biggest of the big picture topics. Plot, pacing, character arc and development, theme, and so on. It considers a manuscript by the paragraph, page, scene, and even chapter. Oftentimes, scenes can be moved around to improve tension or build suspense. Other times, scenes can be cut or lengthened or even inserted (as in a new scene), depending on just what the story needs at that position in the tale.

Of course, this is all highly subjective, and I would definitely recommend second and third and fourth opinions if you're considering making these kinds of sweeping changes to a manuscript, but I have personally re-written an entire book from scratch before, and it was a great learning experience.

* * *

Well, that's it for today. Come back next time and I will cover exactly how I implement these methods when I'm critiquing pages for another writer.

In the meantime, when it comes to general manuscript cleanup, you should absolutely check out this post by my favorite editor, Andrew Karre from Carolrhoda Lab.

Monday, January 14, 2013

The Beauty, and Agony, of Revision, by Matthew MacNish

This is just a stock photo of the Track Changes function in Microsoft Word. I don't actually use it much myself early on in revision, even if it plays a big role later.

Revisions, just in case there are any out there still wondering, can take many roles in the complicated process that is the drafting of a manuscript for publication. The second draft, or first pass, is very different from the first, and the seventh draft (or however many it takes to get you ready to share with your CPs) can be very different from the sixth.

Being the only un-agented, unpublished author here at Project Mayhem, I'm perhaps the least qualified to post on this subject, but then again, so what? The whole point of blogging about publishing, and connecting with other writers is for all of us to learn from each other, right?

So even if I don't have anything to say that helps, maybe we can all learn something from each other, even if the comments are more illuminating than the post itself.

Now, there are several things we, as writers, must focus on during revision. There are little picture things, like grammar, spelling, sentence structure, repeated words, formatting, punctuation and so on, which if you have a contract and a paid copy-editor, maybe don't seem that important, but surely we all care enough about our work as professionals to get these things as close as we can to perfect, before we hand our writing off to ... whoever may be the next person involved in our process.

Then there are big picture things, like pacing, character arc, theme, voice, plot arc, and so on and so forth. These are the kinds of aspects that can make or break a story. A well executed story, however perfect its details, does not necessarily make a great tale. Of course, sometimes it's a very fine line. If you do have a professional editor you work with, they will often make suggestions about these big picture items, but even if you don't you can sometimes utilize critique partners and beta-readers to help you find holes in these building blocks.

Personally, as the title of this post suggests, I find revision to be both the best and the worst part of writing. It's nothing like the natural high of drafting an exciting new project, which can often carry me through months of feel good, productive days, but it does have its moments.

The hardest part of revision is plowing through things that you knew didn't work in the first draft. Missing scenes. Extraneous scenes. Mis-placed scenes (it's not all about scenes, they're just coming to mind right now). Finding a way to force these things into a working format can be so hard, it often takes tens or hundreds of times as long to fix them as it did to draft them.

However, the best part of revision, the moments when you take a good turn of phrase, and make it phenomenal, or when you take a strong, tense scene, and turn it into an edge-of-the-seat-nails-chewed-to-nubs type of scene, and you have that moment where you sit back, look at the page, and sigh, so satisfied that you finally figured out what you were put on this earth to do? That's the moment when you remember what it's all about. When you remember why you started writing in the first place.

At least, that's how it works for me. What's your revision process like?