Showing posts with label editing. Show all posts
Showing posts with label editing. Show all posts

Thursday, 5 July 2018

Trump and sensitive editing

Trump (who I don't blog about much because I don't think it's helpful to criticise his poor command of language when he is so unbelievably awful in so many other more important ways) has been mocked on twitter again. He used the phrase [they] pour over my tweets rather than pore over. This is a very common mistake; lots of perfectly intelligent people also make it; it's not transparent enough for it to be a thing you could work out. You just either know it or you don't. In most uses, pore is a little hole for your skin to breathe through, so it's not obvious why it should mean 'gaze intently', and in fact we don't know where that meaning comes from - we just have it recorded in early English writing and without a known origin. So I'm not going to beat Trump up for not knowing that, but the internet did. The problem was that he used it in a tweet where he explicitly said how good his written English was, and a version of Muphry's Law states that if you write anything praising your accurate writing, there'll be an error in it.

So let's look at this positively. Lot's of people just corrected the spelling of pore, others pointed out other less-than-brilliant aspects of the writing in the original tweet, but this person, a writer himself, edited the tweet to read much better:

There's a commonly-criticised error in the original tweet, which Michael hasn't fixed: the dangling participle(s) at the beginning. Normally, people are keen to point out the comedy of such constructions (Plunging hundreds of feet into the gorge, we saw Yosemite Falls). But in this case, it's fine: the potential confound is it, which is what we call an expletive, which means that it doesn't mean anything so you can't accidentally interpret the modifier as modifying it. And it sets up the context for the rest of the tweet nicely, so it's a perfectly acceptable construction.

Secondly, Michael has actually introduced a split infinitive (to constantly pore). I'm a big fan of these, especially if they make a sentence read better, which they often do, and which it definitely does in this case. It's not the liking that's constant, it's the poring, and the rhythm is also nicer in my opinion.

I like this sensitive editing with attention paid to how the tweet sounds and no rigid adherence to the rules given that it is a tweet. If you're an editor for a newspaper whose style guide says no split infinitives, then you must remove all split infinitives and that's it. But if you do have a choice, then it's good to be able to use them where it improves a thing.

Wednesday, 28 June 2017

For certain it's categorically a tautology

Here's post number two in the series from Jo Nesbo's The Leopard. In this extract, one character says "I know for certain of others with the selfsame reputation who categorically are not" (my emphasis).


The other chap tells him that using both the expressions for certain and categorically is a tautology. It's not, of course. They do mean the same thing (here, at least - categorically can also mean other things), but they don't refer to the same bit of the sentence. For certain applies to know, so Gjendem is certain about the state of his knowledge. Categorically applies to are not, i.e. to their state of being rather than to his knowledge. This doesn't mean that an editor might not suggest rewriting for stylistic reasons (after all, it means the same without either phrase), but it's not a tautology.

Saturday, 28 December 2013

RT, MT, and I was like OMG

A tweet from the Invisible Woman made me think about attribution and reported speech:


Just in case you don't tweet, I'd better explain what's going on here. The Invisible Woman has tweeted her own comment, *speechless with delight* (the asterisks mean that she isn't saying it, it's an action, state or feeling). The rest of the tweet is from Corrie Corfield, which Invisible Woman has repeated - RT means 'retweet'. Now, retweets may just consist of the original tweet, repeated in order to bring your followers' attention to it, or they may, as here, have some comment added. Either way, the RT means that the tweet is quoted as it originally was. You might modify the tweet slightly, by removing some content to make it fit or editing it somehow, and then the normal rules apply (preserve the original intent) and you use MT ('modified tweet'). IW uses RT, so we can assume the tweet is verbatim.

Corrie replies, however, to the effect that she didn't in fact put it like that, and I checked her timeline and it appears that none of the tweet is hers. RT isn't really appropriate here, then. She did, however, say something to this effect, so the original intent is preserved. Should IW have used MT? I would say not, actually, because modified tweets tend to be edited only slightly. It's similar to quoting or paraphrasing academic authors: if you put it in quotation marks, the words are the original author's. You can edit them very slightly, by missing out some words that are not needed for your purposes, or adding in a clarifying bracketed phrase to replace a pronoun that's not clear in context, but no more than this. Any more serious changes and what you're doing is paraphrasing, not quoting. Retweeting is quoting, and MTing is quoting with minor editorial changes. We need a convention to indicate paraphrasing that allows us to use it in 140 characters or less.

It's similar to the use of 'like' for reported speech, maybe. If you say (1) below, we can reasonably safely assume that those were more or less her words. If you say (2), we don't have that security. (3) is more like (2) than (1) in this respect, in that it conveys her message but not necessarily her words. This is an oversimplification, but perhaps this is how RT and MT will come to be used.
(1) Phyllis said "I really hate Bertha".
(2) Phyllis says she really hates Bertha.
(3) Phyllis was like "I really hate Bertha".

Wednesday, 20 June 2012

When is a draft full?

I've got a note on my calendar that says I intend to have a full draft of my PhD thesis ready by the end of this month. I don't know if that will happen, because I don't know how I'll know when it's a full draft.

I know some people write a draft and it's very rough, and then they go back and edit it, and edit it again, and eventually it's a nice polished version. This is a good way to write, as it means you improve it several times until it's as good as it can be. When I write, I get bored very quickly and don't really fancy going over and over it. I know I have to edit and proofread, so I do, but I do it minimally. So my finished versions are usually not that much different from the first version. (Luckily, the first version is awesome. Ahem.)

With a thesis, you can't help but edit to a greater extent, I suppose, and some sections have been moved around and tweaked to show something different, but then there are whole chunks that I wrote in one go and haven't been back to since. All of these count as first draft material to me.

So how will I know when the cut-off point is, when I've got a full draft, but not a finished thesis? Do I have to have filled in all the gaps and written all the sections? Because once I've done that I'll be fairly close to finishing and it's not going to happen by the end of the month. Is it OK to have notes to myself in it, saying things like 'find out if this is true'? Because that means there's more research to be done, and it's not a full draft. Or is it OK to have the majority of it written, but a few bits still to fill in?

The other issue is that I'm not doing what a lot of people do, and writing one chapter at a time. I've got all my chapters partially written. I would like to have completed each in turn, but that's not the way it worked.

I feel like I want some kind of cut-off marker, a goal to aim at, other than 'finishing'. So I think the solution is to say that a 'full draft' means not having bits to fill in, having done all of the sections and only needing to edit the text that's already there. So I'm also going to move that deadline to a bit later on, I think.

Sunday, 7 August 2011

No evidence for Muphry's Law

By the rule of Muphry's Law, this Daily Mail article ought to be chock-full of errors, as should the comments. It's about 'Grammar Man', who has been taking a white marker to the graffiti in Kent, correcting the punctuation and grammar. Here's the example all the papers have been using:


The article notes that Grammar Man is himself committing an error by using a capital L in the phrase 'English Language', and unnecessary capitals throughout his corrections.

Muphry's Law states that if you write anything criticising editing, proof-reading, and general lapses in writing skill, there will be an embarrassing error in what you've written. Grammar Man has indeed fallen prey to it, but it's somewhat astonishing that not only is the article itself clean, as far as I can see, but so are the comments (apart from deliberate errors for 'comedy' effect). One commenter does think that 'misspelled' in the headline ought to be 'misspelt', but I think that's allowed variation.

We must conclude that Muphry's Law is not universally true. More on the news story here.