Although I was pleasantly surprised by the overwhelmingly positive reaction to my last blogpost, it wasn’t universally liked. (No bad thing: if nobody disagrees with you, what you’ve said probably wasn’t worth saying.) The most substantial criticism was a remark on Twitter to the effect that it was unethical of me to criticise a fellow translator’s work without giving them the right to reply.
I don’t agree, but I don’t think it’s a trivial point. After all, I can certainly imagine criticising a colleague’s work in an unethical manner, so what are the defining features of ‘ethical translation criticism’?
Let’s get the ‘right to reply’ issue out of the way first. There are several objections to this.
There’s no other sphere in which we would apply this test. We don’t demand that writers critically reviewing a colleague’s novel offer a right to reply, or that the retired footballer who comments on the state of play at half-time offer a slot to the goalkeeper who has just conceded a soft header. (In fact, there seems to be general recognition that the book review industry is already in something of a crisis due to friends and acquaintances reviewing each other’s work. I think we can all guess what would happen if you had to get the author of the reviewed book on board as co-author of your review every time you wanted to say something negative.)
There’s something slightly worrying about the phrase ‘fellow translator’. Does this mean that the stricture only applies to reviews between translators? (I’m guessing so because in practice there would be no way of enforcing it on writers and commentators who publish reviews in the press.) I’m all for a bit of solidarity but this arrangement smacks more of the medieval guild than of the trade union.
I’m also unsure how the rule would work in practice. I don’t have a hotline to Ann Goldstein (the subject of my last piece) or any way of contacting her. Applying this rule would at best slow down the work of low-status critics like me and at worst simply render it impossible. (The ‘same’ bar, needless to say, would be far lower for a well-connected translator or someone writing in a commercial publication. Make of that what you will, but to me it smacks of one law for the powerful and another for everyone else.)
Balance of power
This brings me onto my next point. Ann Goldstein already has a right of reply, if she wants it. She has direct access (as far as I know) to the Guardian and the New Yorker, and I’m guessing she could easily contact other publications as well. If she decided to post a blog I think it’s fairly certain that it would have greater reach than the double-figure retweets and handful of likes that is the most my own humble post can aspire to.
My last point is very straightforward. My post was my piece of writing. As long as it is not unethical in other ways (see below), then it is for me and me alone to decide what I write and whether or not to invite others to participate in that process, to respond to it and so on. By posting on social media, I am already providing a platform where anybody who disagrees with me can reply if they so wish.
I hope I’ve convinced readers that the right of reply is an ethical red herring (and one which would, if applied, have the effect of making criticism virtually impossible), so let’s get on to the broader issue of what might constitute ethical translation criticism. Anyone who read my last piece will know that I like a good maxim, so here goes.
- Be accurate
Don’t say things that you don’t believe to be true or for which you have no evidence.
- Be fair
Don’t use accurate examples to paint an overall picture which is misleading. Anyone can cherrypick the odd mistake from a full-length novel or quibble with specific phrasings in a text which is generally well written.
- Be clear
It’s easy to take a swipe at a translation, but if you’re going to criticise it then you need to show why (in your opinion) the translation is unsuccessful. You can’t just say “the translator gets things wrong” but have to show what those things are and explain why. An intelligent reader should be able to read your criticism and dispute your conclusions on the basis of the evidence you provide.
- Don’t be personal
If you’re criticising someone’s translation, stick to the text. There may be grey areas; if the translation appears to be poor because of lack of knowledge of the source language, then it’s obviously okay to discuss that and even to produce biographical evidence to back up your point, but that shouldn’t be used as a pretext for character assassination.
- Be commensurate
If you believe you have shown that a piece of work is truly awful, it’s legitimate to reach strong conclusions on that basis. If all you have identified are a few minor slips and the odd stylistic infelicity, then it would be unjustified – and unethical – to reach a damning conclusion.
All of which leaves me a little perplexed as to why some have taken exception, in principle, to my expressing strong criticisms of the work of a named translator. I think that the problem – as we translators love to say – is context. Perhaps a joke might help to understand what is happening.
A community of nuns live in a closed convent. The community has a strict rule of silence which is only broken once a year, on Christmas Day, when one nun is allowed to stand up at the end of the meal and utter one sentence.
At the end of Christmas dinner on the first year, Sister Antonia stands up. “I don’t like the food,” she announces. She then sits down and the convent lapses into total silence for another year.
At the end of Christmas dinner on the second year, Sister Josephine stands up. “The food’s alright,” she says. She then sits down and the convent lapses into total silence once again.
At the end of Christmas dinner on the third year, Sister Agnes stands up. “I’m leaving,” she declares. Her fellow nuns are so shocked by this revelation that they forget their vow of silence and all shout “Why?” in unison.
To which Sister Agnes replies, “There’s too much arguing about the food.”
The problem, of course, is not the amount of argument but the amount of silence.
And I wonder if that is the real problem in the literary translation community. Compared to other translators (technical, medical, corporate or whatever), literary translators talk surprisingly little about the craft of translation, about the nitty gritty of which translations are good, bad or ugly, and why.
Instead, literary translation talk (at least on social media) is dominated by prizes, books, grants, conferences and the like. And most direct comments on translations take the form of encouraging remarks: “Another fabulous translation from the talented…”
That’s nice, of course, but it means that when someone expresses critical opinions about a fellow translator’s work, there is something slightly shocking about it, as if a taboo had been broken. The critic, to quote Billy Connolly, can feel about as welcome as a fart in a spacesuit.
The best response to this problem, in my opinion, is not to strengthen the taboo further, but to fill the critical silence with translation chatter. (Or, to stick with the Big Yin, to accept that the odd fart is a price well worth paying if we are to reach the moon.)
I’ve tried to do this myself by consciously engaging with authors, fellow translators and source language readers in the discussion of issues I’m struggling with in whatever text I happen to be working on at the moment. Perhaps if we all did a bit more translation talk, we wouldn’t be quite so shocked to hear the occasional critical opinion.
And I absolutely promise that my next post will focus on some words that I am struggling to understand in one language and some meanings that I am struggling to express in another.
In the meantime, here’s a picture of some nuns:
I’m not a fan of Translation Theory. Translation is a very practical activity: it involves making judgements about the meanings and connotations of a text and deciding on the best way to convey these into another language. A good solution for one problem in one situation may well be a terrible solution when applied to an apparently similar problem in a different situation. At best, Translation Theory helps translators identify starting positions from which to solve problems; at worst, it provides them with highfalutin justifications for bad solutions.
Personally, I’d swap all the Translation Theory in the world for a few good maxims. And if I was only allowed one maxim (my Desert Island maxim, so to speak) it would be this:
“translate meanings, not words.”
It would be great if we could train translators just by shouting this at new members of the profession, repeatedly and at ever higher volumes, like a British tourist on the Costa del Sol. Unfortunately, life is never that easy.
So the first thing we need to do is to add some clarification. The key word in this maxim is ‘meanings’ and by meanings here, I refer not just to the referential meanings but also to all the other connotations of language: style, register, literary effect and the like.
Even so, this maxim is hard to apply. Most novice translators default into literal translation. When you point out that they have ‘translated the words, not the meanings’ they often stare at you blankly. And when you suggest that some passages of their translation are awkward, unclear or even nonsensical, they are wont to reply along the lines of ‘but that’s what it says in the original.’
So I’d add some practical advice to this maxim:
“Read your translation as you produce it. Reread it once it’s complete. Read it again once you think it’s perfect. If the style is awkward, change it. If the meaning is unclear, clarify it. If you find yourself writing nonsense, either you’ve badly misunderstood the source text or expressed yourself poorly. And if the reader needs to understand the source language to decode your translation, you haven’t done your job.”
Any decent professional translator will recognise all of this as something that they do instinctively, so much so that it feels like common sense. How else could one translate? Well, if you want to see what happens when somebody translates without applying this approach, try reading Ann Goldstein’s translation of Elena Ferrante latest column for the Guardian.
It’s quite short (just 400 words – one or two hour’s work for a translator) but manages to pack in a series of errors, including at least one which is catastrophic.
The subject of the article is laughter and how this provides temporary relief from the constraints of our lives. Ferrante introduces her topic with a childhood anecdote.
“I remember a design that was very amusing to me as a girl. You have to imagine the sign that prohibits honking: a trumpet in a circle, crossed out by a diagonal strip. Next to it is a convertible, and a slow-moving pedestrian who keeps the car from proceeding. The driver is leaning out over the windshield and playing the violin in the pedestrian’s ear. I laughed, and my girlfriends said: ‘Why do you find it so funny?’ ”
I read this a few times and really couldn’t make out what was going on. What was this ‘design’ that so amused the young Ferrante? It sounded like a road sign. Did 1950s Italy specialise in humorous road signs? It seemed unlikely. And then I remembered that the word disegno in Italian doesn’t usually mean ‘design’ at all, but is more typically a drawing and, by extension, a cartoon. The next two paragraphs are devoted to further discussion of the ‘design’ but unless the reader has realised that Ferrante is actually referring to a cartoon, they don’t make much sense.
Now, it’s true that any translator can unthinkingly reproduce misleading cognates in their target language. Not for nothing are these words called false friends. A decent translator, though, quickly develops the habit of questioning such cognates and will often instinctively avoid them. Fortunately, when really treacherous ones slip through, they’re easy enough to spot. One review of Goldstein’s version above should have alerted even the most lackadaisical reader to the glaring error.
If you manage to struggle through the first four paragraphs of the article (and I’ll come back to a couple of other issues in a moment), you will then meet the following sentence:
“Laughter for me can do only this: stretch what is tense to the point where it is unendurable. Otherwise it seems to me overrated.”
At first sight, this sounds reasonable enough. Until you stop and think. Is Ferrante really saying that this (stretching what is tense…) is the only thing laughter can do? That’s what Goldstein’s version says, but laughter can, undoubtedly, do lots of other things as well. Either Ferrante doesn’t know about laughter’s other qualities, or what Goldstein was trying to say was:
“Only laughter can do this…”
(Laughter can do other things as well, but there are no other phenomena capable of stretching what is tense.)
That makes much more sense, and is confirmed by the next sentence:
“Otherwise it seems to me overrated.”
If, as Goldstein has it, there is only one thing laughter can do, then the ‘otherwise’ is somewhere between superfluous and just wrong. If, as I assume Ferrante had it, laughter has at least one unique quality, then the ‘otherwise’ makes perfect sense: despite this quality, laughter is not all it is cracked up to be.
Again, reading the translation for meaning would have picked up this problem immediately, and even an inattentive translator should have been alerted by the glaring non-sequitur that was a side effect of the initial error.
There are, in my opinion, at least two more clear errors in this text. In the penultimate paragraph, Ferrante/Goldstein writes:
“Ridicule, yes, annoys the powerful, but it doesn’t bury them. Yet for the moment we’re laughing, we feel their grip on our life relax a little.”
In context, we understand that ‘for the moment’ means ‘right now’. But it’s odd. ‘For the moment’ in English usually means, ‘at this time (and until something changes)’. For example, “I’m quite happy in my job for the moment (implication: but I might look for a new one next year).” Here, there’s a minor slip in meaning but context forces the reader to correct it almost without realising.
And in the final paragraph, Goldstein has:
“That must be why the laughter that interests me most, in the context of a story, is incongruous laughter, the laughter that explodes in situations where laughing is inconceivable, in fact seems an enormity.”
Here, the meaning is clear enough, but the grammar is all wrong. The simplest fix is to replace the comma after the second instance of ‘laughter’ with a semi-colon. Again, most readers will do this on the fly, reading the erroneous comma as if it were a semi-colon or a full stop, probably without even realising they are doing so. That’s fine – but there’s another way of looking at this, which is that a shoddy translation is forcing the reader to do work that the translator really should have done for them.
The problems with Goldstein’s translation, though, don’t stop at these errors of meaning and grammar. There is also something forced about the structure of many of the sentences. Let’s go back to that first error:
“I remember a design that was very amusing to me as a girl.”
Even if we correct ‘design’ to ‘cartoon’, we are left with a rather tortured structure: “…that was very amusing to me as a girl”. We know what this means but, as it stands, it’s not quite English. More natural ways of saying this might be that the young Ferrante found it funny, it made her laugh or even just that she loved it.
And once you start to notice this kind of thing, you will see that the text is peppered with these odd ‘English but not quite English’ constructions:
“…a pedestrian who keeps the car from proceeding”
“…I get on well with anyone who can come up with this type of idea”
“laughter for me can do only this”
“ridicule, yes, annoys the powerful”
Let’s call these constructions ‘Italianate’. What, you might ask, is wrong with that? After all, Ferrante is an Italian writer. The problem is that these structures are quite normal in Italian (the linguistic term is ‘unmarked’) but they are strange in English (‘marked’). There’s nothing wrong, per se, with strange or marked constructions. Indeed, without them original writing would be impossible. But there is a problem when the translator takes ‘unmarked’ constructions from the source language and routinely translates them with ‘marked’ ones in the target language. The effect is to make the original text seem stranger than it really is, and to render it unnecessarily difficult to read and to understand. It’s what we call ‘translationese’.
If you think I’m being too harsh or indulging in cherry-picking, I’d reiterate that all of this occurs in a 400-word translation that would normally take a translator between one and two hours to produce. Or, to set it in a professional context, if I was doing quality control for a client and they asked for my opinion on this text, my verdict would be that the translation, as provided, is not fit for purpose, and that they should remove the translator from their database of suppliers.
I would also suggest they pass the following feedback on to the translator:
“Read your translation as you produce it. Reread it once it’s complete. Read it again once you think it’s perfect. If the style is awkward, change it. If the meaning is unclear, clarify it. If you find yourself writing nonsense, either you’ve badly misunderstood the source text or expressed yourself poorly. If the reader needs to understand the source language to decode your translation, you haven’t done your job.”
I’ve been a professional translator for 20 years. In my time, I’ve translated academic texts, marketing texts, legal texts and medical texts, to name just a few. However, it was only about a year ago that I decided to try my hand at literary translation. Since making that decision, I have translated four stage plays, am currently working on a literary non-fiction book (due for publication in autumn 2018) and have also translated a number of fiction samples, a couple of which are being pitched to publishers in the UK and the US.
Until I started networking with literary translators, though, there was one term I’d never used to describe what I do when I’m not translating literary texts: ‘commercial translation’. For a while, I used it reluctantly (often with extra quotes around the word ‘commercial’, to distance myself from it). It seemed a convenient if somewhat stilted way of referring to non-literary translation.
But I have decided that enough is enough. Here’s why:
- ‘Literary’ translation is just one specialism among many. It doesn’t contrast with ‘commercial’ translation but with a range of other specialisms – medical, legal, corporate, marketing, academic, audiovisual etc.
- On a broad definition, all professional translation (including literary) is ‘commercial’ – you translate a text, you get paid for it.
- On a narrow definition, some forms of translation have a commercial goal while others don’t. On this definition, all of my literary translation is also commercial (there is a product – a book or a play – with, hopefully, paying customers at the end) while much of my non-literary translation (academic papers, NGO documentation) is also non-commercial.
So use of the term ‘commercial’ to refer to all non-literary translation is just incorrect. (And if you’re a translator but don’t care about words being used incorrectly, then you’re probably in the wrong job.)
Perhaps, though, ‘commercial’ versus ‘literary’ is just clumsy code for ‘easy’ versus ‘difficult’? Well, every field of translation has its own challenges:
- Many non-literary fields require detailed subject knowledge and the ability to handle both specialist terminology and in-house language.
- Working in these areas often also requires translators to be proficient users of a number of software tools: not just Word, but PowerPoint and Excel, computer-assisted translation packages such as memoQ or Trados (and their associated terminology management tools), OCR programs and desktop publishing.
- Non-literary projects often come with very tight deadlines.
- Non-literary texts are often produced by authors who are not professional writers (generating text as a side product of their job, if you like). This poses a particular challenge because these texts are frequently poorly written, and the translator may have to do a lot of editing and rewriting on the fly to spin source language dross into target language gold.
Literary translation, of course, has its own challenges. These include the need to capture the nuances of source texts that tend, by their very nature, to use language in idiosyncratic and creative ways, and the ability to produce a final translation which functions as a literary text in its own right. I’m not convinced, though, that these challenges outweigh the many challenges translators encounter in other fields.
But my real objection to the use of the c-word is that, lurking not far beneath its surface, is an attitude that smacks of elitism and snobbery, an implication not only that literary translation as an activity is more challenging than non-literary forms, but that its practitioners occupy some moral high ground overlooking the fetid swamp of ‘commercial’ activity below.
It’s an attitude that is both ignorant and patronising, but the real losers are not those of us who practise non-literary translation but the world of literary translation itself. Translation, despite what some of its practitioners may claim, is always a craft even if it is sometimes also an art. It is built on knowledge, skill and technique. And translators get better by recognising the importance of these factors and by honing them every day. Taking refuge in misconceptions about the supposed superiority of one field of translation over all others can only make that task more difficult.
I’ve just been helping a fellow translator to submit queries about her translation to a direct client, and it made me think about why we send queries to our clients.
Maybe the question seems stupid. Surely, we send queries when there is something we haven’t understood in the source text or if we are unsure about target language terminology, particularly if it might involve in-house language?
Not quite. Before submitting queries, I would ask the following questions.
Can the client reasonably be expected to help?
Seems obvious, but there’s no point asking a client who operates exclusively in the target language to help you decode the source text. Or asking a client who operates exclusively in the source language to help you resolve target language terminology issues.
How many queries do you have?
If your source text generates a vast quantity of queries, then either you have taken on a text which is beyond your capacities (your problem, not the client’s!) or the source text is seriously flawed. The latter is quite common, but the best solution is simply to make a general comment to this effect rather than to rub the client’s nose in every spelling mistake, grammatical error and logical non-sequitur. And if the text is genuinely untranslatable, then say so.
How easy/difficult is it for the client to answer your query?
Direct clients are often not language people. Vague questions (can you explain this to me?) tend to generate vague answers.
I always try to frame queries as one of the following:
- a yes/no questions
- a choice between a short list of alternatives
- a request for a very specific piece of information.
And remember that clients may not have access to the individual responsible for generating the source text. For example, I quite often translate public tender specifications. My client is an LSP; their client is a (target-language) company considering submitting a bid; the author of the text is a (source-language) government defining the conditions for that bid. Nobody in my chain has access to the author, and the timeframe doesn’t usually allow for it, anyway. So it would be pointless for me to query ambiguous wordings in the source document in this instance.
It’s also worth thinking about what benefits you can get from the query process (besides the obvious one of obtaining information to improve your translation).
Start a conversation
One of the big challenges for any translator, whether working for direct clients or LSPs, is to build a relationship. Sparing use of queries will help you to start a conversation with your client. And feel free to use the exchange as an excuse to build a more personal relationship. (I often throw in little personal titbits – where I’m off to on my next holiday, a comment about my pets or whatever.)
I’d be very wary of openly criticising a source text from a direct client, but do use queries as an opportunity to identify errors in the source text, in a non-judgemental way. For example, when translating financial reports you might be surprised at the frequency of material errors. I even alerted one client to a potentially catastrophic confusion between ‘millions’ and ‘billions’ in one text!
Blow your own trumpet
As translators, we are often invisible. People take our work for granted and only notice when things go wrong. I work for an LSP which often provides me with quite ‘rough’ source material (project documentation produced by field officers working for NGOs). I don’t generally query much in these texts, but I do usually include a comment to the effect that the source material was a little rough and ready but I think I’ve done rather a good job of turning it into something clear and readable.
Or you can use a query to draw attention to a particularly neat piece of work. I recently translated a tourism text which included the line ‘Salchichas alemanas, el arte del embutido gourmet‘ (Literally: German sausages: the art of gourmet sausage-making’). I translated this as ‘Germany – where wurst is best!‘ and checked with the client: ostensibly, to make sure they were happy with my creative approach, but really to flag up a piece of inspired brilliance in order to remind them why they needed me to translate their texts and not someone else.
Cover your back
I’m slightly wary of including this one. In fact, I think a lot of the over-use of queries by translators is probably sub-consciously prompted by a desire to avoid taking responsibility for the final product. (You can’t – it’s what you’re being paid for!) However, there are some exceptions to this rule. Where the source text is truly ropy (see above) then it’s worth mentioning it, in the politest possible terms – and perhaps rephrasing it as praise for one’s own work rather than criticism.
And where there is a specific issue which you really can’t resolve and can’t be expected to take responsibility for, then you may want that on record. I have one client who often asks me to translate software documentation while the software itself is still at the localisation stage. As a result, the target language screenshots are not necessarily available. I always flag this issue up to the client and specifically remind them that they will need to check my translations (with relevant sections highlighted) against the final target language version of the software, website etc.
The following post is based on an article I co-authored for the ITI Bulletin with my colleagues Victoria Patience and Simon Berrill.
Peer pressure: how collaborating with colleagues can be a great source of professional development
Amid all the talk of continuing professional development, translation technology, marketing skills and subject specialisation, it’s easy for us to lose sight of our biggest asset of all: the connections we can make with our fellow translators.
Tim Gutteridge, Victoria Patience and Simon Berrill all work from Spanish into English, and they’ve established a successful collaborative arrangement that spans three countries and two continents and provides them with detailed feedback on their work, career development tips… and even a bit of life coaching!
In search of quality
Tim: I’ve been translating full time for nearly twenty years but for much of that time I’ve worked in near isolation. I’d been to the odd meeting and occasionally worked with colleagues (either outsourcing or, less frequently, working on large projects together where there was some editing and feedback) but my work paradigm until quite recently was basically to fly solo. Then, in late 2016, I received a message from Victoria, a colleague I’d connected with on Twitter, asking if I’d be interested in joining a group that she was setting up.
Victoria: Around the time I wrote to Tim, I’d been hearing a lot of online talk about quality. Quality as a market strategy, quality as a way to prevent our jobs being taking by robots, quality as an end in itself. Although my clients seemed happy with my work, I had the feeling that I was churning out stuff that was good enough but no better than that. I wanted to improve the quality of my work – but how?
Simon: At the same time, but quite independently, I wrote a blog post on the issue of quality which I published under the title ‘The Quality Conundrum’. Like Victoria, I had a feeling I was producing translations that weren’t really good enough, but it seemed difficult to do very much about it.
Ideally, I would have all my translations edited by a second person, but constraints of time and money mean that’s a luxury I can rarely afford. However, without that critical editing process it’s easy to drift along and never really improve. In my post, I suggested various ways in which I might be able to improve quality, one of which I described as ‘sample reviews’. The idea was to team up with a colleague and each would review samples of one another’s work free of charge.
Victoria: I already work with a partner, María Inés Martiarena, who translates in the opposite direction to me, and we sometimes review and comment on each other’s texts. After reading Simon’s post it occurred to me that doing a similar exercise with other Spanish to English translators might be beneficial. So I wrote to Simon and also to Tim, whose tweeted translation tips were already improving my work.
Tim: When Victoria got in touch, I was already thinking a lot about the issue of quality. In particular, I was struck by the way that translator talk on social media and blogs seemed to be dominated either by a very technical approach to quality (focusing on technology, terminology and subject specialisation) or sidestepped the issue altogether in favour of discussion of business issues such as marketing and rates.
All of these are important, of course, but unless you can unpick complex ideas in the source language and express them in clear, elegant sentences in the target language, then all the technology, terminology and marketing in the world won’t make you into a good translator.
Simon: Before we actually started revising each other’s work, we exchanged a few emails to make sure we were on the same page. We were all clear that feedback needed to be robust and that it would be a waste of time if we held back for fear of causing offence. Other than that, we decided it would be best to take an open-ended approach, just sending each other work and seeing how it developed.
Victoria: We each take it in turns to send the other two a short extract of something we’ve translated, both source and target texts. These are mostly finished translations that we’ve already sent to clients, although occasionally we work on ‘live’ texts, confidentiality permitting. The two revisers have a week to send corrections, suggested changes and comments. This feedback process usually takes about an hour.
Tim: Although we refer to it as ‘revision’, we’ve deliberately been quite free in our approach. Each of us has our own style: Victoria tends to give texts a very thorough edit, I’m a bit more discursive but with less attention to detail, Simon is probably somewhere between the two extremes. Despite this, we almost always seem to focus in on the same issues in each text we review and we generally suggest similar solutions.
It’s also important to understand that the process is not really about improving specific translations. After all, most of the texts we work on are ‘dead’ in the sense that they have already been submitted to clients. Instead, our focus is on building our skills as translators so that we can produce better work in the future.
Victoria: We quickly went beyond giving advice on word choices and the flow of texts to discussing other things translators often grapple with alone, like rates, marketing and specialization, and from there to raising bi- or trilingual children, fitting work and family together, local politics, and our shared love of single malt.
Tim: When we first started out, I think we probably expected to identify a list of our own weaknesses: typical mistranslations, specific structures that we tend to overuse or misuse, that kind of thing. There has been a little bit of that, but for me the main benefit of regularly giving and receiving feedback is that it has made me much better at critically reading my own work. I often find myself looking at a sentence or a particular phrasing and asking myself, ‘What would Simon or Victoria think of that?’
Simon: I’ve had the same experience as Tim. When I’m translating a tricky text I often now imagine Victoria or Tim looking over my shoulder and encouraging me to cut a word, rework a sentence or look a bit further for exactly the right solution. I’ve learned that even translations I consider good can sometimes be ‘undercooked’ and need a little more work. It’s also been a good experience in terms of learning to take criticism – something I’ve never been particularly good at! But there’s a mutual trust involved in this kinds of exercise that puts us all on equal terms. I don’t always agree with what the others say, but I know that any criticism is constructive. And I often find myself nodding in agreement as I read their comments.
Victoria: We did consider expanding the group at one point, but in the end we decided that three was the perfect number: communication is manageable, you get more than one person’s feedback on each text, but don’t have to wait too long for it to be your turn to be reviewed.
Simon: Recently we’ve decided to vary the format and do the occasional translation slam, where we each translate the same text and then compare the results. Although it sounds simple, this is actually more difficult to structure because we really want to do more than just look at each others’ efforts and nod. We prepare our translations separately, then compile them into a four-column document to make it easier to compare the different translations. This then provides the basis for a videoconference where we analyse our translations, discuss the differences, and talk about any aspects we found particularly challenging or solutions that work well.
Tim: When we talk to other translators about this, they tend to assume it’s basically an arrangement for swapping proofreading services. But it’s really much more about professional development: improving our skills as translators, and having a place where we can share ideas with trusted colleagues. One simple example of how it’s changed my practice is that, after talking to Simon, I realised I could probably boost my output without compromising on quality. It’s easy to ignore other people’s claims of how many words they translate per day, but when the person telling you is a respected colleague and you can see the quality of his work, then you are less inclined to be dismissive and more likely to be inspired to up your own game.
Simon: We’ve got to know quite a bit about each other’s very different lives, too, which helps build trust and gives the three-way relationship a warmer, human element. When more people started asking to join us, I set up a Facebook group, the Standing Up Revision Club, to help match up others who want to establish their own, similar arrangement. More members of the Facebook group are very welcome – we hope it will lead to more translators connecting to improve the quality of their work.
You can join the Facebook group here:
In his essay, Politics and the English Language, George Orwell railed against confusing and unclear writing.
He summarised his advice in six rules, which have been the mainstay of English style guides ever since:
- Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
- Never use a long word where a short one will do.
- If it is possible to cut a word out, always cut it out.
- Never use the passive where you can use the active.
- Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
- Break any of these rules sooner than say anything outright barbarous.
Unlike writers, translators are constrained by their source text. (I also bridle at the absolute nature of Orwell’s rules.) So I have adapted them for translators:
- When translating a metaphor, simile, or other figure of speech, you don’t always need to use the direct equivalent in the target language. You may not wish to use a figure of speech at all. And if you do, try to avoid using any figure of speech that feels tired and worn out.
- When translating a source text that is packed with long words, remember that the best translation will often involve shorter words.
- If it is possible to cut a word out, consider doing so. It may make your translation clearer and more elegant.
- Avoid using the passive where the active would be a more natural choice.
- Only use a foreign phrase, a scientific word, or a jargon word if the field and register of the text mean this is the best choice or if there is no everyday English equivalent.
- Never write anything that is outright barbarous, even if the source text reads as if it was written by Attila the Hun.