Never seen a thread about the subject so far or maybe I've forgotten. In any case, I think it's due time.

Anyway, I'm submitting a script to Shriekfest soon and am shooting for zero/absolute minimum of typos. Naturally, I've read the script over several times (as always) but this time, I decided to really step up my game. I did separate scans for as many words with dual spellings as I could think of (are/our, bare/bear, hear/here, its/it's, than/then, their/there, etc.) as well as separate scans for the slugs just to make sure everything was as close to perfect as possible. As annoying as it was, it wasn't particularly time-consuming and is a process I plan to continue in the future.

In any case, typos come in many forms and not all of them are as easy to sniff out. I was wondering how other people approach proofreading. It's the most tedious part of writing, for sure, and perhaps takes backseat to other priorities but naturally, a script that's noticeably laden with typos certainly suggests something about the writer. It's definitely something we have to consider.

Also, if anyone's got any more of these pesky dual spellings, I'd love to hear them. I know Bert had some issues with Angel/angle in the past. Maybe we can get a database going.

Proofreading. The mother of all tedious chores. I'm a fairly impatient guy so proofreading is definitely my Achilles heel. Obviously no one wants to present a script with numerous typos but most of the time you simply grow blind to (your own) typos. You can read the same sentence ten times without spotting the typo.

What I try to do, and I'm not saying that my scripts are typo-free, is to first use Final Draft's read-back function. Sometimes you can catch a typo by hearing it. Then I do a good ol' manual proofread - but I do it backwards. That way I am not really reading the script - because if I do that I know I will miss the typo - but the words.

Can't claim that it's a bulletproof way of doing it but that's how I do it.

Quoted from James McClung In any case, typos come in many forms and not all of them are as easy to sniff out. I was wondering how other people approach proofreading.

The absolute best way to find typos in your own work is to find a quiet place to yourself, then read it out loud, completely enunciating each word with care.

Do not do this on the computer.  Print it out and do it on paper.  This step is important.  For some reason, typos are more glaring in print.  They just are.

It will be tedious -- and hard to stay focused for a feature-length -- but there is no better method.

As an added bonus, you will probably find that you want to make a few tweaks in your dialogue along the way.

I recommend it to everyone.  Try it, and you will be surprised how effective it is for a final polish.

For me, they usually "jump out" at me.  If not, my Movie Magic catches pretty much everything and underlines it and even beeps at me.

But, for me, the best and easiest way to proofread is to read back each and every passage, after it's written.  Not at the end, when you're all done, but right away.  You'll find that you'll catch the vast majority of awkwardly phrased sentences this way as well.

I hear people say things like, "I don't understand how I missed these typos, I read it over like 3 times!", and I have to laugh.  That's not going to cut it...at all.  IMO, you should be reading everything over at least 10 times...and that's before you've even finished the script.  After it's all written, you should give it another 2 or 3 reads to catch and clean up any lingering issues.

It's not a lengthy process, really, as long as you're writing at a good clip.  You'll know your script inside and out, also, and it will allow you to "see" it in a whole new light, most likely.  I personally don't even look at this as proofreading.  More like getting to know my script on a personal basis.

Then I usually like to take it out to dinner, snuggle a bit, and then have  smoke.

When I proofread my work, I read the script aloud in a slow voice and go through the screenplay out of order. Working your way backward paragraph by paragraph works well, although reading it backward word by word will almost always catch every single error.

If you try to read the script in proper order by sight only, your mind will most likely interpret the words you meant to write instead of what you actually wrote. The biggest mistake I often make, for example, is accidentally typing "form" when I mean "from" and vice versa.

Take this line: "Daniel said their family comes form the east side of the valley." If I read the line by sight only, I'll almost always miss the error because my mind will interpret what I wanted to write. If I read it aloud slowly, I'll almost always catch it because I will hear myself say what I actually wrote.

Reading the script out of order is also important. If I try to read it in order, my mind tends to wander since I almost always know exactly what line or action follows. Working backward makes the action and dialogue harder to recall and forces me to concentrate on what I am actually reading.

Quoted from James McClung Never seen a thread about the subject so far or maybe I've forgotten. In any case, I think it's due time. Anyway, I'm submitting a script to Shriekfest soon and am shooting for zero/absolute minimum of typos. Naturally, I've read the script over several times (as always) but this time, I decided to really step up my game. I did separate scans for as many words with dual spellings as I could think of (are/our, bare/bear, hear/here, its/it's, than/then, their/there, etc.) as well as separate scans for the slugs just to make sure everything was as close to perfect as possible. As annoying as it was, it wasn't particularly time-consuming and is a process I plan to continue in the future. In any case, typos come in many forms and not all of them are as easy to sniff out. I was wondering how other people approach proofreading. It's the most tedious part of writing, for sure, and perhaps takes backseat to other priorities but naturally, a script that's noticeably laden with typos certainly suggests something about the writer. It's definitely something we have to consider. Also, if anyone's got any more of these pesky dual spellings, I'd love to hear them. I know Bert had some issues with Angel/angle in the past. Maybe we can get a database going.

Hello James,

I don't use spell checkers. I try and rely on what I know and if I don't, I look it up. Even still, there are words that sometimes are so common that we think we know their spelling and we don't.

I've given this example before, but it's a funny one. I had written the curse of Damn as Dam and very repeatedly through a manuscript. At that time, I honestly didn't know any better.  

My advice is to read your work aloud. Also, I find it helps to work from a printed copy and away from the computer for a change of pace.

The best thing I recommend is a lot of time between different projects that you're working on because your eyes just get tired and it all runs together at some point and you're sure to miss things.

Proofing takes time. It's like rewriting and all that. All part and parcel.

Sandra

Quoted from abelorfao When I proofread my work, I read the script aloud in a slow voice and go through the screenplay out of order. Working your way backward paragraph by paragraph works well, although reading it backward word by word will almost always catch every single error. If you try to read the script in proper order by sight only, your mind will most likely interpret the words you meant to write instead of what you actually wrote. The biggest mistake I often make, for example, is accidentally typing "form" when I mean "from" and vice versa. Take this line: "Daniel said their family comes form the east side of the valley." If I read the line by sight only, I'll almost always miss the error because my mind will interpret what I wanted to write. If I read it aloud slowly, I'll almost always catch it because I will hear myself say what I actually wrote. Reading the script out of order is also important. If I try to read it in order, my mind tends to wander since I almost always know exactly what line or action follows. Working backward makes the action and dialogue harder to recall and forces me to concentrate on what I am actually reading.

Very good tips here I think. Reading backwards. Especially for those who have difficulty in this area.

Sandra

My method might be looked on as time-consuming but it works well.

I handwrite all my stuff first anyway, then copy it onto the computer. This way, its like a revison at the same time as writing; sometimes it could be a couple of weeks between each process, so I can change things if needed.
Then I give the script a quick read and pick up any minor typos.

I usually leave my scripts for a few weeks before I go back to it to correct any mistakes.

I find reading soon after catches some errors but if you leave it for a while you'll catch almost all of them.

Then again, it's my grammar that could do with improving.

Here's what I do. What Bert said. That's all right.

Then stick it through a few good programs. As they'll all pick up different things.

Invest in a good dictionary. They are worth every penny and more.

Find a friend who is a smart arse. They can have their uses. Buy them a drink. Do them favours. Then ask them when they need you. Job Done.

R

Yeah, proofreading can be a long, lingering pain but all it’s for the betterment of your work.

Some great suggestions here, in particular James's separate combs for slugs and dual spelling words as well as Bert's (environmentally questionable) printing out habit.

I agree with Rob in that you can literally read over your stuff a dozen times and not spot the most obvious mistakes…or finally detect those glaring errors on the 10th read. I think what works well is once you’ve ran it past your own eyes a number of times and all the software spell checks possible is to give it to someone else to read, someone you can trust with the directive for them to focus on spelling and grammar as well as what they think about the actual story.

Oh and to echo Jeff's sentiments, once its all done, take it out for dinner, a movie, maybe a drink or two before getting it back into your domain for some serious heavy petting.

Quoted from Colkurtz8 Oh and to echo Jeff's sentiments, once its all done, take it out for dinner, a movie, maybe a drink or two before getting it back into your domain for some serious heavy petting.

Now you're talking.

I do believe recycled paper is available. For those who feel the planet and the trees need saving.

Scripts read better on paper. In my humble cake.

Cooking col.

R

Quoted from jayrex I usually leave my scripts for a few weeks before I go back to it to correct any mistakes. I find reading soon after catches some errors but if you leave it for a while you'll catch almost all of them. Then again, it's my grammar that could do with improving.

I've found setting a script aside for a few weeks to a few months is also helpful when it comes to finding plot and story problems. Constantly working on a script day after day often causes me to become wedded to the words I've written. Distancing myself from the script for a while allows me to read the story with a more critical eye. I can't tell you how many times I've written a script I felt was perfect only to find glaring deficiencies when I reread it after a few weeks or months.

Quoted from abelorfao I've found setting a script aside for a few weeks to a few months is also helpful when it comes to finding plot and story problems. Constantly working on a script day after day often causes me to become wedded to the words I've written. Distancing myself from the script for a while allows me to read the story with a more critical eye. I can't tell you how many times I've written a script I felt was perfect only to find glaring deficiencies when I reread it after a few weeks or months.

Absolutely and one hundred percent agree. I know my scripts are completely deficient and yet I cannot write them without going through such deficiencies. The process of writing and rewriting goes so far and wide I can't even express it.

That's why I come back to old works and cycle through them and then enter into new unexplored territory again.

It helps to read through a script at different times concentrating your search for different problems each time. For instance one time you go through it only paying attention to sluglines and another time you go through it to tighten everything, another time you go through it working with characters and their particular dialogue, another time you go through it and look for the kind of punctuation marks that aren't literal punctuation marks, but ones that mark a certain strong image, or theme, or any critical marking point in the script whereby a character learns something or there's been a dramatic shift etc... and on and on...

Sandra

Hi,
I'm brand-new to Simply Scripts.  My parents wrote radio scripts, mostly murder mysteries, in the 1940s.  Two Shadow scripts, a Mr. and Mrs. North, a Famous Jury Trials, a Grand Central Station.  I have copies of them all.  However...I myself am a professional proofreader, so thought I'd respond to your post.  (I'm also a copyeditor, and have edited more than 60 book manuscripts in the past two years.)  If you'd like to have a professional proofreader work with you, contact me!  LindaJay