Thursday, March 15, 2007

Translatorial Censorship

In the last post, I quoted from Dr. Marjorie Garber’s book Vice Versa: Bisexuality and the Eroticism of Everyday Life, in which she mentioned some translatorial/editorial changing/censorship (or “gender bowdlerization”) of work featuring homosexuals and bisexuals. Unfortunately, this is not a unique or altogether rare phenomenon.

In the special Translating Humour issue of The Translator magazine from 2002, in an article entitled “Francoist Translation Censorship of Two Billy Wilder Films,” Jeroen Vandaele writes about how, during Franco’s regime, translatorial censorship took place of work that was considered inappropriate or immoral. For example, Some Like it Hot might be considered amoral because of issues relating to its portrayal of cross-dressing, the potential gay implications of the movie, and other sexual topics (especially, it might be noted, sexual issues that are outside the realm of what is accepted as “normal”). Dr. Vandaele says that some of the sexual humor in Some Like it Hot and The Apartment was “changed or deleted because of immorality” or “replaced by morality,” and one can assume that if this sort of censorship happened to films, it was part of a general view of culture and society that also affected literature.

Whether for political or other reasons, translators and editors (and other people with power, such as teachers) sometimes censor or change material that they consider improper or otherwise unsuitable. I remember someone who grew up in Iran telling me about seeing foreign films in Iran and then, once she had moved to Europe and later to America, seeing the same movies and being surprised at how much longer they were; in other words, “inappropriate” material had been deleted or changed before the films were deemed acceptable in Iran.

Personally, I’m a strong believer in having as little as possible come between the audience and the text (or film or whatever) as the author (or director or whoever) envisioned it, and I hope that we translators will be cautious about (ab)using the power the wield.

Monday, March 12, 2007

Translating Homosexuality

To continue with the gender theme from the last post…

If you didn’t know it already, translation is everywhere. While reading Vice Versa: Bisexuality and the Eroticism of Everyday Life by Dr. Marjorie Garber (yes, it’s shocking, but I do actually read books on topics other than translation!), a fascinating book that I didn’t expect to relate to translation, I noticed a brief discussion of how translators and editors changed Plato’s Symposium and Shakespeare’s sonnets when they found the genders or sexual identities inappropriate or discomfiting, i.e. when they were not explicitly heterosexual.

Dr. Garber writes: “Thus the Greek word eromenos, meaning “male beloved,” became “mistress,” and the “army of lovers” that would have its historical counterpart in the famous Theban Band of warrior-companions becomes, by implication, a bevy of knights and ladies. The word “boy” in Greek was simply translated as “maiden” or “woman,” thus making same-sex love invisible to the non-Greek reading eye.” On the next page, Dr. Garber mentions Lord Byron who “like the timid translators of Greek…often chose the path of gender bowdlerization in his writing” and she creates the term “textual heterosexual” to refer to those who pass as heterosexual through this “gender bowdlerization” in their writing, or by implication, in translation.

She also points out that correct, non-bowdlerized translations of this sort of material later helped make homosexuals and bisexuals more visible and more accepted.

To be blunt about it, translators have a lot of power, and abusing it by significantly changing texts, including by deleting anything not “appropriate,” is, in my opinion, wrong.

Thursday, March 08, 2007

Gender in Translation and Other Challenges

An article by Vivian Eden includes reviews of translations of poetry from Hebrew and French to English, and Dr. Eden, herself a translator, writes that translation is a good way of conversing with and learning from other writers:

“After many years of ruminating on this conundrum, I have come to the conclusion that it is indeed possible to get dead writers to listen to you, in three steps: Read, read, read again and again; formulate your questions or observations very precisely (Do you really need that third drink?); and then again, read, read, read. The texts will tell you what you want to know and confirm, deny or comment on your observations. One of the best ways of carrying out this three-step procedure is by translating.”

Some of the issues this article, and the three books reviewed, brings up are fascinating. For example, what can a translator, whether of poetry, fiction, or non-fiction, do when faced with a word in the source text that has more than one possible meaning? How can the translator decide which meaning to highlight, which one/s to sacrifice?

And what about gender in languages? Linda Stern Zisquit, a poet, describes how she began to translate Yona Wallach’s poetry from Hebrew: “In 1982 I translated several of Yona Wallach's early poems in response to the request of a friend then editing an issue of Hebrew poetry for The Literary Review. I had reservations: My Hebrew was new, and Wallach's reputation - as a masterful poet who fragmented syntax with demonic power and broke laws of male and female conjugation - was intimidating.” The gender aspect is fascinating and it would be interesting to know how translators to and from other gendered languages deal with these issues. How can a translator represent gender, and the breaking of gender rules, in a non-gendered language? Similarly, number is something that can be played with by writers and that can be difficult for translators to portray in the target language. Ms. Zisquit includes notes in the book on the translation and challenges involved in working on Yona Wallach’s poetry, and that is a helpful idea that more translators might want to adopt.

And finally, to continue with the theme of gender, French poet Jacques Reda introduces a volume of his poetry in English translation with an implication that male and female translators are different – one wonders exactly what he meant by that. Mr. Reda, referring positively to his translator, writes: “Perhaps the convergence of these qualities comes as less of a surprise in a woman translator than in a man.”

So what do you think about these issues? Do male and female translators differ, and are they suited for different kinds of work? And what can translators do about gendered languages, numbers, and the multiplicity of meaning that some words or sounds have?

Tuesday, March 06, 2007

The Translation of Harry Potter

I may be one of the few people not to have read any of the Harry Potter books, but I nevertheless found this article by Daniel Hahn about translating J.K. Rowling’s work interesting.

He writes: “Of the 325 million Harry Potter books sold around the world, some 100 million copies don't contain a single line of JK Rowling’s prose. They’re mediated by the work of other writers who set the tone, create suspense and humour, and give the characters their distinctive voices and accents. The only thing these translators have no impact on whatsoever is the plot, which of course is Rowling’s alone.”

Frankly, I disagree with Mr. Hahn’s description. It’s rather melodramatic, and it makes it seem as though translations have very little in common with originals. The plot is the only thing he mentions, but most translators work very hard to recreate the same “tone,…suspense and humour” and other features of each text; if they are creating new tones or new kinds of suspense or humor, then it seems to me that the translation becomes a different book. Also, of course, some translators do unfortunately change the plot of books they work on. And in some cases, even if the translators don’t change the plot outright, some of the changes they have to make for linguistic or cultural reasons do of necessity affect the plot.

Mr. Hahn also touches on an issue that has been mentioned here before: the invisibility of the translator. He says: “The job of any translator requires that they be simultaneously present and absent; altogether sympathetically embedded in the work and yet totally invisible. And for the most part that invisibility is well maintained.” Today, some people disagree with this idea of translation and the related one of fluency. Personally, I wonder if the concept of in/visibility remains stronger in the translation of children’s literature than in that for adults.

At any rate, whether you are a Harry Potter fan or not, you might want to read about some of the special difficulties Ms. Rowling’s translators face, such as names and invented words. It’s also interesting to consider how today’s technology affects translation; Mr. Hahn mentions some of the requirements that making films out of these books imposes on the translators.

Thursday, March 01, 2007

Learning Welsh on St. David’s Day

Today is St. David’s Day here in Wales. David, or Dewi, is the patron saint of the country and it is believed that he died on this day in 589.

So in honor of the holiday, I thought I’d post a few links for sites that will help you learn Welsh. And just as a word of advice, Welsh is not a language to attempt to learn if you are not willing to spend a lot of time memorizing (and, yes, I know, all languages require significant study and memorizing) – together, the various verb forms, the many mutations, and all the ways you can say “yes” or “no” in Welsh make this a challenging language!

Learn Welsh on the BBC’s website

A beginning Welsh course


Enjoy learning Cymraeg!

Monday, February 26, 2007

The Humor (and Poetics!) of Mistranslations

While reading Walter Nash’s The Language of Humour: Style and Technique in Comic Discourse, I noticed a short passage on mistranslations. Mr. Nash refers to the humor that can come from the “excessively literally or misguidedly ambitious” translation. Surely we’ve all sniggered at poor translations in users’ manuals for items manufactured in other countries or while on vacation, whether in hotel rooms or on menus. Maybe some of us have even attempted to politely inform the managers of the restaurants or hotels that the translation was not correct. What’s interesting is that these mistranslations can inspire artists, as in the poem by Robert Graves referred to by Mr. Nash.

Apparently Mr. Graves noticed a badly translated tourist guide and let himself be inspired by it:

«¡Wellcome, to the Caves of Arta!» by Robert Graves

‘They are hollowed out in the see-coast at the muncipal terminal of Capdepera at nine kilometer from the town of Arta in the Island of Mallorca, with a stuporizing infinity of graceful colums of 21 meter and by downward, which prives the spectator of all animacion and plunges in dumbness. The way going is very picturesque, serpentine between style mountains, til the arrival at the esplanade of the vallee called «The Spiders». There are good enlacements of the railroad with autobuses of excursion, many days of the week, today actually Wednesday and Satturday. Since many centuries renown foreing visitors have explored them and wrote their elegy about, included Nort-American geoglogues.’ [From a tourist guide]

Such subtile filigranity and nobless of construccion
Here fraternise in harmony, that respiracion stops.
While all admit thier impotence (though autors most formidable)
To sing in words the excellence of Nature's underprops,
Yet stalactite and stalagmite together with dumb language
Make hymnes to God wich celebrate the stregnth of water drops.

¿You, also, are you capable to make precise in idiom
Consideracions magic of ilusions very wide?
Already in the Vestibule of these Grand Caves of Arta
The spirit of the human verb is darked and stupefied;
So humildy you trespass trough the forest of the colums
And listen to the grandess explicated by the guide.

From darkness into darkness, but at measure, now descending
You remark with what esxactitude he designates each bent;
«The Saloon of Thousand Banners», or «The Tumba of Napoleon»,
«The Grotto of the Rosary», «The Club», «The Camping Tent»,
And at «Cavern of the Organs» there are knocking strange formacions
Wich give a nois particular pervoking wonderment.

Too far do not adventure, sir! For, further as you wander,
The every of the stalactites will make you stop and stay.
Grand peril amenaces now, your nostrills aprehending
An odour least delicious of lamentable decay.
It is poor touristers, in the depth of obscure cristal,
Wich deceased of thier emocion on a past excursion day.

Thursday, February 22, 2007

Translating Primo Levi

Readers of the New Yorker might have noticed that quite a few recent issues have included stories by late authors, two of which were by Primo Levi. Ann Goldstein translated one of those stories from the Italian (Alessandra Bastagli translated the other one) and she talks about his work and the translation of it on the New Yorker’s website.

In this interview, Ms. Goldstein discusses, among other things, Mr. Levi’s “precise” language and his use of scientific terms; she says that she chooses scientific words in English that the reader may not know rather than simplifying them because she is aware of the fact that Italian readers, too, wouldn’t necessarily recognize all those terms. Thus, she attempts to retain Mr. Levi’s intentions.

An interesting note is that Ms. Goldstein seems to say that her first translation from Italian was published in the New Yorker. I’m sure many of us who work as literary translators, or would like to, don’t ever get published in that magazine, much less with our very first job! She is now one of the translators of the forthcoming collected works of Primo Levi.

Monday, February 19, 2007

Translation and Censorship

I’ve never compared translation to censorship before, but this interesting quote from poet Joseph Brodsky, which I noticed in the book Translating Milan Kundera by Michelle Woods, does just that:

“What translation has in common with censorship is that both operate on the basis of the ‘what’s possible’ principle, and it must be noted that linguistic barriers can be as high as those erected by the state.”

Obviously, the major difference is that censorship attempts to keep something out, whereas translation has to find a way to get around the cultural and “linguistic barriers”. That’s the challenge involved in being a translator – you have to escape the censorship that cultures and languages attempt to impose, whether they do so intentionally or not.

Thursday, February 15, 2007

Learn a New Language and Concentrate Better

Like many people, I have heard it said that those who speak two or more languages aren’t really fluent in any language. That has never made much sense to me, and when parents have used that reasoning as an excuse not to teach their children their native tongues, I have thought it was misguided and sad. Well, this recent article says that research into bilingual people suggests that they are in fact able to operate in more than one language, and also that they are better able to concentrate. So while it is true that there can be interference between or among languages (and I have certainly spoken or written the wrong language to people more than once, so I know what an embarrassment it can be), the potential benefits seem to be stronger. Hopefully there will be more research on this soon, but in the meantime, we can all safely continue learning foreign tongues!

Monday, February 12, 2007

More on the Ethics of Translation

I always find the ethics of translation to be a fascinating topic, so it was interesting to see it come up for the second time within a year in Randy Cohen’s Ethicist column in the New York Times Magazine.

In Sunday’s column, a woman writes that her father, a translator, was hired to translate pages from a diary of a woman whose husband suspected she was cheating on him. Was it ethical to translate the diary pages? Mr. Cohen says that the translation was legal, but not moral.

I agree with his assessment and I hope I would have turned down the assignment, but the fact is that translators don’t always get to see (or know much about) the work before they accept it, although certainly a translator could turn down the job once she or he sees the document in question. Also, some freelancers might truly be desperate for money and unable to say no to any work.

What do you think? Would you have accepted this job? When does something cross the line for you from being an acceptable job to one you feel obligated to refuse?

Friday, February 09, 2007

Translating Milan Kundera

In the last post, I quoted from a review of I.B. Singer’s work, which makes it clear that he rewrote as he translated, thus blurring the definition of translation. In the book Translating Milan Kundera, Michelle Woods describes how Mr. Kundera does the same thing, constantly translating his work and his biography in a variety of ways.

Milan Kundera is a Franco-Czech novelist who, it can be argued, primarily has readership though translation. Ms. Woods analyses his oeuvre and the various functions of translation within it through the prism of the four kinds of translation that she sees there: translation in the traditional sense (that is, between languages and cultures), rewriting (Mr. Kundera rewrites his books, reworks his earlier writings into later ones, and redefines his bibliography), writing (all writing can be considered translation, and this is especially applicable to Mr. Kundera, since he mostly writes for a non-Czech audience), and reception (how publishers and readers both in the Czech Republic and abroad understand and receive his work). Woods compares and studies Kundera’s Czech, French, and English writings, and uses them as a case study to understand all the different ways translation is involved in authorship.

What is interesting about Mr. Kundera, as with Mr. Singer, is that he changes his books as he reviews and works on the translations (he does not translate himself, but works with and supervises his translators closely – some say too closely. The books aren’t changed so much that they become unrecognizable, but they are clearly not just ‘straight’ translations. So they are some combination of rewriting, adapting, and translating. Perhaps we could call it transwriting, writing across cultural and linguistic boundaries.

Monday, February 05, 2007

Translating and Rewriting

Speaking of Yiddish, I noticed this review of a biography of Isaac Bashevis Singer in December. Interestingly, the biography itself is a translation, which is never mentioned, but the review does briefly discuss the translation of Mr. Singer’s work:

“Fame in America came to Singer shortly after, when The Partisan Review published his story “Gimpel the Fool.” Here too, though, sweetness came with bitterness. Saul Bellow had translated the work at the request of Irving Howe and Eliezer Greenberg. “I had seven names in all: imbecile, donkey, flax-head, dope, glump, ninny and fool,” Gimpel begins, sounding more like Augie March than someone from the old country. It’s hard not to wonder about the effect on Singer of this side door to renown. We know he never let Bellow near another story of his, doing his own translations from that time on with the help of not-so-famous assistants.

“These translations — “second originals” as Singer called them — grew to be quite different from the Yiddish texts. Singer often stripped much of the metaphysics and verbal density out of his native-language efforts, leaving a simpler mix of the imaginative and the quotidian, the carnal and the concrete, that he felt would appeal to the tastes of English-language readers. And they — especially American Jews — responded. Singer became for them an appealing combination of home-grown mystical realist and approachable modernist. In addition, he was the beneficiary of their guilt and grief over the fate of the people they had left behind in Europe.”

In other words, Mr. Singer changed his works as he ‘translated’ them, perhaps just to make small adjustments or improvements at times, and for other works, changing them for the target audience. Is something still a translation if it is a new, changed version in a new language? Where is the line drawn between translating and rewriting, or translating and adapting?

This will be discussed more in the next post.

Thursday, February 01, 2007

Books on Language – Yiddish

Continuing with books on language, this post will be on Yiddish.

I read two books on the subject not long ago, and they complemented each other well. The books were Words on Fire: The Unfinished Story of Yiddish by Dovid Katz and Outwitting History: The Amazing Adventures of a Man Who Rescued a Million Yiddish Books by Aaron Lansky.

Mr. Katz’s thick, instructive book gives the history of Yiddish, explaining where it came from, how it was used in different situations than Hebrew and Aramaic (that is, for Ashkenazi Jews; other Jews did not traditionally speak Yiddish), and how it was viewed. He also looks at Yiddish literature, who speaks Yiddish today, and other related topics.

Mr. Lansky’s book is about his personal journey with Yiddish and how he helped save Yiddish books. He was a doctoral student when he realized that as elderly, Yiddish-speaking Jews died, their children, who generally did not know Yiddish, threw out their Yiddish books. Mr. Lansky quit his program in order to save the Yiddish books, travelling around the world to do so, eventually starting the National Yiddish Book Center in Massachusetts as a library, center, resource place, and shop for Yiddish books. He has helped save over 1.5 million Yiddish books and his adventures are both fun and sad.

It was interesting to read the two books together, because first I learned about what the mamaloshen meant – and means – to Ashkenazi Jews, and then I read about Yiddish in modern times and what has happened to Yiddish books.

Let me know about other good books about languages!

Tuesday, January 30, 2007

Books on Language – Latin

To continue with the theme of books on language, I’d like to look at Latin.

I studied Latin in middle school and high school and I realized immediately that it was a really useful language for any speaker or learner of English or Romance languages (and, of course, it has influenced other tongues as well). Even though I unfortunately can’t read it today, what I remember still helps me, both as a teacher of English and also as a user of the language myself.

But though I learned the language (including all those declensions), I didn’t get a good sense of the culture surrounding it. Tore Janson’s book A Natural History of Latin fills that need. Mr. Janson explains the origins of Latin, how and why it became important, and why it is relevant today. I wish his book had been available when I was in school, because it would have helped me understand Latin in the context of its cultural and historical background.

Tuesday, January 16, 2007

Books on Language – English

As a certified “language nerd,” I really enjoy reading books about the history and culture behind languages. As a translator, you have to understand the grammar and vocabulary of a language, of course, and having a sense of the cultural is also important, but learning about the history of a language is not only helpful, but also fascinating. Unfortunately, I’ve noticed that many people who teach languages too often ignore the cultural and historical aspects, which I happen to think would entice students and get them more excited about their language learning. Language is not just a way to communicate (unless you’re speaking Globish!), but also offers a whole culture and a worldview.

In this post and the following two, I’ll write about some of the interesting books on language that I’ve read.

My all-time favorite book on English is Bill Bryson's Mother Tongue. Mr. Bryson is an excellent, entertaining author who could probably make any subject interesting. His book enthusiastically describes the history of English, how it has become a global language, and so forth, but it also includes chapters on word play and swearing, and has examples of bad English. I admit that I laugh aloud as I read (and re-read) Mother Tongue, and I’ve shared the book with students, who found it both amusing and interesting.

The Stories of English by David Crystal has a different perspective than most language books in that it doesn’t just discuss the history of standard English but instead includes many varieties of English. Hence, the title is not The Story of English but rather The Stories. Many people view the standard varieties of languages as the only correct ones (in part because that is what is taught in school), but the fact is that the majority of the speakers of any language do not speak the standard. This book looks at the development of English, in all its varieties, over time. The prolific Mr. Crystal, by the way, has recently started a blog.

What about you? Do you have favorite books on languages?

Friday, January 12, 2007

Translator Joachim Neugroschel

I happened to find an interview with translator Joachim Neugroschel, who has translated from French, German, Italian, Russian, and Yiddish, and also to German. I found some of his ideas about translation a little different from those of other literary translators. For example, he never reads a book before translating it, because he says he has “[n]o reason to.” How, then, does he decide what to translate and what to turn down? Apparently, money is the answer, as he says, “If the publisher pays me enough, I will do the translation.” Many translators say they need to feel they have something in common with the authors they translate, or at least some feeling of empathy and interest, but Mr. Neugroschel doesn’t feel it is necessary to even have much knowledge of the author’s work, because he can just “get the style” by reading a page.

Interestingly, he also claims that you can tell a bad translation just by reading it, which suggests that all you need it the target text and then you can judge the translation. Obviously, I disagree with that, and feel that you do need to know an author’s work and the source language to be able to truly judge the quality of a translation. Bad grammar could be part of the source text on purpose, so if it is in the target text, that doesn’t necessarily mean the translation is poor. Also, many other things could make a translation bad, such as if the translator has misunderstood the original document or has tried to improve it, or if the word choices don’t accurately represent it. And it is difficult for a monolingual reader to judge any of that.

As a side note, I wonder if Kafka really would find Mr. Neugroschel’s translation excellent. It isn’t that I doubt the latter’s abilities, but if Kafka didn’t even want his work published, what would he think about it being translated and made available to even larger audiences?

Here are some excerpts from the interview with Mr. Neugroschel.

Interview with Joachim Neugroschel

EG Do you read a whole work before translating? Do you translate the words literally?

JN I never read a book before translating it. No reason to. I do not translate the words literally. Only a bad translator would translate literally.

EG In order to not write a literal translation, don't you have to have a sense of an author and their work? How do you capture that uniqueness of an author and transfer it to another language?

JN You don't have to have a sense of the author's work to translate. I read a page and get the style. It is a question of music and rhythm. It is like being an actor. An actor can take on different roles. A translator takes on different roles.

EG Does anyone go over your translations before publication?

JN Yes, often a copy editor. One copy editor changed the words spiral crack to spinal crack. If you get hit in a certain way the crack is spiral.

EG How do you recognize a good translation?

JN Just read it. Grammatical blunders are a clue. Example: when it comes to adverbs, first you have place and then time.

“I went to school yesterday.” To school is an adverbial phrase of place. Yesterday is an adverb of time. This is correct usage. A phrase such as, “I'm going tomorrow to school,” is bad grammar. Poor grammar is obvious in bad translations.

EG You are taking a little of the mystery of translation away. I don't speak a foreign language; thinking about the art of translation is new to me.

JN If you don't know a foreign language, you can only judge a translation by its use of English. Think about this. Most of the books you've read are translations.

EG I never thought of that. When you think of it you are not getting the direct voice of the author. What if Kafka was around today and he knew English, what would he think of your translation of "Metamorphosis"?

JN He would find it excellent. I've captured the flavor and the quivering of his voice. He would be very grateful to me.

Wednesday, January 03, 2007

Pseudotranslations and Anti-Plagiarism

A really fascinating subject has come up in some of my recent reading: pseudotranslation. In his book Descriptive Translation Studies and Beyond,

Gideon Toury defines pseudotranslations as “texts which have been presented as translation with no corresponding source texts in other languages ever having existed – hence no factual ‘transfer operations’ and translation relationships”. In other words, it is a fake translation.

But what is the point of that? Mr. Toury suggests that this is a “a convenient way of introducing novelties into a culture” and is especially useful “in cultures reluctant to deviate from sanctioned models and norms.” He also mentions that there may be times when either translation itself or else a particular type of literature has prestige, so authors try to get in on the action, as it were, by creating pretend translations. There are also occasionally political reasons behind them, and an example he gives is of a supposed Kazakh folk singer whose work conveniently existed in Russian, but never in the original language.

After reading the “excursus” on pseudotranslations in Mr. Toury’s book, I happened to read an article on looking for literary plagiarism that described a similar phenomenon, anti-plagiarism. The article said “Literary critic Terry Eagleton has written entertainingly of “anti-plagiarism,” a 19th-century literary wheeze favored by Irish critics, who pounced on poets or novelists for plagiarizing or surreptitiously translating some little-known domestic or foreign work and presenting it under their name. The trick was that the “original” work presented by the prosecuting critic was itself a forgery, written after a new work’s publication to frame an enemy.” This article then linked to Mr. Eagleton’s on literary forgery.

Although both pseudotranslations and anti-plagiarism can seem to be a kind of literary shtick, designed to get an author noticed, or even an abuse of the form, meant to accomplish a political or cultural goal, there might be times when such a style can be successful and witty.

Monday, January 01, 2007

Happy New Year

All the best wishes for 2007, and for translators that includes interesting and challenging assignments, pleasant customers who value your work, and lots of translatorial success in general.

I’ll be taking a break from work in January, which means I’ll be posting less, but do check in, since there will still be new material.

Saturday, December 30, 2006

Inttranews

I recently stumbled on this site, called Inttranews. It has links to news on translation and interpreting from around the world, so it is a good resource.

Wednesday, December 27, 2006

Monolingual UK and Globish

As in the US, residents of the UK are not so good about learning other languages. Here are a couple of interesting articles I noticed recently about learning and using a variety of languages.

The first one, Monolingual Britain, looks at how British students have stopped studying languages as much as they used to, in part because of the sense of English as the world language, and the idea that everyone speaks English. Sound familiar to you Americans? The article also mentions Globish, a simplified version of English with a truncated vocabulary of only 1500 words, no humor, and no idioms. In other words, the goal of Globish is to be a pared-down languages that serves the simplest communication purposes. Some also believe it could save languages that might be threatened by English.

The second article, called Babelling On, discusses how many official languages the EU should have. Of course, to be completely fair, the EU should include all European languages (yes, even Welsh – and now that I live in Wales, I find it odd that Irish Celtic is included and Welsh is excluded, though there are more speakers of Welsh) and should subsidize translation to and from all the languages. In practice, this is not plausible and it is also very costly. So perhaps the EU should make sure that all major decisions are available in all languages but otherwise just stick to one language, which would likely be English. Or maybe the EU should switch to Globish. Many legal decisions are often difficult to read anyway, so Globish could be an improvement!

Saturday, December 23, 2006

How to Read as a Translator

The last two posts looked at reading and critiquing translations. Now we’ll look at reading and analyzing a text from the translator’s perspective.

Do translators read differently than others? Should they? If so, how? What should they be looking for as they read?

Well, translators who are reading something they are about to translate clearly do have different goals and needs than critics, academics, people who are reading for pleasure, or anyone else. In her book, Text Analysis in Translation, Christiane Nord offers a method for reading as a translator that will be helpful to students training to be translators and also for relatively new translators, but I personally find it too detailed and time-consuming for experienced translators, not to mention the fact that people with quite a bit of translation experience probably do much of what she suggests automatically.

Nord recommends a careful analysis of all extratextual and intratextual factors and she writes that doing this will “ensure full comprehension and correct interpretation of the text” and “explain its linguistic and textual structures and their relationship with the system and norms of the source language (SL). It should also provide a reliable foundation for each and every decision which the translator has to make in a particular translation process.”

Examples of extratextual features are the sender (not always or necessarily the same as the producer of the text), the intended audience, the medium, and the reason behind the production and translation of the text (what Nord terms “motive for communication”). Intratextual features include things such as the subject matter, non-verbal elements, and sentence structure.

After an explanation of what these extratextual and intratextual factors are and how they combine and relate in a text, Nord offers lists of questions for translators to consider in regard to these factors. Among many others, there are questions such as “What clues to the ST addressee’s expectations, background knowledge etc. can be inferred from other situational factors (medium, place, time, motive, and function)?” and “Is the subject matter bound to a particular (SL, TL, or other) cultural context?” and ”Which sentence types occur in the text?” and “What model of reality does the information refer to?”

Nord seems to suggest that by answering all these questions as they read a given text, translators can ensure that they have a firm grasp on all essential details related to the text, which in turn helps them make and defend translatorial decisions, and she writes that her system can be used with any kind of document, in any language, at any level. I am not convinced that her method covers absolutely everything, nor that all the questions offered in her text really need to be answered about each document a translator works on, but it is a good start, especially for new translators. As already mentioned, though, Nord’s method of reading and textual analysis does require a lot of time and effort, and that is just not plausible, or even necessary, for experienced, professional translators.

Does anyone use Nord’s system? What other ways of reading and analyzing do translators have?

Wednesday, December 20, 2006

How to Read a Translation

The last post looked at critiquing translations. But let’s take a step back and think about simply reading translations, without any intention of critiquing or reviewing them. How should we do that?

Look at this article by translator and academic Lawrence Venuti; appropriately enough, it begins with a translation of The Aeneid, the very work that spurred the writing of the last post.

Mr. Venuti, as is well known and has been mentioned on this blog before, is a critic of fluency, and he writes “[p]ublishers, copy editors, reviewers have trained us, in effect, to value translations with the utmost fluency, an easy readability that makes them appear untranslated, giving the illusory impression that we are reading the original. We typically become aware of the translation only when we run across a bump on its surface, an unfamiliar word, an error in usage, a confused meaning that may seem unintentionally comical.”

Mr. Venuti believes readers should understand what translation is and what a translator does “as an attempt to compensate for an irreparable loss by controlling an exorbitant gain.” His essay offers five rules for reading a translation that aim to make readers aware of the very fact of the translation, and, through this, come closer to the original text while also learning about translation.

His first rule is: “Don’t just read for meaning, but for language too; appreciate the formal features of the translation.” Since translators carefully choose each word, Mr. Venuti suggests that paying attention to linguistic features brings the reader closer not only to the original text, but also to an understanding of the translatorial choices.

But what linguistic features are there in a text? Well, the second rule is: “Don’t expect translations to be written only in the current standard dialect; be open to linguistic variations.” Translators might use temporal or geographical dialect/slang, or foreign words, or other features that somehow deviate from the norm, and this might surprise or confuse readers who expect a smooth, fluent text.

That relates to Mr. Venuti’s third rule: “Don’t overlook connotations and cultural references; read them as another, pertinent layer of significance.” Along with the linguistic choices, cultural references may also be part of the translator’s strategy, and can help the reader come closer to the original text, even if they affect “easy readability.”

His fourth rule is: “Don’t skip an introductory essay written by a translator; read it first, as a statement of the interpretation that guides the translation and contributes to what is unique about it.” Introductions, afterwords, footnotes – any paratext that a translator adds to a document is useful to the reader, because it helps explain the translator’s thoughts, processes, and choices.

And the fifth rule is: “Don’t take one translation as representative of an entire foreign literature; compare it to translations of other works from the same language.” Here, we could add that readers might even want to compare multiple translations of the same text, and various translations by the same translator. These are all useful ways of learning more about translation, as well as about other cultures and specific translators.

Mr. Venuti reminds us that translators do not just make copies of the original document in a different language. He writes, “[t]o provide this sort of experience, a translator would have to endow us with a lifelong immersion in the foreign language and literature.” And, of course, if we had that “lifelong immersion in the foreign language and literature,” we wouldn’t need translation anyway!

So as we read translations, we should keep Mr. Venuti’s rules in mind, and in general try to remember that we are reading translations rather than books that were written in that language. That will give us a better reading experience while also making translation and translators more visible.

The next post will look at reading from a translator’s perspective.

Sunday, December 17, 2006

How to Critique a Translation

Not long ago, I linked to an article about translator Robert Fagles. Today’s New York Times includes another article about his most recent translation, of The Aeneid. The article, by Mount Holyoke professor Brad Leithauser, mentions how many people have translated this work over the years, and then goes on to compare Mr. Fagles’ translation to that of Robert Fitzgerald.

Of course, it is always good to see translation highlighted and made more visible, but I do wonder about Mr. Leithauser’s methodology. Although he does mention metrical issues involved in translating Virgil’s work, he basically just compares short quotes from the two translations. He does not, unfortunately, include quotes from the original (which, obviously, would require back-translations). Perhaps he had strict space limitations for his article, but since the quality of a translation is not just about how it sounds in the target language, but also how it relates to the source text, I think a critique of a translation has to include a more in-depth analysis of the original document as well as of the finished product.

After all, what does it mean to critique a translation? It doesn’t mean just reading the end product and deciding if it “flows” well in the target language. A translation has to have some sort of connection to the original text, and it is impossible to judge the success (for lack of a better work) of the translation without referring to the work it is a translation of. And yet, many reviews attempt to do just that. It is likely the case, especially in English-speaking countries, that most critics don’t know the language/s of the book/s they are reviewing, or at least not at the necessary level, but that is a failure of the educational system and ought to be rectified.

In an ideal world, reviewers, like translators, would have a firm grasp of the source language and culture, including general literary history and specifically in terms of the writer in question, as well as of the target language and culture. Otherwise, they are, frankly, not capable of truly critiquing the translation, and are just reviewing the book as though it had been written in the target language.Just as reviewers are supposed to make public any ethical considerations related to their reviews of specific books (for example, if they know the author, or the book was published by the same company that publishes their own work), I think they should also make it clear whether they know the source language and whether they actually have read and analyzed the work in the original.

The next post will look at reading a translation in general.

Thursday, December 14, 2006

If the Clothes Don't Fit...

We’ve looked at various metaphors for translation, and most recently that was the clothing metaphor.

Lawrence Venuti, one of the major critics of “invisible” translators (i.e. that “fluency” is not necessarily the major criteria we should judge in translations), also refers to translation as clothing.

He wrote: “The translator is no stand-in or ventriloquist for the foreign author, but a resourceful imitator who rewrites the original to appeal to another audience in a different language and culture, often in a different period. This audience ultimately takes priority, insuring that the verbal clothing the translator cuts for the foreign work never fits exactly.”

Clearly, his idea that the clothing doesn’t fit, relates to the idea of visibility. You generally don’t notice someone’s clothes if they are neat, clean, fashionable, and well-tailored. We can compare that to invisible translation; it serves a specific purpose and is unobtrusive. But you would notice clothes if the clothes are dirty, out of style, and ill-fitting. That is visible translation. You are aware of the lack of fit, even if it is just slightly off. You, as the reader of a translation that doesn’t fit exactly, probably feel a little uncomfortable, and your attention is drawn to the very fact of the translation.

What’s interesting is that Mr. Venuti suggests that it is the translator’s concern for the target audience that ensures that the clothes don’t fit and that the translation is visible, whereas others might argue that it is the translator’s faithfulness to the source text that does that.

Monday, December 11, 2006

Do Writers Make Good Translators?

In the last post, I looked at reasons why writers might be put off from translation (the belief that translation is not creative or stimulating, the idea that it is not a well paid job, and a simple lack of knowledge about how to begin), but I didn’t explore a somewhat controversial point made in one of the first paragraphs. I wrote: “Writers are the ideal people to work as translators because they generally already have excellent writing and language skills and an enthusiasm for words”, but is this in fact true?

Well, let’s compare the qualities the typical good translator needs to those the typical good writer has. To start with language ability, a translator must have native proficiency in the target language and near-native proficiency in the source language. A writer obviously ought to have exceptional language skills in the language she or he writes in, but that doesn’t mean that she or he knows a second language at the necessary level. However, being immersed in the world of words and having a deep understanding of language does suggest that one would be open to and capable of learning another tongue.

Next, a translator has to have excellent reading comprehension abilities, because she or he is, it can be argued, the closest reader a text will ever have. Many writers are also voracious and careful readers, or at least they should be because reading and analyzing works by others is beneficial to their own work. A translator can not translate well without thoroughly understanding what the text is about, who the audience is to be, what the author’s style is, what kind of vocabulary is used, what the source and target cultures and literatures are like, and so forth, and these are all issues that writers presumably have also considered.

Translators also need to be good writers. They are taking documents written in one language and basically rewriting them in another. Translation is not simply just choosing a word for word equivalent or copying out the text in a foreign language; it is finding a way in another language of expressing the same thoughts and feelings the author did in his or her language, so translators must be sensitive to what good writing is and how to put words together. Writers, it goes without saying, also care intensely about how to craft texts.

Finally, editing skills are essential in translation, because a translator has to be able to review his or her work, check it against the source document, and also make sure it reads well and makes sense in the target language. Writers, too, typically rework their rough drafts, improving them, seeing if they make sense and use words well, and so on.

In other words, translators must have good language skills, reading skills, writing skills, and editing skills – and as for writers, check, check, check, and check!

So, while certainly not all good translators are or would want to be writers, and not all writers are suited to be translators, I think it is safe to say that many writers potentially could make good translators, and that it is a career path they should consider.

Saturday, December 09, 2006

Do You Have What it Takes to Be a Translator?

Here is a recent article, published online at Writing-World.com, that explores reasons why few writers incorporate translation into their careers.

Do You Have What it Takes to Be a Translator?

Translation, just like writing, is a creative, challenging craft that requires excellent writing, analytic, and editing abilities, as well as a love and feel for language. The major differences between translating and writing, of course, are that translators must have near-native skills in at least two languages, and work with transferring words an author has written in one language into another language, whereas writers need only work with one language and with their own thoughts and texts.

Writers are the ideal people to work as translators because they generally already have excellent writing and language skills and an enthusiasm for words, yet not many attempt it. There are several possible reasons for why few writers make translation part of their business.

The first is a belief that translating is less creative or interesting than writing. As both a writer and a translator, I'd argue that translation is incredibly demanding and creative. The limits imposed by the fact that a translator has to understand what the author meant and be able to recreate it in another language for a different audience forces translators to work very hard to find just the right way to express the author's thoughts given the target language's vocabulary, grammar, melody, and culture. This process can be compared to how some poets prefer to write haikus or sonnets rather than free verse, or how some fiction writers create artificial rules for their work (they can't use a certain letter, for example, or they have to focus on a specific topic). The fact is that the restrictions imposed by the form compel translators to be creative in a new way.

The second reason is that writers don't think they can earn money by translating. It's true that literary translation generally does not pay well and that it can be difficult to find such work; most English-speaking countries publish few literary translations, in part because publishers don't see much importance or profit in foreign literature and thus aren't eager to pay for it. Nonfiction translation, however, is very lucrative. Literary translators report getting around $2000 per novel, while nonfiction translators can earn that in just a week or two. Rates vary quite a bit, depending on the location, customer, level of difficulty, and the languages involved, but 12¢ per word is about average. Large companies with customers in many countries need translators and are willing to pay for quality work. Although some writers fear that it would be boring to translate user manuals or articles, such work can be quite stimulating and demanding. Translating court documents, for example, can be like reading a thriller; working on annual reports can teach you something about finance; while translating advertisements requires not just an understanding of language, but an ability to subtly make the ads more appropriate for the new culture. Translators I have spoken to report just as much satisfaction from finding the right word for a translation of a website as they do for a poem.

The final reason why writers are reluctant to seek translation work is because many simply don't know where to begin. The easiest way to start is sign up with translation agencies and to join one or more of the many e-lists that focus on translation. It is generally more common for translators to work for agencies rather than directly with customers, especially when starting out. Though agencies usually pay less, many translators like working for agencies because then they don't have to try to market to, contact, and sell their services to customers and also because agencies edit all the translations before sending them to the end clients, which means that an extra pair of eyes always checks over the work.

E-lists are useful because they often have job announcements and one can also meet other translators through them; more experienced translators might have advice for new ones, and they also might have too much work on occasion and be willing to subcontract assignments. For people who are more serious about translation, joining a professional organization, such as the American Translators Association or the International Federation of Translators, is a good credential. Such associations often have databases of translators where potential customers can find you, as well as newsletters with information, and conferences to attend. It's not cheap to join professional organizations, but the investment is worthwhile. Finally, make sure you tell your family, friends, neighbors, bosses, writing clients, and everyone else that you work as a translator. You might be surprised by how many people know someone who needs a translator and how many jobs friends or colleagues can pass on to you. In any business, making contacts is important.

Translation is a creative and stimulating art and craft, it can be lucrative, and there are easy steps new translators can take to find business. Not least, many writers are uniquely suited to being translators. All that remains now is for writers to expand their writerly horizons and start translating!

Thursday, December 07, 2006

Pamuk’s Nobel Lecture Online

Today Orhan Pamuk gives his Nobel Prize lecture. While only a select crowd gets to be in the audience, we can all watch the broadcast live on the internet at 5:30 p.m. CET. The science and economics lectures will be online tomorrow and the peace lecture on Sunday.

I’ve recently heard that Pamuk’s work is “better” in Swedish translation than it is in the original Turkish. I have only read it in English, so I can’t compare it, but it would be interesting to know if others feel that is true. Translation doesn't only involve losses; something can be gained through translation, too.

Wednesday, December 06, 2006

Sunday, December 03, 2006

Translators’ Responsibilities: When the Source Text Has Issues

The definition of a translator is someone who translates a text from one language to another, carefully considering the cultures involved, the style of the text, the purpose of the text and of the translation, and the potential audience. That’s all challenging enough, and there’s much to consider in that about what the translator’s responsibilities are and what s/he should prioritize, but in this post, I’d like to look at an aspect of the job that is rarely mentioned: what should a translator do when faced with a source text that is, to be perfectly frank, not well written?

Some source texts themselves are poorly done translations while others simply have been authored by people who either didn’t put much effort into the document or don’t have good writing skills, or both. A sloppy text might have misspellings, grammar mistakes, factual errors, unclear meanings, or other problems. What options does a translator have when working on such a text? And, more to the point, what is the translator’s responsibility in this case?

Some translators believe that their job is simply to translate whatever is on the page, without questioning it. So they’d generally correct misspellings and bad grammar (that is, they wouldn’t create equivalent misspellings or incorrect grammar in the translation), but they wouldn’t rewrite awkward sentences, mention factual errors to their client and/or the author of the text (that’s not always the same person, obviously), or ask what was intended by a certain phrase.

Others will ask the client to clarify confusing passages or to re-check facts. Still other translators would go even further and give the customer feedback on the text, pointing out some, or even all, of the problems.

There are translators who offer to rewrite and/or edit the source document for an additional fee, and there are some who refuse to translate poorly written documents until they have been reworked, whether by themselves or by the author and/or customer.

All of these different responses show the various ways translators view their job and their translatorial responsibilities.

I have tried a variety of these methods myself, but most often what I do is ask about anything that seems unclear or especially awkward plus point out mistakes I find in the source text. If I can’t understand what is meant by a phrase or a paragraph, then I won’t be able to translate properly, so I do feel it is my responsibility to make sure everything is clear to me (and, I should note, if something is seemingly incomprehensible, it may, of course, be attributed to my own lack of understanding or knowledge, and not just because the writer is not proficient as his or her craft). As for the reason why I mention mistakes to the client, I feel it is a courtesy to them, and it also shows that I am observant and take my work seriously. A client who later finds mistakes in the source text but remembers that I didn’t bring them up might wonder whether I even noticed them and whether, if I didn’t notice them, I paid as close attention to the document as I should have.

There have been occasions when I have received a document of low quality that has had such a number of careless errors and sloppy phrasings that I didn’t feel I should have to spend the time necessary to edit the whole text, especially as I wasn’t getting paid for that, so I instead just gave the client a general summary of issues I noticed in the text, with a few specific examples. Once, I had a text so riddled with problems that I found it very difficult to translate, and I suggested that I or someone else be hired to fix the document, but the company I was working for made it clear that they didn’t care enough about having correct and well-written language to spend additional sums on the document, so I could only do my best with the text as it was.

So I suppose where I stand on this issue is somewhere in the middle: I believe translators have a responsibility to thoroughly understand the documents they work on, and that they must ask questions or do research if a certain text doesn’t make sense to them in some way. I also believe that translators should fix problems such as misspellings or incorrect usage as they translate (unless such things are part of the style of the text, as in some fiction or in reproductions of dialect), and I think it is respectful to the customer to mention whatever issues come up in the text, even if in a general way, without necessarily sending back a completely marked-up source text. But I don’t think translators should have to rewrite source documents (unless they get an extra fee for that) or that they should feel the need to give the client detailed feedback on them.

What do other translators think? And what about those of you who employ translators?

Friday, December 01, 2006

Paying Markets for Translators from Erika Dreifus

Erika Dreifus’s helpful blog for practicing writers offers some paying paying literary markets for translators. Those of you who want to publish translations of fiction or prose might find her links useful.

Wednesday, November 29, 2006

Translating from English to English

In the last post, I mentioned that American and British English are not always the same, even if they are, obviously, mutually intelligible for the most part. Something many people don’t realize is that there are translators who translate between American and British English.

Why would such a job be necessary? After all, if you can read English and have some basic knowledge about vocabulary and grammar differences among the various Englishes, why should seeing the word “boot” (UK English) instead of “trunk” (US English) bother you? Wouldn’t you understand if a character in a novel asked, “Do you have a pen?” (US English) instead of “Have you got a pen?” (UK English). Wouldn’t it just add to the flavor (or flavour) of whatever you are reading?

Well, I believe that is generally true for literary works; after all, just as it would be odd if, in a book set in Spain, a character suddenly used American slang, I think preserving the original style and feeling of an English text is important. Publishers tend to disagree with me, however, in part because they seem to assume the audience would find it confusing or disturbing if a book was in any way “foreign.”

This is especially the case with children’s literature, because it is erroneously believed that children don’t understand that people in other countries might speak differently or have different traditions. So publishers worry that Americans kids might think it is “weird” if an English boy in a book that takes place in England says “lift” and not “elevator,” and therefore such things are translated to American English (or to British English, in the case of American books). I have not read any of the Harry Potter books, but I have been told that the vocabulary and grammar in them is Americanized for US audiences, and that some American Harry Potter aficionados insist on buying their books from the UK, so they can read the original texts. And, as another example, I received some information not long ago about a children’s book translated to English from a Scandinavian language. An editor at the British publishing company implied that major, “neutralizing” changes were made in the translation (including removing all mentions of the setting), so the book would be ready for child audiences in both the UK and the US, and so a second, American translator wouldn’t later be needed, at an additional cost to the publishers. To me, this kind of translation amounts to a sort of dumbing-down of the book, because it makes it easier for readers to access. Sure, explanation may sometimes be needed, and that can be given in a footnote or by adding a word or two to the text, but remaking parts of a novel so it appeals to foreign readers is going a bit far.

When it comes to non-fiction, though, I have more understanding for publishers. In some non-fiction works, it is essential that the message not be lost because the audience doesn’t recognize the words or the style. For example, I have seen an ad here in Wales that says “Have you sussed it?” As an American, I had no idea what that meant when I first saw it. Then I learned that “to suss” means “to check out” or “to find out” or “to understand.” If that ad were used in the US, perhaps it would be changed to “Do you get it?” and the company wouldn’t have to worry about losing potential customers because of the incomprehensibility of their message. That’s the kind of thing an English to English translator can help with.

Cultural references can add quite a bit to a novel, but might need explication in a work of non-fiction. Recently, I read Simon Winchester’s book about the OED, The Surgeon of Crowthorne. That’s the original British title, anyway. In the US, the book is called The Professor and the Madman, apparently because the American publishers thought (correctly, I suspect) that their more dramatic title would appeal more to Americans. Knowing that fact made me wonder what else beyond the spelling and grammar had been adapted or translated for American readers. I have not read the American version, but I would imagine that the mentions of the Civil War are not necessarily as detailed in the American book, since Americans are presumably more familiar with the facts of the war, and that there might be more information about the locations in the UK, so American readers can understand distances and issues of, say, fashionability. I wondered, too, if the tone of the book, which seems rather British to me, might have been changed a bit.

In short, translators from English to English analyze texts for issues of grammar, vocabulary, and culture-specific references (locations, politics, educational systems, and so forth), and they adapt such “problem passages” to another kind of English. As I made clear above, I see the need for this in non-fiction documents, especially for ads, user’s manuals, tourist information, and other such texts that are to serve an informational purpose. But I don’t think much of it when it is applied to fiction.

Have you sussed all that?


To learn a little more about this very specific kind of translation, check out this article. It would also be interesting to know whether this type of translation is common in other languages that are spoken in two or more countries (such as German, French, Spanish, or Swedish).

Monday, November 27, 2006

English for Native Speakers

Now that I’ve lived in the UK for two months, I’ve become more and more aware of the differences between UK and US English. We don’t just spell some words differently (colour versus color) or use different vocabulary at times (hoover versus vacuum) or have some different usage rules (such as for apostrophes and commas, but I won’t let myself get started on that!). There are some significant issues that separate American English from British English, and those of us who claim to be able to translate to or copy edit either variety ought to make sure that’s really the case.

So here are some references I’ve found:

American versus British English

Vocabulary differences

Grammar and spelling differences

English-English dictionary


I’ve given them to my students and I’ve sometimes found them useful myself, too, especially if I’ve needed to translate to British English (just because English is my native language doesn’t mean I can’t learn more about it!). And, yes, of course there are many other kinds of English as well, but I think it is safe to say that American and British English are by far the most influential.

The next post will look at translating from English to English. Yes, you read that right!

Friday, November 24, 2006

A Translation Metaphor

I always enjoy reading metaphors or other descriptions that involve translation in some way (both metaphors that depict translation and those that describe something else using translation), because they offer a view of what people think translation is. One day it might be interesting to study these metaphors and see how the sense of translation has changed over time.

For example, last month, I mentioned Alistair Elliot’s idea of translation as powdered eggs. Henry Rider, in the preface to his 1638 translation of Horace to English, offers a very different metaphor, that of translation as clothing:

“Translations of Authors from one language to another, are like old garments turn’d into new fashions; in which though the stuffe be still the same, yet the die and trimming are altered, and in the making, here something added, there something cut away.”

I’d thought of translation as many things before, but I hadn’t thought about it as “old garments,” and though I like Mr. Rider’s metaphor, I don’t really agree with it.

Do you have favorite translation metaphors or descriptions?

Tuesday, November 21, 2006

Just Be Honest

As a brief follow-up to the recent post about writing letters of inquiry, I have to add one more piece of advice. I didn’t mention it before because it seems so obvious, but then I received yet another such letter from a freelancer and his letter made me realize that sometimes the obvious is, well, not quite so obvious.

Here it is: you can, and should, proudly mention your education, your work experience, your skills, and anything else related to the prospective job that sets you apart from all other applicants, but please, do not pretend to be, do, or know more than is actually true. In other words, do not exaggerate or lie in any way.

If a potential employer believes that you are not being completely honest, she or he will not feel enthused or confident about hiring you. And if someone does ask for more information or even hires you, but later discovers you were not telling the truth – perhaps by the low quality of your work or by you being unable to do something you claimed you were proficient at – not only will that negatively affect your working relationship with that person (as in, you probably won’t have a working relationship anymore and she or he will certainly not recommend you to others), but you may also make that employer more suspicious and less likely to employ other freelancers in the future. Even one small lie can make things difficult for yourself and for others.

If you are exaggerating because you feel you don’t have enough experience, be honest about that instead and realize that you may have to accept lower fees or less challenging work until you can build up your CV. If you are exaggerating because it is part of your culture to do so, keep in mind that this may not work in other cultures and that you might have to adjust your approach. If you are exaggerating to make yourself feel better in some way, that is something for you to think seriously about.

So, do not say you have near-native fluency in seven languages (like that “interpreter” mentioned a few posts back) or that you are equally comfortable with literary, financial, legal, technical, and academic documents, or that you regularly translate 15,000 words a day. Do not pretend to have degrees from schools you only took one or two classes at or that you are familiar with all the translation software programs when you have in fact just heard about them. Do not give as references people who wouldn’t even recognize your name, and do not lard your CV with claims of work that you did not actually do.

To summarize, be honest about who you are and what you can do. Often, that’s good enough, and there is no need to employ exaggeration or lies; doing so will probably backfire in some way, and it will likely make you disappointed in yourself as well.

Saturday, November 18, 2006

Updated Archive by Category

I’ve now updated and reorganized the archive by category (see the left side of this page), so it should be very easy for you to find posts on whatever topics interest you, such as practical advice, interviews, poetry, translation technology, and so on. I hope this is helpful!

Wednesday, November 15, 2006

Writing Good Letters of Inquiry: Advice for Freelancers

Lately, there’s been a plethora of new freelance translators wildly sending out their CVs to any translation agencies, companies, or even other freelance translators that they find. Most of us who get these e-mail messages tend to ignore them. Why? What are these new translators doing wrong? Or, rather, let me rephrase that question positively and ask: How should freelancer translators write good letters of inquiry?

First of all, if you’re looking for work – and this applies to any job, not just translation – you need to do some research. I suspect that many of these new translators are buying or finding lists of translation companies on translation websites or else that they are doing quick Google searches and that they don’t bother to carefully look at the companies’ websites before hurriedly sending off letters of interest. If you translate from Spanish to Chinese, there is no point in writing to a company that only works with Scandinavian languages. If you only have experience translating personal letters, don’t try to get work at a company that just hires authorized translators. And, frankly, there isn’t much call at all for you to write to other freelance translators, since chances are that they don’t want or need to hire someone, and that even if they do, they already have the contacts they need. So make sure you check to see what languages and what subjects each potential employer works with, and what needs they might have, before you waste both your time and theirs sending them a letter.

Once you have narrowed down your list and know where you want to inquire about work, you have to write a good, brief letter. Some of the applicants who have sent me letters have rambled on about themselves or mentioned things that have little to do with translation, and that doesn’t make me want to keep reading. Say who you are, what your background is, what you can offer the company you are writing to, and why you are interested in just that company. Each letter should be personalized; it is always obvious when someone is sending out a mass mailing (especially when there are lots of e-mail addresses listed in the “To” and “CC” fields, which really looks unprofessional) and mass mailings show that little thought or effort went into it, and that won’t make people want to hire you. This is why research is so essential; if you know something about the company, you’ll be able to add a sentence or two about why you would fit in well with their business objectives and needs. If they haven’t advertised for new freelancers (and, of course, even if they have), then you have to be able to clearly and succinctly explain why they ought to consider you.

Speaking of personalization, find out the actual name of the person you are writing to and don’t just write “Dear Madam/Sir.” If you are unsure of the gender of the person you are addressing, study the company’s website a little more; usually, the biographical information will refer to the person as “he” or “she” and then you know whether to use “Mr.” or “Ms.” Don’t use first names (or any other casual language or slang, for that matter) and make sure you spell the name of the person and the company correctly. In fact, check all your spelling carefully. Correct spelling and good language usage are always important, but this is particularly the case when you want to work with language!

So, if you want your letters of inquiry to be read, start by doing thorough research, then target your letters appropriately, write personalized and brief letters, and use correct, polite language. If you take the time and make the effort to look for work in this way, potential employers will see that you are conscientious and careful, and they will be more likely to consider your application, instead of just reading a sentence or two, getting frustrated and annoyed, and deleting your letter.

Monday, November 13, 2006

Speaking of Words: On Learning New Words

The last post was about unique or “untranslatable” words, some of which I believe ought to be borrowed into other languages, including English. But thinking about words reminds me of one of the biggest challenges for people learning new languages: building their vocabulary.

To become proficient in a language, you can’t just memorize the grammar rules and work on your accent; you also have to learn words. Lots of words. The language teacher’s rule of thumb is that for every 100 new words a learner sees, only 10 will stick in some way, especially if the words are not actively used more or less immediately. That means you have to be exposed to many words, and you have to try to use those words, too.

So how can you find new words to learn each day? Well, obviously you can read books or newspapers in English and pick a word or two each day to look up in the dictionary and attempt to understand. That’s the best way to learn new words in context. I’ve found that you may not remember a dictionary definition, but once you’ve seen a word in use, the next time you see it, you have a sense of what it means. After a few times, you really understand the word.

If you want, you can also get free e-newsletters that teach you a new word each day. Here are some of my favorites for English, and one for Swedish:

A Word A Day is one of the largest such e-newsletters, and it has a theme each week.

Oxford University Press publishes many dictionaries and other books, and they have various e-newsletters with words each day. Note that not all the words they introduce readers to are ones you’d want or need to use on a regular basis, but that doesn’t make them any less interesting. OUP offers: American Slang Word of the Day, New Oxford American Dictionary, Erin’s Weird & Wonderful Word of the Day, and Garner’s Usage Tip of the Day (this does not teach new words exactly, but it does give advice on using English, which sometimes includes distinguishing between two similar or frequently confused words).

Merriam-Webster, another dictionary publishing company, also has an e-newsletter.

Ett Ord om Dagen is a way to learn about Swedish words.

Let me know if you are familiar with other such sources for learning words!

Saturday, November 11, 2006

An Inclusive English Tongue

I noticed this recent BBC article on Hinglish, which hints at what each tongue has to offer other languages and cultures. Since each language has a different way of understanding life, it has unique words and phrases that explore the world from that point of view. English has long been a promiscuous language that has blended with and taken from other tongues. Now, besides Hinglish vocabulary, we should also eagerly accept new words from Swenglish, Spanglish, Chinglish, and so forth.

One of my personal efforts towards the goal of having a more inclusive English language (and by inclusive I mean that there are more words from more languages to describe more concepts), has been to try to see the Swedish word “sambo” transferred to English. “Sambo” comes from “tillsammans” (together) and “bo” (live) and it means partners who live together without being married, as is much more common in Scandinavia than in other parts of the world. Another possible Swedish candidate is “lagom,” which means, more or less, “just right.”

What other words should the English language absorb? Maybe Christopher Moore’s book In Other Words: A Language Lover's Guide to the Most Intriguing Words Around the World has some ideas for us.