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:
Translator training – and much discussion in professional translation circles – tends to focus on the knowledge base. At its simplest, this is competence in the source and target languages. More widely, it includes such things as technical knowledge of software applications, and knowledge of terminology in specific subject fields or institutional settings. At first sight, this seems a reasonable approach. After all, what else could training and professional discussion focus on?
I wonder whether this focus is really helpful. One of the particular challenges of translation is that the knowledge base is incredibly broad. In fact, I am tempted to say it is limitless.
There are some ways of restricting this: by working in a single language combination, in a few specialist fields or in specific institutional settings. However, as I have argued elsewhere, the real world has a nasty habit of defeating such attempts: institutions such as the EU or the UN often demand multiple language combinations, while true ‘single-subject’ texts are surprisingly rare. (Hybrid texts such as a legal contract about electrical equipment hire, the financial statements of a pharmaceutical company or a marketing text for a surf school are the norm, not the exception.)
Likewise, the focus on the technical aspects of computer-aided translation tools strikes me as missing the point. Anyone can master the basics of CAT (import, export, applying a TM, using terminology etc.) in a day or two. If you have more specific needs (e.g., because of the nature of your client base or your project management role) you can probably get to grips with the more esoteric aspects of the software in a week or two. The real challenge for a translator using CAT tools is – to put it crudely – how to stop it ruining your style. How do you avoid falling into the trap of over-literal translation that cleaves too closely to the source text? How do you deal with supra-segmental and ‘whole text’ issues such as cohesion, the need to split and join sentences, the flow of an argument, repetition and so on? You can’t do this in a day or even a week – these are challenges that will stay with you for the rest of your professional career.
If you think I am overstating the problem, I would ask you to pause and consider the following.
- In university translation courses, teaching is frequently delivered by staff who have little or no professional translation experience and whose background is in language teaching. In other words, they are ‘qualified’ by their mastery of the knowledge base (in this case, the source and perhaps target languages) not by their skills or experience as translators.
- The online training offered by two of the most widely used CAT tools – SDL and memoQ – focuses entirely on technical issues. There is simply no mention of the ‘soft’ skills that I refer to above and which I think are the real challenge to successful use of CAT tools.
- Translator assessment in both academic and professional settings tends to privilege ‘objective’ criteria (accurate transfer of meaning, correct syntax and punctuation) over more ‘subjective’ ones (the importance of clarity, readability and style), with the result that texts can be marked as acceptable if they do not contain any clear errors (knowledge base failings) even if they do not meet the standards of high-quality writing that is fit for its intended purpose (‘soft’ translation skills).
So what is the solution?
- Well, for a start we need to attribute less importance to the knowledge base (language, terminology, software) and more importance to how we exploit this base (through problem solving and research skills, and reading and writing with reference to sense and context). This should be built into all translator training from the very first day, and should also be put at the centre of training in specialist tools.
- Translator assessment should be adapted to reflect the realities of the translation process: translation is, among other things, a subjective, aesthetic activity and assessment needs to take this into account.
- We need to balance our emphasis on specialisation with a recognition both of the limits of such specialisation and of the fact that, whatever the degree of specialisation, this can never negate the need for a more craft or skills-based approach.
*I have borrowed the title of this post from a wonderful song by Si Kahn. You probably won’t be surprised to hear that the song is not about the translation profession. Or at least not directly. The song is about human dignity, making best use of your talents and doing right by others. And that, ultimately, is also what this post is about. Here’s a rough but beautiful version of the song by Ben Grosscup:
I blogged the other day about how a single text can often cover a range of specialist subject areas, and suggested that the whole idea of subject specialisation for translators may have been oversold.
When we are not being urged to specialise by subject area, translators are generally encouraged to find direct clients. There is usually an assumption that the two go hand in hand: that your client will be active in a particular sector and will generate texts in the associated specialist area.
But if the idea that individual texts can be categorised by subject area is often questionable, then the notion that clients will helpfully stick to their own chosen industries when producing copy strikes me as wishful thinking.
I do a lot of work for a large pharmaceutical company. This morning I’ve been despatching a batch of short texts for them. Here’s what I’ve done so far today:
- an email regarding malfunctioning public display systems
- a press release on an architectural prize
- an internal item about a professional seminar on coagulation therapy
- an internal item about a professional seminar on pharmaceutical technology
So, at least four different fields (IT, architecture, clinical medicine, medical technology) and three text types. What’s more, although all of these texts required me to decipher some technical content and identify the correct target language terminology, in every case the real challenge was more general: to work out the meaning of the source text (both technical and general) and to find the most elegant and culturally appropriate way of expressing the author’s message in English.
I sometimes worry that the focus on specialisation leads new (and not so new!) translators to assume that the biggest challenge of any text is to match the correct target language terminology with the source terms. Of course that’s important, but we shouldn’t allow it to obscure the often far more challenging ‘general’ issues of style and meaning that cut across specialisms.
The standard advice to any translator trying to move upmarket is to specialise. It obviously makes sense – you should be able to produce a better standard of work, command higher fees and build stronger relationships with your customers. However, I sometimes wonder if this advice gives the misleading impression that the translation industry (and the world) can be separated into distinct niches.
I am currently working on an expert witness opinion for a claim for damages.
But legal texts are never just legal: laws, disputes, contracts are almost always about something in the real world (the exception, I guess, are laws whose sole purpose is to regulate the legal system). In this case, the expert witness opinion is about an industrial property dispute.
So it’s industrial property.
Not so fast. This industrial property dispute is between two (groups of) pharmaceutical companies.
So it’s pharmaceuticals.
Or maybe not. Most of the details of the expert witness opinion actually relate to the financial impact of the disputed behaviour in terms of loss of earnings, impact on market share and so on.
So my legal text is actually a legal-industrial property-pharmaceuticals-corporate finance text.
The world is a messy place. And sometimes the translation industry is, too.
I should start by saying that I’m not keen on the whole concept of “person as brand”. (And one of the many benefits of not being brand-conscious is that you’re less likely to commit any of the crimes listed below.) However, the reality is that many translators are on Twitter to consciously build their brand, and there’s certainly an argument that, simply by connecting with colleagues and with existing or potential clients, your “brand” is at stake even if you deny its very existence.
Having got that caveat out of the way, here are some of my least favourite ways in which some over-enthusiastic advocates of personal branding are using Twitter (and helping to ruin it for the rest of us!).
I’m surprised at the number of translators who think it’s acceptable (let alone desirable) to post a generic advert for their services on a daily basis. This:
- will annoy your followers
- will give the impression that you are desperate for business
- will negate any impact that a well-designed advert might have.
There seems to be a category of translator who has decided that the best way to project a professional image is to flood their Twitter feed with articles about marketing and business techniques. If you genuinely have insights to share, then please do so. (There are plenty of translator-entrepreneurs out there who have a lot to teach their colleagues.) However, if all you are doing is rehashing yet another tired list of “marketing tips”, “advice on obtaining direct clients”, “looking after your customer”, then please don’t. You will fool nobody.
Another common Tweet runs along the lines, “X% of the world’s population don’t read English. Why you should translate your website.” Who is this aimed at? Most of the followers of any translation-focused account fall into one of two camps: members of the translation industry (translators, LSPs, clients etc.); others (friends, family, social connections, old schoolfriends etc.). The members of the first camp have already got this message. The members of the second camp are not interested in it. Repeating the message ad nauseum will just annoy both groups (and make you look like an idiot along the way).
So what should people post? A good starting point is to restrict yourself to content that ticks at least one of the following boxes:
In other words, instead of “building your brand”, just behave like the kind of human being that others might want to interact with. After all, we spend a lot of time saying that human beings are better than computers when it comes to translation. And we’re better than brands, too.
I love this from Michael Hofmann. There is really a whole philosophy of translation packed into this one small paragraph.
One of his guiding principles for translating, he says, is to avoid the obvious word, even if it is the literal equivalent of the original. When the opening page of a Roth novel contained the word Baracke, he insisted on going with “tenement” rather than “barracks”. In the second paragraph of Hofmann’s version of Metamorphosis, Gregor Samsa doesn’t ask “What happened to me?” (Was ist mit mir geschehen?), but “What’s the matter with me?”. He liked the phrase, he says, because it sounds like someone having trouble getting up after a heavy night. “Nobody will notice, but you have taken a step back from the original. You have given yourself a little bit of self-esteem, a little bit of originality, a little bit of boldness. Then the whole thing will appear automotive: look, it’s running on English rather than limping after the German.”
The quote comes from a longer article in the Guardian, which is well worth a read.
In February 2002, Donald Rumsfeld, George Bush’s Secretary of Defense from 2001 to 2006, was asked about the evidence linking Iraq to weapons of mass destruction. He famously replied “there are known knowns; there are known unknowns; and there are unknown unknowns”.
The remark was widely mocked at the time as a nonsensical attempt to justify the subsequent invasion of Iraq, the “unknown unknowns” turned out not to exist, and the consequences of the invasion are still playing out in Iraq and across the Middle East today.
However, if instead of talking about non-existent chemical weapons factories, Rumsfeld had been talking about translation research, his point would have been a good one.
In translation we have:
- known knowns: words, phrases, real world knowledge etc. of which we are certain – no need to research this
- known unknowns: words, phrases, real world knowledge etc. of which we are uncertain – we always need to research this
- unknown unknowns: words, phrases, real world knowledge etc. that we think we have understood but which actually contain different/additional meanings.
The problem is that, by definition, we don’t know when our source text may contain “unknown unknowns”. As a result, we don’t realise that we need to research them. The solution, fortunately, is simple:
“Research everything about which there is the slightest cause for doubt, including all real world information, any parts of the source text where your understanding clashes with the context or with a common sense interpretation, and any phrasing in your translation that you suspect of being influenced by the source text.”
In other words, if in doubt, Google it. And, in the spirit of Donald Rumsfeld, if you’re in doubt about whether you’re in doubt, then you should still Google it.
A personal bugbear of mine is text that reads as if it has been written by a robot. One example that springs to mind is the use of the formula “and/or”. Logically, this make perfect sense – “apples and/or oranges” technically provides three options: “apples, “oranges” or “apples and oranges”. However, most humans are perfectly capable of understanding, based on context, when the apples and oranges are mutually exclusive and when the text means you can have one or both types of fruit. If you’re writing for humans, it’s best to write as if you are one.
This year I’ve added some literary translation to my Spanish translation workshop for the M.Sc. students at Heriot Watt. In the process, I’ve been hunting around for relevant resources, so I thought I’d gather some of them together here: