Things have been crazy busy at my end of the world, but I wanted to take some time to give a well-deserved shout-out to a fellow blogger whose meticulous proofreading/editing services I’ve recently had the chance to experience.
I’ve been following the blog of Thomas Weaver for quite some time now (well, just about since I started blogging myself), and have consistently enjoyed his Grammar Rants, amongst other posts. I’d like to believe that we’re similar in some respects (perfectionists, sticklers for detail, and grammar na… er, ninjas), but I can’t claim to have any seriously honed editing skills (though I did rant myself about things an editor should’ve picked up in a book written by my favourite author that I just couldn’t overlook). So, since I remembered from first browsing his site a long time ago that he was also an editor who offered a free sample of his proofreading/editing skills for up to 5000 words – and because I knew I would soon be submitting my first chapter, which therefore had to be extra polished – I thought I’d see whether he’d be able to find any little errors I may have overlooked in my own writing. I was pretty convinced that there wouldn’t be more than a few, and that those would have been ones that crept in with recent edits to said first chapter.
Boy, was I naïve.
Thomas not only found a few errors that had crept in, he also managed to remind me of how inconsistent I’d become with my commas and semicolons (in more places than I’d like to admit publicly), and of my bad habit with adding a fourth dot to an ellipsis when it’s at the end of a sentence, which isn’t correct.
I did have the audacity to disagree with some of his suggested edits, and, in our interesting email conversation about several aspects of editing and grammar, rather than being a “my way or the highway” kind of guy, he was happy to agree with some of my reasoning and answer my questions about some of the finer points of… stuff.
Oh, and, as a bonus, he came up with this gem regarding ellipses that cracked me up:
Then thou must write three dots upon the page. Three shall be the number of the dots, and the number of the dots shall be three. Four dots shall thou not write, neither shall thou write two, excepting that thou then proceed to three. Five is right out. Once the three dots, three being the number of the dots, be written…
It helps to know the Monty Python original to appreciate it:
So, clearly, if you’re in need of professional proofreading and/or editing, I can whole-heartedly recommend Thomas’ services. Not only will you get first-class service, you’ll also be communicating with a guy who is very approachable, who knows way more than just his commas and semicolons, and who has a great sense of humour.
You can even try out his free sample offer so you have an idea of what you’ll get for hiring him. And if you do, please tell him Amos sent you – maybe I’ll get a discount when I need more of his excellent editing skills. 😉
As writers, I think it’s our duty to lead by example as much as possible. Even if you’re not serious about ever being published and just blog for fun, consider that every time you make a common error, the chances of someone reading your error and subconsciously registering that that’s the way to do it increase, and you’ve helped the error to spread. If you write, consider yourself one of the guardians of good language. Thomas’ succinct post hits the head on the nail.
It’s not that difficult a concept: If you have a sentence that could be divided into two sentences by removing a conjunction (a compound sentence), there must be a comma before that conjunction. This isn’t optional. This isn’t a matter of personal taste.
It is also a good idea not to use a comma after a conjunction-type word at the beginning of a sentence. If you’re going to start a sentence with but (usually fine in informal writing, which is what fiction is), don’t use a comma after it. The same thing goes for and. After all, if you use but or and in the middle of the sentence, the comma goes before it.
Inept punctuation in a novel makes the author look bad; inept punctuation in an indie-published novel makes every other indie author look bad, too, because a lot of readers still think indie equals unprofessional. Perpetuating this misconception is
View original post 41 more words
Previously, on Amos M. Carpenter
In one of my very first posts, back in early March, I wrote about 10 common mistakes writers shouldn’t make. Spotting mistakes is one of my gifts – or curses; hard to say which at any given moment – and I’ll go over some I notice in writing of all types, from Internet scribbling to serious books.
To recap those from the last post, the five easy ones were:
- Don’t add apostrophes to make plurals
- Homonyms: “its” vs “it’s”, “their” vs “there” vs “they’re”, “your” vs “you’re”
- Using “alot” a lot
- I before E, except after C… how hard can it be?
The five that were slightly trickier:
- Careful with your tenses
- Singular “is” vs plural “are”
- Who thinks of whom
- The postfix -ward vs -wards
- Using “if” vs “whether”
Continuing on from last time, I thought I’d blog about 10 more mistakes that have caught my eye.
Five (arguably) easy ones
Like “definitely”, this is one of those words an incredible number of people just do not know how to spell. It’s not “seperete”, or “sepret”, or “separete”. If you can’t remember it any other way, think of the word “karate” when you write it.
2. Space before punctuation
I believe that some people who also speak (and read/write) French get confused on this one (because in French, you use a space before punctuation). Or they just don’t know any better. In English, there is no space before punctuation like commas, full-stops, exclamation marks, or question marks. (“No space for you!”) Of course there’s one space after them, though. With en- and em-dashes, it can be different, depending on which style guide you’re following, as some prefer to use spaces both before and after them.
3. Couple OF
Dropping the preposition “of” after using “couple” is becoming more popular. However, I’d always recommend adding the “of”, as dropping it is mostly due to writers following in the footsteps of sloppy speakers. In spoken language, of often gets abbreviated to o’, so we go from “a couple of apples” to “a couple o’apples” to “a coupl’a apples” to “a couple apples”. It’s the same with “a cup of tea” becoming “a cuppa tea” – but would you ever say “a cup tea”, dropping the “of” completely?
I recently noticed how much this annoyed me when I read Patrick Rothfuss’ otherwise wonderful books (as I mentioned in this post). He’s one of those people (or perhaps it’s his editor?) who don’t believe “couple” needs a preposition, and many times while reading his story, it jarred me enough that it broke my immersion. (He’s still one of my favourite authors. I’m a forgiving sort of person. At least when someone tells such great stories.)
4. Then vs than
This one should be very simple – use then when referring to time, use than when comparing – but many people still get it wrong. First comes one thing, then something else. Jack is taller than Jill. Simple.
5. Have isn’t of
When “have” gets abbreviated, as in “I could have” becoming the contraction “I could’ve”, it sounds like, but isn’t “I could of”. I suppose people who get this wrong just write things the way they hear it, but pausing just a second to think about it should make it obvious that the two are not interchangeable. I could of, would of, should of used could have, would have, should have.
Five more, slightly trickier
Ok, I’m sure you knew all of the above, so here are some that are just a tad more advanced.
6. Is “alright” all right?
Many careful English users would consider the shortened form, “alright”, to be less acceptable than “all right”, especially in formal writing. Some would even consider it to be an invalid word, but it can be found in some writing, mainly in the US, so perhaps it will become more acceptable in time. For now, I’d recommend sticking with “all right”.
7. Further vs farther
You’ll know this one if you’ve seen Finding Forrester. It’s easiest to remember if you keep in mind that “far” relates to (measurable) distance, as does “farther”. On the other hand, “further” is used when denoting an abstract amount of something. So it’s “set them farther apart”, but “of no further value”.
It gets tricky when the dividing line between the two isn’t immediately obvious, as in “to go one step further/farther” – you have to ask yourself whether it is a physical step (i.e. “farther”), or a metaphorical step (“further”).
8. Capitalisation of formal titles
Obviously, certain things are always capitalised (capitalized, if you prefer – in Australia, we use the “s” form, I believe both are used in the UK and the US prefers “z”), such as days of the week, languages, or countries. But what about formal titles, “honourifics”, like General, or Professor, or Queen? Are they capitalised or not? Well, it depends on how you use them. If the word is used to refer to a particular person holding that title, it should be capitalised. If it is used to refer to a group of them, or to the title itself, leave it in lowercase (with the obvious exception of being the first word in a sentence).
Thus, it would be “Professor Smith”, or even “there’s the Professor” (despite the name not being used, it’s a particular professor), but “he’s a professor at my university”, or “the professors have arrived”.
If you invent a title for your story, you should treat it the same way.
9. Full-stops (periods) after abbreviations
When do you place a full-stop after an abbreviation? Why do you sometimes see it written as “Mr.”, and sometimes as “Mr”?
In British English (similarly for AUS/NZ/SA as far as I’m aware), the deciding factor is whether the abbreviation begins and ends with the same letters as the full word or phrase. Since “Mr” does meet this criterion (mister), there is no full-stop: Mr Jones. “Prof.”, however, does not begin with “p” and end with “r” (professor), so it gets a full-stop: Prof. Jones.
In US English, I believe the full-stop is always used. Just something to be aware of when you read and write.
10. Ellipses at the end of sentences
The ellipses I’m talking (well, writing) about are the ones in creative writing that indicate the speaker trailing off, or leaving something unsaid, as opposed to those that indicate an omission in a quote.
This is one that depends on which styleguide you follow. Some argue that an ellipsis (dot dot dot) at the end of a sentence finishes that sentence, while others consider it a part of the sentence and add a fourth dot to end the sentence, just as if the ellipsis had been any other word….
Personally, I add the fourth dot, even in informal writing (e.g. in blog comments), but I think the main thing is to pick a convention and stick with it consistently.
There you go, I hope some of these common mistakes have refreshed your memory of what to look out for, or perhaps even taught you something new.
Which errors do you frequently commit, or spot? Which ones really annoy you when you see them in written form? Or do you think sticklers for detail (like me) should just stop with the nitpicky posts already? Please let me know in the comments!