RSS

Can I edit what I am not? Editing outside your direct sphere of knowledge

24 Feb

DictionariesThis year so far, I’ve worked on, among other things, a book about Black history in the UK, incorporating a number of responses in prose, poetry and rap which reflected the spoken norms of inner city youth; a project about (very) experimental architecture; and a book giving advice to gay men on dating and relationships. I’ve transcribed interviews with bands I know nothing about, and I’ve localised texts about items I’m never going to use. As a straight, white woman who is not an experimental architect, doesn’t follow those bands and is unlikely to use a remote-controlled helicopter, should I have engaged with these texts where I was quite clearly the “Other” in the relationship or knew little about the topic? Or should I stick very closely to what I know?

I think it’s fine to edit and otherwise work on texts that are outside your direct experience, as long as you’re flexible, keep the audience in mind, are willing to learn and keep an open mind. I also think that there are limits to what you can work on, and I’ll talk about that, too.

Why I think it’s OK to edit outside your direct experience

It’s my personal opinion that it’s OK to edit texts that are outside your direct experience, as long as you bear a few things in mind.

  • Be flexible. The language of an inner-city rap poet might not be the same as your own casual register, let alone the register you use for formal academic writing. Think about the conventions of what you’re working on, not your own preconceptions, go with the flow and keep things consistent and clear (which is the editor’s mantra anyway)
  • Be open-minded. The advice given in a dating book on apps for hooking up with people might be way beyond your comfort zone as a happily married, middle-aged woman, but that doesn’t mean you’re right and it’s wrong, or bad, it’s just different. Which leads on to …
  • Think of the audience. What will the readers of this book want? Is the relaxed style with all the I’d and should’ve contractions something that they will feel more comfortable with? Leave those in.
  • If you’ve got a good amount of life experience and a solid general knowledge, that will see you a long way into an unfamiliar topic.

Why I think it’s positively GOOD to edit outside your direct experience

The good editors I know are wise in knowing what they don’t know and seeking to expand their knowledge. They love to learn. What teaches you more than grubbing around in the very innards of a text on something you never even knew existed? There are other positives, too.

  • By approaching the text as the “Other” (while retaining a sensible approach to the privileges you might have as someone who is not usually the “other”), you might be able to suggest subtleties or pick up on attitudes that are going too far the other way. Maybe you can help reassure an author and their readers that people outside the core audience DO understand / empathise.
  • More importantly and commonly, the aim of all writing should be to be clear and express its author’s intentions clearly. So if you, as an outsider, don’t understand the text, maybe it does need to be simplified a little. If I don’t understand something on the second or third go, I’ll pop a comment in the margin that this might need to be clarified.
  • I think I have a tendency to edit better and more carefully when I’m working on something slightly unfamiliar. It’s like editing your own writing: if you really know the topic, you tend to see what you expect to read, and may skim over errors. I know I have this propensity, so I work extra hard on texts on known topics, and try not to enjoy the process too much at the expense of doing a good job!
  • You learn all sorts of things that might be useful in your everyday life, the next thing you edit, or even pub quizzes. Your next client will benefit from that extra knowledge (or maybe the one after that – I edited a load of texts on Agile working a few months ago, so can cheerfully say I know all about it when another prospective text comes in).

When I think it’s NOT good to edit outside your direct experience

There are some occasions when I do think a text is best left alone. Complete incomprehension of a technical topic or genre is not going to make for a good editing process. I pass those jobs along to a colleague (and get some co-opetition karma in the process). Examples in my own work of jobs I’ve turned down have included:

  • A book all about optimising your motor vehicle engine use, with lots of diagrams and examples. I know nothing about this, and there was little value I could add to something so technical.
  • A localisation job where I would have had to research European legislation on a topic I knew little about to start off with, and match it up to US legislation. That’s too dangerous to mess with.
  • Editing novels in genres I am not familiar with myself such as romance and science fiction – you do need to know your genres if a book is to be edited to fit into them. I’ve actually pretty well stopped working on fiction apart from the odd thriller for an on-going client, as they are pretty well all in genres where I know someone else will do a better job.
  • Specialised transcription – medical and legal in particular. I’ll cheerfully type about makeup I don’t wear or economic policy that can be checked easily, but I don’t go near the specialised terminology used in medical and legal transcription.

In summary … in my opinion, it’s good to stretch the boundaries of the areas you work on and to edit and otherwise work with texts on topics that are unfamiliar, unless the level of technical or specialist content is high enough that you are floundering and uncomprehending. In that case, there’s always someone who  knows more about the topic that you can pass it on to. Happy learning!

What are your thoughts on the subject?

 
 

Tags: , ,

4 responses to “Can I edit what I am not? Editing outside your direct sphere of knowledge

  1. Elizabeth

    February 24, 2016 at 2:18 pm

    I agree 100% with your assessment. In the dawn of home computers, my husband wrote a newsletter about how to use them. I was the perfect person to edit as I knew NOTHING about them and I could tell him immediately if he needed to add more info or tone down the tech jargon. Now as an architect, I work in an office of engineers who work on space projects. I tell them up front I can edit for grammar, punctuation, and general common sense, but I cannot edit and advise whether acronym ES4 should be ER3. I will, however, comment if they have been discussing ES4 and suddenly ER3 shows up.

    Like

     
    • Liz Dexter

      February 25, 2016 at 5:17 pm

      Thank you for that comment – it sums it up perfectly! I was wondering if I’d gone out on a limb here, but I seem to be getting a good response!

      Like

       
  2. Monocle Editing (@MonocleEd)

    March 9, 2016 at 2:40 am

    You make a lot of great points here. I recently started getting a lot of leadership/business books from a client, but they were SO foreign to me and the jargon drove me nuts. I nearly asked the PM to stop offering me these projects, but I persisted (partly because they pay really well). Just recently I caught some proper name errors that I would never have if I hadn’t seen them over and over in these books. In an industry that doesn’t specifically include “fact-checking” with every “copyediting” assignment, these are an added value where just a little bit of experience goes a long way toward an author saving face.

    Like

     
    • Liz Dexter

      March 9, 2016 at 7:06 pm

      I’ve had the same kind of thing happen to me – editing lots of stuff on Agile Working so I could catch more than just the basics in the nth document I got on the subject!

      Like

       

I love hearing from my readers - do please leave a comment!

This site uses Akismet to reduce spam. Learn how your comment data is processed.