Today I learned something new about journalism. According to a recent article in the New York Times, reporters sometimes use nonsense words and expressions to mark unfinished parts of articles they’re writing. For example, a busy reporter might realize that he needs a fact or statistic for an article he’s writing. Instead of stopping to look up the information, he decides to finish drafting the article. He types in TK – meaning “to come” – as a reminder to himself, and then he keeps writing.
Or – something that used to happen before newspapers modernized their typesetting practices – a reporter discovers a mistake in a piece she’s been writing. Because of the peculiar way newspaper type used to be set, she can’t fix it herself. She types in the nonsense words Etaoin shrdlu as a signal that the printer needs to look for the problem and fix it.
But sometimes those signals are overlooked and find their way into a printed article. Readers who come across a TK or Etaoin shrdlu are – obviously – going to be confused. Huh? What’s that about?
I’ve made similar boo-boos myself – for example, putting a reminder to myself into the subject line of a blog post, and then forgetting to remove it before I clicked PUBLISH.
And now you’re probably expecting a reminder from me about the importance of slowing down and carefully proofreading what you’ve written.
Or maybe – if you’re a regular visitor to my blog – you know that I try to avoid posting obvious advice, and I’m going to swerve off in an unexpected direction. (Good for you – you’ve hit the jackpot!)
What I want to tell you today is that language has an unlimited supply of tricks and pitfalls for sabotaging your earnest efforts to do quality writing.
After I read the New York Times article about TK and Etaoin shrdlu, I remembered something that happened to a close friend (now deceased, sadly) who wrote religious books for young readers. Joan wanted to write a book about Teresa of Avila, a dynamic 16th-century woman whose spiritual writings are still popular today.
Joan sent a letter to her publisher to see if they were interested in a young people’s biography of St. Teresa. But Joan (a notoriously bad speller) made an error in her letter, asking if the publisher was interested in a book about St. Theresa. Back came a letter saying the company would be delighted to have a book for young people about Therese of Lisieux, a saint Joan was not even slightly interested in.
Common sense (and the opportunity to write another book and make some money) won the day, and Joan really did write that book about St. Therese. (It’s a fine book and still in print!) But Joan never got a shot at the book she really wanted to write.
How many writing instructors have you heard droning on and on about the importance of checking your work for errors? How many literature instructors have lectured endlessly about trying to uncover the theme in a novel, or short story, or poem – or analyzing the structure – or explicating the historical context?
All of those activities are useful and important. But wouldn’t English be a far more exciting subject if we sometimes approached it from the perspective of language – that untamed force that resists our mightiest attempts to control it?
My life changed – that is no exaggeration – when one of my professors casually mentioned that he saw Bernard Shaw as a writer “struggling with language.” Those three words have kept my brain busy for years, and there’s no end in sight.
How about you? Do you ever struggle with language – or ponder how a particular writer battled against this wonderfully slippery communication tool of ours? It’s a project I heartily recommend to you!