Happy International Translation Day, or I <3 St. Jerome

Happy International Translation Day!

St. Jerome at the VaticanToday is the feast of St. Jerome, patron saint of translators, and therefore the day we celebrate International Translation Day. When I visited Florence and Rome last year, the wonderful historian Ada Palmer struck up a game of “Spot the Saint” at each museum we went to and each important monument we passed (which in those two cities is approximately every 50 feet). I wasn’t the best at the game, but I could always spot St. Jerome a mile away, because he’s the best one. (By which I mean the one I like best–he has a dashing red coat and a sweeping hat, and listening to his story as told by Ada, I felt like he and I really “got” each other.) You can see I snapped a photo of him here hanging out at the Vatican, in a painting by Pier Francesco Mola…

I think it’s great for each profession to have a day of recognition for their service, and what better day than that of a man forever associated with words, AND in my mind a fond memory of gorgeous Italian art?

So here’s to all my translator colleagues, and the ways in which we build bridges between cultures and people. And to everyone else, give a smile today for your favorite translator. We help the world share books, films, inventions, medicines, and diplomatic talks. We keep the wheels of justice turning. We save lives, or just help you have fun.

I celebrated today by attending a few webinars, doing outreach, finalizing plans to share a hotel room at this year’s American Translators Association conference, and finishing up a giant project… which actually isn’t quite finished yet, so that’s all for now!

The Nameless Terror

Hello_my_name_is_sticker.svg

When is a personal name more terrifying than a word? I’m sure most teachers taking attendance on the first day of school have stories about name-terror… and so do translators, sometimes. For a Japanese-English translator, the terror can go beyond a simple “How do I pronounce this?” to “How do I spell this in the Latin alphabet? Because I have three equally valid guesses that are spelled absolutely nothing like each other.”

That’s right: in languages that share alphabets, names are (allegedly) easy to “translate” because you simply copy and paste. Your name is your name is your name. But put it into another alphabet–like Japanese, in which the same sounds have different characters and the same characters have different sounds–and it all goes downhill fast.

“What’s this name written here?”
“I don’t know; I don’t know that guy.”
“But I thought you could read Japanese.”
“Oh, I can read it; I just don’t know what it is. I can give you a guess, if you want.”
“Should I ask a Japanese person?”
“Sure; they’ll give you a guess too.”

So you would think that the easiest thing I translate would be staff lists, because they’re just people’s names. Instead, they’re difficult and rarely satisfying, because you want everyone to be credited correctly with their actual (romanized) name, but unless you’ve met the person or they have their own website or you can find someone who knows them, there’s just no way to be sure. You see, when you fill out paperwork in Japan, next to your name there’s always a space for “how to pronounce your name.” This is because two people could have the same Japanese character as their names, yet the names could sound completely different: 真 could be “Shin” or “Makoto.” They don’t even share the same number of syllables, let alone any sounds! So it’s a language where you have to routinely tell other people how to read your name.

Sometimes an anime licensor or business client will be able to check each name on the list and let you know if anything is incorrect. But other times, they’ll be able to look it over, but there might be people on the list who worked out of house and are not available anymore, and nobody is actually sure. So it’s just you and your best strategies… and when all else fails, your best guesses.

These days I give all my clients this disclaimer:

Since not all translation companies deal with Japanese regularly, my policy is to always advise my clients that on a legal document, you will need to confirm the name spellings with your client before considering the product final. Name spelling confirmation on other documents is also advisable. Japanese names are written using Japanese characters, and English spellings for the “same names” in Japanese can vary wildly based on individual preference (example: “Kosuke” vs. “Kousuke”). In addition, wildly different names can be spelled the same way, giving the entire name an unknown status (example: the given name 昌 could be either “Akira” or “Sho”).

Otherwise, what do you do with names in other alphabets? A few approaches I use:

1. Google the name to see if the person happens to have their own website or blog, and if so, whether their name is spelled out there in your alphabet or at least given a pronunciation.

2. See if the person has an account on a social media site like Facebook, LinkedIn, or Twitter, and ditto. (Warning! There are always many accounts for different people who happen to have the same name, so in this technique you have to make sure it’s really and truly the person you want.)

3. If you know or can discover a company the person works for, check the company’s website to see if their name appears.

But sometimes, it will sadly come down to “This is my best guess based on statistical averages.” We always want to do right by everyone on that list, but it’s just not always possible.

And then there’s birth certificates, where making a mistake or bad guess is NOT a good thing! You better bet every client gets this disclaimer when I do a birth certificate!

The Curse of the Unfunny Joke

“Children always know when company is in the living room—they can hear their mother laughing at their father’s jokes.”  —Source unknown1

One of the questions I get the most as a TV translator is, “Isn’t it hard to translate the jokes?” What they mean is, “Isn’t it hard to translate the jokes so that they’re still funny?”

And it is hard sometimes, of course. Humor doesn’t always translate across cultural lines or language lines. But over the course of my career, I’ve built up a system for myself to handle wordplay and such–I even made it one of the topics of my Translation Tricks panel at Anime Central this year, which I actually think was the topic the audience got the most engaged in. So although each case is different, and sometimes you do hit an impossible one, at least I’ve got a bag of tricks that I can try on a joke to try to carry the funny over. Most of the time it works out.

What are really difficult, at least for me, are the jokes that aren’t funny. Something you never think about until you actually become a translator: how do you translate a bad joke? A joke that’s sort of funny, but mostly lame? A joke that’s actually designed to fall flat? It’s incredibly challenging to walk that line between “this is a joke that tried to be funny and failed” and “this is a joke that is genuinely funny.” Because if the joke isn’t funny in the source language, but my translation is funny, to one degree or another my translation has failed. And if the whole point of the joke is its unfunniness, then I’ve failed completely.

So okay, then: the translation shouldn’t be funny. But in that case, how do I get across to the audience that the non-funny dialogue I just wrote is a joke? Somehow I have to encode a “should have been funny but wasn’t” signal into the dialogue without actually producing funniness. I have a few vague theories, but I’m still not quite satisfied with any of them. Often I second-guess myself: Will the audience really get that joke if it’s not funny? Will they think it was a funny joke that got translated unfunnily? Will they even be able to tell it’s a joke at all?

It’s times like this that make me realize how lucky I am to have grown up in a sporadically funny family. My father and many relatives on his side of the family seem to embrace the philosophy of “Tell all the jokes as they occur to you, just in case.” A joke never had to be a good joke to get told by my dad or my uncle. Funny jokes are the best, of course. Ideally the joke should be funny… but if it’s discernibly a joke, then funny or not, you might as well tell it. And often they got equal pleasure out of the horrible ones, and even tricked me through some sort of osmosis into doing the same. My mother and her siblings tell their own jokes, of course, but they don’t seem to take the same primal glee out of it, and they seem to value funniness as an essential component of joking. Even as a young child, it was pretty easy to discern the stupid jokes from the clever ones by whether or not Mom would laugh.

Now, as an adult, I’ve come to respect that sometimes the stupid jokes take their own brand of cleverness!

~~~~~
1Fun fact: in Japanese there’s a term specifically for jokes somebody’s dad would tell: oyaji gyagu, or “Dad joke.” It’s that particular brand of joke that only your dad or other men your dad’s age tell, but which they seem to universally love. My personal theory is that when you become a dad, you activate a special part of your brain that produces that specific flavor of humor. But even if you’re not a dad, if you’re like me, some small part of you secretly enjoys it.

Wham, bam, pow! And Scarier Sounds in Translation

“Hey guys, does anybody know what doom sounds like?”

On Friday I came across a perfect example of a classic translation challenge in Japanese fiction. It all started when an editor reviewing a TV episode showed me some onscreen Japanese text that said “gogogogo.”

Now, anyone who spends time watching or reading Japanese media is pretty used to seeing sound effects scrawled everywhere, like the old Adam West Batman where all the fight scenes were punctuated with word bubbles exclaiming “Bam!” and “Pow!” The Japanese language loves onomatopoeia, the sound-words that we English speakers usually associate only with comic books and children’s songs (“Here an oink, there an oink, everywhere an oink oink”). Though English is pretty stingy with its sound-words, Japanese and some other languages use them in a much wider variety of contexts and have a much richer trove of them. In Japanese, they don’t stay confined to comics and songs; they permeate every area of conversation and life. A non-native speaker of Japanese who never gets the hang of using them in speech just never sounds quite right. I know that as an American, when I use onomatopoeia it can sometimes become the first moment of real connection between me and whoever I’m speaking to, even if I’ve spoken to them many times before. A former coworker and I once bonded when she was handing out crunchy snacks and I told her I liked her choice because I think paki-paki snacks are better than bari-bari snacks–in other words, I like a more understated style of “crunchiness.” All of a sudden the two of us, who honestly didn’t get along that well normally, were launching into an animated conversation about crunchiness values, and for those few minutes getting along beautifully. It wasn’t because the eternal chips vs. pretzels debate was really that important to us; it wasn’t because I’d said anything particularly clever (paki-paki usually doesn’t even describe food). I think it was because for that brief span of time we just sounded right to each other. These sound words are one component of “naturalness” in Japanese.

In fact, sound-words feel so natural that Japanese a whole category of them called gitaigo (擬態語), which are mimetic words–sound-words for things that don’t make sounds. For example, when you stare at someone, your eyes go jiro-jiro. When you tear up, your eyes go uru-uru. This isn’t the “wham, bam, pow” or even the “pitter-patter” you find in English. Not only is no sound being made, but no sound is really physically plausible. But we can still use these mimetic onomatopoeia to talk about emotions or states of being, and they’re every bit as much a part of everyday life. In Japanese, everybody knows exactly what silence sounds like, because the sound of silence is “shiiiin.”

In translation, these sound-words often disappear. Instead of following Japanese conventions literally and saying “I feel so [invent a sound of anger to replace muka-muka with here],” I’ll use “I feel so pissed off!” in my translation of a story. But working in TV shows or comics, sometimes we’re confronted with sound-words plastered all over the screen or page, staring at the viewer and demanding to be translated by the force of their presence. So every few days I find myself being shown a screenshot of a grinning boy with the word niko-niko over his head, and saying, “Oh, that’s the sound of him smiling. How about we caption it as ‘grin’?”

Which brings us back to the beginning of this post and Friday’s “classic translation challenge”: what is this gogogogo the editor showed me? Well, it’s one of my favorites when I don’t have to translate it, and one of my least favorites on days like Friday… it’s the sound of impending doom. (Unless the doom is already here, in which case it’s the sound of a very ominous situation indeed.)

As my dear friend Ada Palmer and I once discussed, this is no problem in a comedy. In a comedy, we can simply scrawl “DOOM!” across the top of the frame in dramatic ALL CAPS and be done with it, and it’s perfect. But in a serious show, unfortunately, that doesn’t work. It’s one of those translation situations where you have to climb the same mountain all over again every time, because every time the task is impossible and every time it refuses to submit to the same “solution” you came up with last time.

In this particular case, the editor showed me the translator’s solution and asked me what I thought. I said it worked for me unless anyone else could come up with something that sounded more like doom.

On Translation vs. Interpretation (Repost)

This is a repost of my essay “On Translation vs. Interpretation,” which first appeared on my site on 11/03/2006, and has been featured in a couple of other places since then.

 

On Translation vs. Interpretation

Many people don’t realize there’s a difference between “translation” and “interpretation.” Even people who work with translators all the time will sometimes ask us “Can you translate at a meeting I’m holding?” And I’m sure interpreters frequently get handed documents and asked to translate them. Perhaps it’s easier to go from interpretation to translation; I wouldn’t know and wouldn’t like to assume. However, as a professional translator I can definitely say that interpretation is so unlike translation as to be an entirely different proposition and much more difficult for me.

So what is the difference between “translation” and “interpretation”? “Translation” refers to the translation from one language to another of something which is frozen in time: a book, a TV show, a letter, a play, a speech someone has already delivered which is recorded and then given to the translator in its entirety. “Interpretation” is a real-time exercise–when you interpret, conversation, speech, etc. is actually taking place, and as it happens you are taking what is said in Language A and communicating it in Language B. It may be that you are interpreting at the same time as others are speaking, or it may be that you wait until the end of a chunk of speech and then interpret it into another language while the speaker pauses to wait for you.

Although many people seem to regard “translation” and “interpretation” as the same or at least activities that the same person would do, and although there are people who do both translate and interpret, the two are radically different both experientially and practically.

Just recently I had my first interpretation gig. I had the honor of interpreting at two Question & Answer panels and two autograph sessions for Mr. Yoshitaka Amano at Oni-con 2006 in Houston, Texas. I think a large part of the reason why I was approached about the job (about 48 hours before the con began) was that assumption so many people have that translators interpret and vice versa. However, I took the job and am glad I did so; it was fascinating. Here are a few of the things I learned or confirmed my suspicious about:

Translation is you in a room; interpretation is you in the world.

Most translation takes place alone at a desk. The translator interacts with something which is fixed in time, complete, a separate unit. The translator only talks to people as a side activity. The translator is free to wander the chambers of her mind, to ruminate and to solve problems in consultation with and according to the dictates of her own body and soul. There is silence in which to think; there is the freedom to, if she suddenly finds herself needing to know an obscure fact about whale migration, make a long-distance call to Dad and ask him about the migratory patterns of whales. Interpretation, on the other hand, generally takes place in a group of people, because what you are interpreting is generally the speech of or between people. You must interact with people. You are not free to intensely probe your own soul until you find the answer to a sticky problem, no matter how much introspection it may take. You are not free to take a bathroom break in the middle of the climactic point in the dialogue. You are not free to stop and call Dad to have him clarify a technical point.

The advantages and disadvantages there are obvious. However, there is another side to this interaction with the world in interpretation. In translation, it is often not possible to ask the original creator what s/he intended. If something is open to multiple interpretations, leaving you in a jam about which to opt for, there is usually no recourse. There is often no opportunity for dialogue between the translator and the original writer/speaker. It’s an inorganic process, in a way. Interpretation, however, is an organic process. There is often (though not always) an open avenue of dialogue between you and the person you are interpreting. Often you can ask a question, clarify a point, ask for a rephrase, or confirm that your understanding is correct. It’s possible to look much worse in interpretation–to crash and burn–because the result is real-world and not inorganically polished before publication. But it is also possible to fly much higher, in some ways.

Translation is out of time; interpretation is in time.

Because interpretation is in the world, it occurs in real time. The translator must make her deadline, but she does not have to translate in real time, or even in real order. She can take breaks; she can work slowly on a section of text if it is dense or difficult; she can even translate the end before the beginning if she wishes. The translation will be delivered as a whole product, and no one will ever know or care how it was done. In interpretation there is no “whole product,” and there is immense time pressure. You cannot skip to the end of the conversation and do that first, because the end has not happened yet. You cannot go think for an hour. You do not have the time to lovingly craft and polish each line like a fine precious stone. Interpretation is down and dirty. You are not blowing glass. You are in the sandbox.

This is one of the key differences between someone who identifies as a “translator” and someone who identifies as an “interpreter,” I believe. The translator works in nuance, sometimes spending days revisiting and fine-tuning a single sentence or even a single word. The interpreter pays attention to nuance but deals in the meat of the issue. Often there must be instant turnaround of the type a translator is not used to providing and may be quite bad at (“Usually I would go back to my desk, think about this, and email you!”). The interpreter must grasp the meat of the issue right away and deal with that first. When you deal in real time this way, sometimes tiny pieces are lost. This would eat away at my soul and mind as a translator but is something I have to resign myself to in interpretation or I will go crazy. Likewise, I have had occasion to supervise the translation work of someone who primarily identifies as an interpreter, and found that his translations did not capture nuances that a translation (as opposed to real-time interpretation) is able to capture and should capture. (I should note that I do not believe he is necessarily representative of interpreters as a whole; I think it spoke more to his individual, personal attitude being the type of attitude which did not go well with translation.)

The interpreter, too, must have a much larger vocabulary than is strictly necessary in a translator. The translator is free to look up any and every word she doesn’t know or doesn’t feel 100% comfortable with and that’s fine, but the interpreter must not be constantly looking up things in a dictionary. Perhaps the translator can in this way extract things which are more precise, but the interpreter will have more core knowledge.

I found while interpreting for Mr. Amano that this time pressure was both a curse and an unexpected spur to creativity. The time pressure made it more difficult to bend my intellect to the issues in a disciplined, thorough way–but the terror and necessity of it caused the kind of sudden solutions, the organic creativity, that can only happen in a situation with time pressure. Under the gun you come up with ideas that otherwise might never occur to you.

For translation you have to be able to write; for interpretation you have to be able to talk.

There are a couple of ways in which this is true. An excellent translator must be excellent at writing; depending on the type of translator, proficiency may be required in many types of writing: technical, literary, expository, and/or dialogue writing. But a translator is seldom required to be a good public speaker. On the flip side, an interpreter may not need those writing skills, but an interpreter must have the ability to speak to people, and to speak to crowds. Obviously not every interpretation gig will involve crowds, but it will come up (it certainly came up in my gig–not only did I have to speak in front of a crowd, but I had to speak in front of a crowd of fervent Amano fans!). Interpreting for Mr. Amano was much different than translation, because my output was spoken words from my own mouth, rather than text that someone would later read. This allowed me to say things in a way that I would not translate because it wouldn’t be appropriate to written form, but writing also has advantages over speech in some ways, so the mental approach has to be different depending on what your output is.

It’s also true that interpretation may often involve speaking in multiple languages–in other words, within one conversation a Japanese/English interpreter may have to switch between interpreting Japanese-to-English to Person A and English-to-Japanese to Person B. Suddenly not only must the interpreter be comfortable speaking, but she must be comfortable speaking in both languages. Some translators also go in both directions, but not always. I have occasion to write business emails in Japanese sometimes, but for practical purposes I’m strictly a Japanese-to-English translator at this point in my life, and don’t usually go the other way around. Interpreters generally don’t get to specialize in that way. Since I’m a translator and seldom get the opportunity to really hold long conversations in Japanese, although I speak Japanese I feel much less comfortable holding sustained time-pressured conversations in it in front of strangers than I would feel doing the same thing in my native language of English. I don’t have to constantly speak smooth Japanese to translate well. But interpretation is different.

In the case of Mr. Amano’s Q&A panels, I was very fortunate to be pairing up with a coworker who is a native speaker of Japanese. He, like me, is a translator by profession. But he had done some interpreting before and suggested that we handle things this way: when an audience member asked a question in English, he would interpret that question for Mr. Amano in Japanese. Then when Mr. Amano answered the question in Japanese, I would interpret it for the audience in English. This turned out to be a fabulous way to do things because each of us got to do the brunt of our speaking in our native language, making things faster, more comfortable for the listeners in both languages, smoother in general, and much easier and more comfortable for the two of us. (Plus, because there were two of us, we could help each other out with our respective tasks when necessary.)

Translation and interpretation subject you to different kinds of strain.

The physical and mental endurance/exhaustion factors are a bit different across the two activities. I had a horrible time in my second Q&A panel because for the last forty-five minutes of it, I had to go to the bathroom. A translator isn’t subjected to this stress unless she’s in the thick of some brilliant idea she doesn’t want to lose–if my concentration suffers because of physical needs as I translate (and those physical needs can be very different from those encountered in interpretation), I can usually get up, take care of them, and come back. Not so with interpretation. Physical conditions in interpretation have to be endured until the opportunity arises to cope with them, and when you’re unprepared for how to deal with them they can cause added stress that makes it difficult to think calmly and rationally.

In the area of mental strain, which is highly individualistic and so will probably be different for other people, I found differences as well. There is a lot of mental fatigue in translation, because you’re performing the same highly-mentally-tasking activity for hours at a time. For me this is fatigue is a slow drain, like walking around all day. But when I’m interpreting, it’s a large fast drain, like sprinting. There’s more on-your-feet thinking. Your memory gets more of a workout: you have to stretch yourself to remember all the linguistic stuff, yes, but also to remember all the research you’ve done on the relevant people/topics, and more importantly everything that’s been said and is being said. Statements can be long and sometimes meander many places before there’s a break for you to begin repeating them in the other language. Holding all that stuff in your head until you can regurgitate it while at the same time figuring out how to regurgitate it in the target language stretches memory and intellect both at once. One of those two things may give. After the first panel with Mr. Amano I quickly learned to bring more paper and take more notes, jotting down key words as soon as the sentence began to jog my memory in case the sentence’s end was a long way off.

But translation and interpretation are BOTH about research.

Yep. I’ve said many times that translation is all about research, and I think interpretation is the same way. Before I went to meet and interpret for Mr. Amano I visited his website, printed out Japanese Wikipedia’s entire article about him, and went through and listed the names of the main characters in all the Final Fantasy games in both English and Japanese. All of it was useful. Familiarizing yourself with the person and the relevant topics to the extent possible is key. Since this was a last-minute gig I didn’t get a chance to do much more than Wikipedia, but every little bit helps. In particular, I remember Mr. Amano talked about a work of his called “New York Salad” which I never would have understood or been able to cope with if I hadn’t already known the work existed. Plus, both the client and his agent were immediately set at ease when we met because I had done this basic research, and that’s important as well. Apparently Mr. Amano once got stuck with an interpreter who didn’t know anything about his work, didn’t know who Picasso was, and had never heard of Final Fantasy!