<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Durf.org &#187; work</title>
	<atom:link href="http://www.durf.org/category/work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.durf.org</link>
	<description>Live from the world&#039;s largest Japantown</description>
	<lastBuildDate>Wed, 21 Jul 2010 10:02:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>My bookshelf</title>
		<link>http://www.durf.org/2010/07/06/my-bookshelf/</link>
		<comments>http://www.durf.org/2010/07/06/my-bookshelf/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 07:37:01 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[Japan]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=566</guid>
		<description><![CDATA[Like the title says. These are some of the paper references I use in my work as a translator and editor. (The links take you to amazon.co.jp pages on the things.) Of course I do plenty of research and look up lots of terms online, but Wikipedia and Google and so on have yet to [...]]]></description>
			<content:encoded><![CDATA[<p>Like the title says. These are some of the paper references I use in my work as a translator and editor. (The links take you to amazon.co.jp pages on the things.) Of course I do plenty of research and look up lots of terms online, but Wikipedia and Google and so on have yet to replace the dead trees in my life.</p>
<div style="text-align:center;"><img src="http://www.durf.org/wp-content/uploads/2010/07/imagesdictionaries1.jpg" alt="dictionaries.jpg" border="0" width="440" height="248" /></div>
<p><span id="more-566"></span></p>
<h3>J-J dictionaries</h3>
<p><a href="http://www.amazon.co.jp/dp/4385139059/">大辞林</a> &#8211; I have this in paper, as well as in data for use in <a href="http://dicwizard.jp/logophile/">Logophile</a>; I even bought the <a href="http://www.monokakido.jp/iphone/daijirin.html">iPhone app</a> too since it&#8217;s so nicely done there.</p>
<p><a href="http://www.amazon.co.jp/dp/400080121X/">広辞苑</a> &#8211; This is considered the &#8220;standard&#8221; J-J dictionary, but I don&#8217;t like it as much as things like 大辞林 and 大辞泉 (another one I have at home) since it lists definitions in their historical order, so you have to wade through a bunch of archaic meanings before you get to what words mean today. (See what lexicon whiz Tom Gally has to say about this in his <a href="http://gally.net/translation/kokugo.htm">very informative page</a> on Japanese [国語] dictionaries.) That said, it&#8217;s a classic reference and as such it has a place on my shelf, as well as in data form in Logophile.</p>
<p>Some good 漢和辞典. These seem to have fallen by the wayside to a greater extent than anything else in my collection, but I do browse through them from time to time.</p>
<p>The <a href="http://www.amazon.co.jp/dp/409521001X/">日本国語大辞典</a> by Shōgakukan is one I use at the office. I don&#8217;t have my own copy because it costs nearly ¥200,000 to assemble all the volumes; that Amazon link is just for volume 1. But this is the Japanese answer to the OED, basically: the biggest out there.</p>
<p>Also in the &#8220;have it at the office and lack shelf space for it at home&#8221; category is the <a href="http://www.amazon.co.jp/dp/4095261072/">日本大百科全書</a>, or <em>Encyclopedia Nipponica</em>. I do have this in data format as well. It came with a Sony electronic dictionary my wife was kind enough to get for me for my birthday some years ago. It is also searchable via Logophile, which makes it very handy indeed.</p>
<h3>J-E dictionaries</h3>
<p><a href="http://www.amazon.co.jp/dp/4767420261">Kenkyusha&#8217;s New Japanese-English Dictionary</a> &#8211; This is called the &#8220;green goddess&#8221; by translators for its cover color; it&#8217;s a standard reference. (The <a href="http://www.amazon.co.jp/dp/4767410266/">E-J version</a> is the &#8220;brown behemoth.&#8221;) The fifth edition is a fantastic improvement on the fourth and deserves a place on the serious learner&#8217;s bookshelf. A <a href="http://www.amazon.co.jp/dp/B000A17CNM">CD-ROM version</a> is also available. You can also purchase online access to a <a href="http://kod.kenkyusha.co.jp/service/">frequently updated version</a>.</p>
<p><a href="http://www.amazon.co.jp/dp/0804820368/">The New Nelson Japanese-English Character Dictionary</a> &#8211; The best-known of all the 漢英 Japanese resources. This (well, the second revised edition) is the book I used in my university days to pound kanji into my head.</p>
<p><a href="http://www.amazon.co.jp/dp/0939657481/">Bungo Manual</a> &#8211; This little book is a great one for advanced learners who want to puzzle out the meanings of some older forms in the language. Classical Japanese isn&#8217;t something you need to be able to read on a daily basis, but exposure to its forms will help you decipher a lot of the things that you do see in use in Japanese to this day.</p>
<p><a href="http://www.amazon.co.jp/dp/0804820422/">A Dictionary of Japanese Food</a> &#8211; This slender volume has come in handy a number of times. Nice to have as a general reference when living in Japan, even if you aren&#8217;t a translator.</p>
<h3>E-E references</h3>
<p><a href="http://www.amazon.co.jp/dp/0764571257/">Webster&#8217;s New World College Dictionary</a> &#8211; This is our desk dictionary at the office; that means it decides how we spell things for our publications (unless a client tells us otherwise). We use this in conjunction with the <a href="http://www.amazon.co.jp/dp/013953654X/">Webster&#8217;s New World Speller/Divider</a>, which is a small book with sturdy pages for rapid flipping. A much better choice when you&#8217;re proofing a layout and want to quickly confirm a word&#8217;s spelling or a hyphenation choice. Perhaps not so useful to people not in the publishing industry, though.</p>
<p><a href="http://www.amazon.co.jp/dp/0226104036/">The Chicago Manual of Style</a> &#8211; Our house style guide at Japan Echo Inc. It looks like the 16th edition will be coming out later this summer. We have an additional guide about 10 pages long to set down our rules for things not covered in Chicago; many of these match the rules you can find in . . .</p>
<p><a href="http://www.amazon.co.jp/dp/1880656302/">Japan Style Sheet</a> &#8211; This little style guide is put out by the <a href="http://swet.jp/">Society of Writers, Editors, and Translators</a> and is worth owning if you do any writing on Japan.</p>
<div style="text-align:center;"><a href="http://www.flickr.com/photos/62787200@N00/3348824442" title="View 'Battle scars' on Flickr.com"><img alt="Battle scars" src="http://farm4.static.flickr.com/3546/3348824442_ca6e8ba3dc.jpg" border="0" width="500" height="334"/></a></div>
<p>Other style guides. One major client prefers that we use the <a href="http://www.amazon.co.jp/dp/0465012620/">Associated Press Stylebook</a> (AP just came out with a new edition that I need to pick up). I also have the <a href="http://www.amazon.co.jp/dp/1846681758/">Economist</a> and <a href="http://www.amazon.co.jp/dp/081296389X/">New York Times</a> manuals for my own reading pleasure.</p>
<p>There&#8217;s also a handy little book called <a href="http://www.amazon.co.jp/dp/4789008770">和英翻訳データブック</a> put out by the Japan Times. This one, and its predecessor (<a href="http://www.amazon.co.jp/dp/4789005496/">英文ライターのための和英翻訳ハンドブック</a>), have largely been replaced by the Web when it comes to searching for the official English name of some government department or whatever, but when I&#8217;m translating a text that refers to the central bureaucracy as it stood in the 1990s, say, these are lifesavers. If JT ever puts out a new version I&#8217;ll likely get it too. Handy little Japan references for translators and reporters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/07/06/my-bookshelf/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Japan Echo Web</title>
		<link>http://www.durf.org/2010/07/05/japan-echo-web/</link>
		<comments>http://www.durf.org/2010/07/05/japan-echo-web/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 10:05:31 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[Japan]]></category>
		<category><![CDATA[translation]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=549</guid>
		<description><![CDATA[My company&#8217;s latest project, Japan Echo Web, went online this afternoon. (It will do the same in Chinese in a couple days.) Here&#8217;s a post to mark the occasion and to give an overview of what has happened over the last year or so. The history The journal Japan Echo got its start in 1974. [...]]]></description>
			<content:encoded><![CDATA[<p>My company&#8217;s latest project, <a href="http://www.japanechoweb.jp/">Japan Echo Web</a>, went online this afternoon. (It will do the same in Chinese in a couple days.) Here&#8217;s a post to mark the occasion and to give an overview of what has happened over the last year or so.</p>
<div style="text-align:center;"><img src="http://www.durf.org/wp-content/uploads/2010/07/imagesjelogo.png" alt="jelogo.png" border="0" width="396" height="73" /></div>
<p><span id="more-549"></span></p>
<h3>The history</h3>
<p>The journal <em>Japan Echo</em> got its start in 1974. From the beginning it was positioned as a channel for high-quality translations of Japanese views on Japan: at the time the country&#8217;s leaders were concerned that the Japanese voice wasn&#8217;t reaching the world as it should, and this was one move to help develop a persuasive global presence for the country as a more complex place than simply the home to a bunch of industrious radio and auto manufacturers.</p>
<p>Just as importantly, from the beginning the magazine—and the company producing it—was structured so as to prevent it from being a government mouthpiece. Mochida Takeshi, the firm&#8217;s first president, laid down rules that said Japan Echo Inc. would never take on &#8220;OBs&#8221; from the Ministry of Foreign Affairs or other government agencies. This kept the organization from turning into yet another <em>amakudari</em> playground for senior bureaucrats. At the same time, he carved out an editorial stance for the magazine that kept it able to select from the broadest possible range of Japanese journals for its source materials. There were no limits to what could be selected by the (again, governmentally independent) editorial board for translation and publication. (There were other limits in place, though, which I&#8217;ll get to in a bit.)</p>
<p>This continued through 2009, and volume 36 of the magazine. Most of our readers during these decades likely obtained their copies courtesy of the Japanese government, as the Foreign Ministry purchased part of our print run and distributed it via Japan&#8217;s embassies and consulates to university libraries, government agencies, and researchers all around the world. MOFA was always our largest institutional subscriber in this sense, and our primary source of revenue for the magazine. (In the early years this was synonymous with the company as a whole, but over time we&#8217;ve developed a much more diverse set of clients and we make our money translating and publishing stuff for all sorts of public- and private-sector outfits today.)</p>
<p>When the end came, it was due to <em>jigyō shiwake</em>, the Democratic Party of Japan&#8217;s process of shaking waste out of public spending on various projects. The DPJ examiners judged that government ministries had no business purchasing magazines in bulk from private publishers. This put an end to the Japanese-language <em>Gaikō Forum</em> as well as our production. Vol. 37, No. 2 of <em>Japan Echo</em> was published in April 2010, bringing the magazine to its end.</p>
<p>You can see more on the magazine&#8217;s history and end in the essays from its <a href="http://www.japanecho.com/sum/2010/370216.html">publisher</a> and <a href="http://www.japanecho.com/sum/2010/370201.html">editor in chief</a> in the final issue. </p>
<h3>What&#8217;s changed</h3>
<p>Japan Echo Web is online now. Some of us would have preferred an entirely new name for this thing, given its new format, but the powers that be made the choice to keep &#8220;Japan Echo&#8221; in there. There are still some significant differences between what&#8217;s online now and what was once put out on paper, though.</p>
<div style="text-align:center;"><img src="http://www.durf.org/wp-content/uploads/2010/07/imagesjeweb_cap.png" alt="jeweb_cap.png" border="0" width="440" height="180" /></div>
<p>First, it is no longer an independently published journal. This is a Ministry of Foreign Affairs project, as noted on the <a href="http://www.japanechoweb.jp/about">site&#8217;s &#8220;about&#8221; page</a>. While the editorial board remains mostly the same as before, and we have the same people working on the production side, MOFA has more say over what does and does not go into it. As Shiraishi Takashi writes in his opening comment, “In order to keep the publication from being government propaganda, though the views of the Foreign Ministry are to be considered, the editor in chief is to have final say over the editorial content.” This is no promise that the consideration of MOFA views will be minimal, though. It&#8217;s something to watch.</p>
<p>Second, it is no longer drawing on the same source texts. Japanese copyright law states that we have to get permission from the author and publisher of a Japanese article if we want to publish it in English, and while most authors (with a few notable exceptions over the years) love seeing their stuff made available via the web to a global audience, the publishers of the monthly magazines like <em>Bungei Shunjū</em> and <em>Sekai</em> tend to deny permission to publish such translations online. There are a hundred thousand blogs out there written by people who ignore these restrictions, or have no idea that they exist in the first place, but we don&#8217;t exactly have the same luxury.</p>
<p>The two major monthlies that are happy to let us translate their articles for online use are <em>Voice</em> (PHP Institute) and <em>Chūō Kōron</em> (Chūō Kōron Shinsha). So you can expect to see articles chosen from their pages, along with interviews we do ourselves and pieces we commission from academics and government officials and so on.</p>
<p>Third, it&#8217;s going to be updated more than once every two months. We&#8217;ll be posting major articles on a monthly basis, with two months&#8217; worth representing a single &#8220;issue&#8221; of the journal as before. (And there will in fact be a printed edition of articles selected from the site, published every two months; that will mainly be for MOFA&#8217;s own distribution purposes, though, so you won&#8217;t see it on the Kinokuniya shelves.) There are also blog entries from members of the editorial board, which we hope to get up on a weekly basis. Not exactly the sort of thing to set your RSS reader on fire, but the translation and editing do take time.</p>
<h3>What&#8217;s still the same</h3>
<p>Japan Echo Web is still translated by the same native-English-speaking translators, checked by the same talented Japanese checkers, and edited with the same care as our print version was. We have the same house style as before, so the voice of this content should be the same as what you know from the magazine days. You don&#8217;t get to see my name in there as &#8220;senior editor&#8221; any more, but it&#8217;s still me looking over the texts any number of times before they go out.</p>
<p>And . . . that&#8217;s it, really. It&#8217;s a whole new ball game other than this. For now we&#8217;re still creating this publication, but as our editor in chief notes in his <a href="http://www.japanechoweb.jp/from-editor/jew0105">inaugural comment</a>, we won the right to do this in a competitive bidding process that will be repeated each year going forward. Hardly an efficient way to do things—government rules mandate a 40-day period for entrants to prepare their bid packages, and then there are presentations and judging that take place, so you end up losing two months of each year that could be spent preparing an entire magazine&#8217;s worth of content instead. We&#8217;d love to see this changed to a three- or even five-year contract, but in the present political climate this hardly seems likely.</p>
<p>There are dozens of other little things I could add to this post: All the design decisions that I&#8217;m not crazy about but that had to be made for various reasons. The chance that there will be a &#8220;Japan Echo&#8221; branded publication in the hands of a different company that underbids us for a future annual contract. For the time being, though, we&#8217;re live and there&#8217;s fresh content to prepare for the big update later this month, so back to work.</p>
<p>Happy reading!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/07/05/japan-echo-web/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Job at Japan Echo</title>
		<link>http://www.durf.org/2010/06/07/job-at-japan-echo/</link>
		<comments>http://www.durf.org/2010/06/07/job-at-japan-echo/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 07:57:59 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[Japan]]></category>
		<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=530</guid>
		<description><![CDATA[My employer, Japan Echo Inc., wants to hire a full-time, in-house Japanese-to-English translator and English editor. This is a one-year contract position to begin this summer: if the new person could be in his or her seat on July 1 it would be ideal, although we realize that&#8217;s relatively short notice. The office is in [...]]]></description>
			<content:encoded><![CDATA[<p>My employer, <a href="http://www.japanecho.co.jp/">Japan Echo Inc.</a>, wants to hire a full-time, in-house Japanese-to-English translator and English editor. This is a one-year contract position to begin this summer: if the new person could be in his or her seat on July 1 it would be ideal, although we realize that&#8217;s relatively short notice. </p>
<p>The office is in central Tokyo, handy to Kasumigaseki, Toranomon, and other stations. The work provides good variety, including stuff in the arts and humanities, although the focus tends to be on texts dealing with government, economy, and international relations. </p>
<p>While of course you shouldn&#8217;t take anything I write on my personal website as a promise, there&#8217;s the possibility of a contract extension in 2011 or even a shift to 正社員 status depending on how much work we see coming down the pipe in the longer term and what we think of the individual&#8217;s skills.</p>
<p>If you&#8217;re interested, you&#8217;ll need to complete the trial translation available <a href="http://www.japanecho.co.jp/trial.pdf">on our website</a> [PDF] and send it in with your Japanese-language resume to <a href="mailto:work@japanecho.co.jp">work@japanecho.co.jp</a>. The resume could be a standard 履歴書 format or something you roll yourself; it will be read by some people here who aren&#8217;t translators, though, so we do need it in the language of the land. </p>
<p>Make sure your materials reach us no later than June 15. If you have any questions about the position or the company, you can contact me. Feel free to forward or repost this information. Thanks!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/06/07/job-at-japan-echo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The low-down on the publishing industry</title>
		<link>http://www.durf.org/2010/05/06/the-low-down-on-the-publishing-industry/</link>
		<comments>http://www.durf.org/2010/05/06/the-low-down-on-the-publishing-industry/#comments</comments>
		<pubDate>Thu, 06 May 2010 09:27:05 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=509</guid>
		<description><![CDATA[Sci-fi author Charles Stross is writing a series of blog entries on Common Misconceptions About Publishing. Interesting reads, particularly number 4, which goes into detail about translation and overseas publishing rights and so on and gives some helpful numbers covering the English-language markets (at least for SF writing). The eighth and most recent entry, not [...]]]></description>
			<content:encoded><![CDATA[<p>Sci-fi author Charles Stross is writing a series of blog entries on <a href="http://www.antipope.org/charlie/blog-static/2010/04/common-misconceptions-about-pu-1.html">Common Misconceptions About Publishing</a>. Interesting reads, particularly <a href="http://www.antipope.org/charlie/blog-static/2010/03/cmap-4-territories-translation.html">number 4</a>, which goes into detail about translation and overseas publishing rights and so on and gives some helpful numbers covering the English-language markets (at least for SF writing). </p>
<p>The eighth and most recent entry, not linked on that index page at the moment, is called &#8220;<a href="http://www.antipope.org/charlie/blog-static/2010/04/cmap-8-lifestyle-or-job.html">Lifestyle or Job?</a>&#8221; It gives some figures on author incomes that should scare you away if you&#8217;re thinking about getting rich as a writer. J-E translator incomes might be getting pinched by bargain-seeking clients and budget-slashing DPJ governments (more on that in an upcoming post), but I think we&#8217;ve still got it better than the folks who have to come up with their own ideas to put into words on the page. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/05/06/the-low-down-on-the-publishing-industry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More on translation choices</title>
		<link>http://www.durf.org/2010/03/29/more-on-translation-choices/</link>
		<comments>http://www.durf.org/2010/03/29/more-on-translation-choices/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 08:33:19 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=484</guid>
		<description><![CDATA[To follow up on the &#8220;whether to add things in translation or hew to the original&#8221; post over here, here are a few quick things from links I&#8217;ve been meaning to address here. First, Matt Treyvaud&#8217;s translation of Mori Ōgai&#8217;s 翻訳について (Hon&#8217;yaku ni tsuite; &#8220;On translation&#8221;): The sweets that Nora eats I translated makuron マクロン. [...]]]></description>
			<content:encoded><![CDATA[<p>To follow up on the &#8220;whether to add things in translation or hew to the original&#8221; post <a href="http://www.durf.org/2010/03/29/translators-additions/">over here</a>, here are a few quick things from links I&#8217;ve been meaning to address here.</p>
<p>First, <a href="http://neojaponisme.com/2010/01/19/haters-gonna-hate-mori-ogai-on-translation/">Matt Treyvaud&#8217;s translation</a> of Mori Ōgai&#8217;s 翻訳について (<i>Hon&#8217;yaku ni tsuite</i>; &#8220;On translation&#8221;): </p>
<blockquote><p>The sweets that Nora eats I translated <i>makuron</i> マクロン. Write rather <i>amedama</i> 飴玉, I was told. Advice like this simply boggles the mind. Tins of almond macaroons have been shipped here in great number so that you may buy them at Aokido whenever you please. Reflect, if you will, on the difference in situation between a woman of the West eating a macaroon and a child of Japan eating an <i>amedama</i>. I recall one scene in a novel by someone-or-other wherein two female university students in Paris&#8217;s Latin Quarter munch on macaroons as they trade stories of heartbreak. To switch those macaroons for <i>amedama</i>, of all things—well, it would certainly be comical. The gist of such teachings is that items should appear in translation as appropriately chosen items unique to Japan, but as for myself, I strive to avoid things unique to Japan, the better to produce an extraordinary effect. Furthermore, we only consider here cases where there is an appropriate corresponding item. When uniquely Japanese and inappropriate items appear, the results are quite unbearable.</p></blockquote>
<p>(Adamu of Mutantfrog Travelogue posted <a href="http://www.mutantfrog.com/2010/01/20/self-proclaimed-veteran-translator-modern-fansubbing-a-mess/"> this entry</a> in response to that Neojaponisme piece. Also interesting, especially the comment discussion there.) </p>
<p>Second is <a href="http://search.japantimes.co.jp/rss/ft20071129a2.html">&#8220;Translator of the universal and the local,&#8221;</a> a <i>Japan Times</i> interview with Meguro Jō, who has translated plays by Martin McDonagh (see also <a href="http://d.hatena.ne.jp/jomeguro/">her blog</a>):</p>
<blockquote><p><b>How do you decide how &#8220;foreign&#8221; to make your translations?</b></p>
<p>Obviously there are cultural gaps, but I prefer to retain some unfamiliar things rather than ignore them or change them into something familiar for Japanese. I don&#8217;t think it&#8217;s right to rework foreign plays as if they were as natural and smooth as plays written in Japanese. We should keep some &#8220;foreignness.&#8221; Getting the balance right is quite sensitive and difficult. English four-letter words, such as f**k—which McDonagh includes a lot—must be translated case by case. Sometimes, I translate them to keep the rhythm, but sometimes I think it is better to cut them.</p></blockquote>
<p>And third, there are of course cases where you can&#8217;t stick closely to the form of the original at all, so you have to get more creative if you want to get the same point across in your target language. I wrote about these so-called <a href="http://www.durf.org/2004/07/26/untranslatability/">untranslatable terms</a> a while ago. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/03/29/more-on-translation-choices/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Translator&#8217;s additions</title>
		<link>http://www.durf.org/2010/03/29/translators-additions/</link>
		<comments>http://www.durf.org/2010/03/29/translators-additions/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 07:36:16 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=482</guid>
		<description><![CDATA[A strict definition of translation tells us that the translator of a text isn’t supposed to add any content to it, or to subtract from it. In a Japanese-to-English job, everything in the original J should be in the target E—no more and no less. This strict definition is the required approach in some types [...]]]></description>
			<content:encoded><![CDATA[<p>A strict definition of translation tells us that the translator of a text isn’t supposed to add any content to it, or to subtract from it. In a Japanese-to-English job, everything in the original J should be in the target E—no more and no less. </p>
<p>This strict definition is the required approach in some types of work. If you’re working on a contract or some other legal document, or even a piece of business correspondence in some cases, your text could be brought into legal proceedings at some point. Will the lawyers be able to point to each term and phrase in the target text and indicate what it matches in the source? Word-for-word translations are what let them do so. </p>
<p>In the areas where I work, this usually isn&#8217;t the best approach, though. The translator’s job is sometimes closer to that of a copywriter—someone who writes a text with a certain goal in mind. This advertisement needs to make the reader want to buy our brand of beer, or think that we&#8217;re operating our business in an eco-friendly manner. This essay needs to convince the reader that our political position is the correct one, or that the other country&#8217;s view is mistaken. When you’re writing toward goals like these, you think more about the impact of the words you use in the target text. What do the readers need? What is their level of background knowledge? How will they react to what you write? Is their reaction what the writer of the source text, or your client, wants to see? </p>
<p>When I do a translation for a Japanese politician, the pendulum can swing to either extreme. This weekend I stayed up late translating on Friday night and did some editing on Saturday of part of Prime Minister Hatoyama&#8217;s Friday afternoon <a href="http://www.kantei.go.jp/jp/hatoyama/statement/201003/26kaiken.html">press conference</a> (Japanese; for English go <a href="http://www.kantei.go.jp/foreign/hatoyama/statement/201003/26kaiken_e.html">over here</a>). For this client (the Kantei) we stick very closely to the Japanese—sentence order, phrasings within those sentences, you name it. In previous translations I&#8217;ve worked on for the Kantei (<a href="">here&#8217;s one</a>) we&#8217;ve resorted to [bracketing the information] that&#8217;s begrudgingly admitted to be necessary for comprehension. Example: </p>
<blockquote><p>J: 第二次補正予算、そして平成２２年度予算の早期成立に全力を尽くします。<br />
E: We will make every effort to secure the early passage of the second supplementary budget [of fiscal 2009] and the fiscal 2010 budget.</p></blockquote>
<p>In a translation for <i>Japan Echo</i> magazine, I&#8217;d toss that &#8220;2009&#8243; in before the supplementary budget without a second thought, but &#8220;Heisei 21&#8243; wasn&#8217;t in the prime minister&#8217;s original words, so there you have it. </p>
<p>The English text I give a politician client might be something else, though, like a speech he&#8217;ll give before an English-speaking audience. It’s rare for that speech to look exactly like the source text provided to me. A Japanese speaker knows that Japanese listeners will understand certain concepts he covers without explanation. This isn’t the case with the English-speaking listeners, though. As I’m translating this document I think hard about the original words, of course, but I also consider the people who will hear what I’m writing. If the Japanese pol is talking about the upcoming upper house contest, and says something like 前回のきびしい選挙結果, will the listeners&#8217; needs be met by “the brutal results of the last election”? In some cases, yes: maybe the speaker already laid down the background for this statement, or maybe the speech will be given before a bunch of scholars of Japanese politics who are up to speed on all of this. In other cases, I need to help them more: “the results for the previous election for the House of Councillors, held in July 2007, in which the ruling LDP suffered a serious setback.”</p>
<p>Not all those words were in the original text. But an informed Japanese listener would understand all that unspoken information—and for a speech, it&#8217;s often the translator&#8217;s job to make sure that the English listeners will come away with the same level of understanding. </p>
<p>Long story short: Translation choices get made depending on more than just the words in the source document. Take <i>that</i>, Google Translate! </p>
<p>(Edit: I just posted a quick follow-up to this one <a href="http://www.durf.org/2010/03/29/more-on-translation-choices/">right here</a>.)</p>
<p>(Edit 2: Added the English version of the prime minister&#8217;s press conference, which just went up. This time the client&#8217;s editor was content to make his own changes instead of sending the MS back to us for revisions, whew.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/03/29/translators-additions/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Et tu, Barack?</title>
		<link>http://www.durf.org/2009/11/19/et-tu-barack/</link>
		<comments>http://www.durf.org/2009/11/19/et-tu-barack/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 15:18:36 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[tech]]></category>
		<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=475</guid>
		<description><![CDATA[Yet another article on how computer technology will save us all from the tyranny of having humans in charge of the task of human communication. A BusinessWeek piece titled &#8220;White House Challenges Translation Industry to Innovate&#8221; tells the tale: Companies have combined the power of humans and computers to simultaneously double the speed of translation [...]]]></description>
			<content:encoded><![CDATA[<p>Yet another article on how computer technology will save us all from the tyranny of having humans in charge of the task of human communication. A BusinessWeek piece titled &#8220;<a href="http://www.businessweek.com/innovate/content/oct2009/id2009101_196515.htm">White House Challenges Translation Industry to Innovate</a>&#8221; tells the tale:</p>
<blockquote><p>Companies have combined the power of humans and computers to simultaneously double the speed of translation and nearly halve its cost. Where each translator once converted 2,500 words a day at a cost of some 25¢ per word, they can now offer 5,000 words a day at around 12¢-15¢ a word.</p></blockquote>
<p>Marvelous. This translator makes the same amount of money per day, according to this math, but turns out twice as much text in the target language. Efficiency up, global understanding up. But there are problems here. A few quick, unorganized thoughts:</p>
<p>Problem 1: We aren&#8217;t worrying about the fact that this means only half as much time can be spent on proper rereading by the translator and editing by a fresh pair of eyes. The hybrid approach of MT to begin and a human to polish the turds that are MT output means there&#8217;s an unhappy person in the mix now—at least I don&#8217;t think many people are happy about wrestling with clumsily translated text. I can&#8217;t stand it when I&#8217;m dealing with stuff a human put together, and even that clumsy human translator is leagues ahead of a machine, and will remain there for the foreseeable future. </p>
<p>Problem 2: The editors who deal with machine output are, ideally, bilingual and capable of doing the translation themselves. If something looks truly odd in your target text, going back to the source text to figure out what&#8217;s going on is the only way to set things straight. (Well, there&#8217;s actually another way: the monolingual editor just makes a wild guess. I didn&#8217;t say it was a <i>good</i> way.) In other words, the ideal form of this man-machine mind meld involves taking a translator who used to be crafting his own sentences and making him clean up the ones a computer spits out at him. Job satisfaction in this new world? Heh. </p>
<p>Problem 3: Don DePalma, chief research officer at a translation outfit, notes that companies need to get their information out there in front of customers in their own languages. &#8220;When you&#8217;re dealing with anything really expensive or that potentially involves a long-term financial decision—like life insurance or stocks—customers prefer to have information in their own language,&#8221; he says. But this is precisely the sort of text that needs to be handled by a specialist, and the companies that sell &#8220;really expensive&#8221; products will be the very last holdouts still using human pros for the entire process. (It would be fun to see someone trying to market life insurance via Google Translate and an editor in Bangalore, though.) It&#8217;s fine to trot this out as proof that companies will need to pay more attention to localizing their material for various markets, but it&#8217;s a poor example to bring into the &#8220;MT is the future&#8221; article. </p>
<p>Problem 4: This.</p>
<blockquote><p>With [human-assisted machine translation] systems, text is fed into a computer program that tackles the first round of word and sentence conversion using statistics, language rules, or matching with past translations. That covers about 90% of the work. A human then steps in to correct mistakes, clarify sentences, and refine the language for the intended audience or market.</p></blockquote>
<p>Anyone who&#8217;s done translation (at least at a level going beyond churning out crap drafts for rock-bottom prices) or editing knows that the 90% figure here is sheer idiocy. Experienced translators don&#8217;t tend to work in phases like this (pump out rubbish at blinding speed and then go back to correct spelling and grammar errors and think about tone and style); they have all these tasks in mind as they go through their text, and it&#8217;s hard as a result to define percentages for the effort going into each one of them. But I think the thing that makes translating between human languages a steep challenge for computers is the need to &#8220;refine the language for the intended audience or market.&#8221; Computers can&#8217;t recognize context like that. Humans can, and for human translators, keeping that context in mind and crafting a target text that meets the needs of style, readership, and client preference accounts for vastly more than 10% of their effort. I&#8217;d suggest flipping this formula around and saying that the computers handle a tenth of the work, not nine times that amount. </p>
<p>Problem 5: &#8220;Language translation is far from being mastered by humans, computers, or any mix of the two.&#8221; This is just annoying. It reeks of creationists&#8217; &#8220;teach the controversy&#8221; demands for equal time for unequal worldviews. Using languages to communicate is <i>what humans do</i>. Birds fly. Fish swim. We talk. What mastery there is in the field of translation belongs entirely to people, and articles like this one need to be written from the perspective of how close computers are to reaching that standard. </p>
<p>Anyway. Enough problems. I&#8217;m of two minds when it comes to predicting the future of machine translation. On the one hand, I think the human capacity for language is too deep and too broad for machines to ever take it over completely, and even if 90% of clients end up happy with dirt-cheap mediocrity, the 10% of clients still paying for human quality will represent a healthy chunk of a growing language-services pie. So the good translators will still be making money, and it won&#8217;t be by massaging the output of a Google data center. </p>
<p>On the other hand, though, if the scientists ever crack this mystery wide open (perhaps by giving up on computers with nothing but 0s and 1s to deal with and creating new machines that function more like a brain) then we&#8217;ll get our translating machine. I&#8217;ll be out of a job, along with all my translator and interpreter buddies. But of course we&#8217;ll have plenty of company in the unemployment lines, since computers with real thinking power will already have taken over more menial tasks like piloting airplanes, writing software, drafting legislation, teaching children . . . </p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2009/11/19/et-tu-barack/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Breaking into the Industry</title>
		<link>http://www.durf.org/2009/05/25/breaking-into-the-industry/</link>
		<comments>http://www.durf.org/2009/05/25/breaking-into-the-industry/#comments</comments>
		<pubDate>Mon, 25 May 2009 14:50:23 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=426</guid>
		<description><![CDATA[Yet another of those translation-related essays for the JET folks. I talk about the &#8220;CIR experience&#8221; below, but there are people with the language skills they need to get onto the low rungs of the translation ladder working Eikaiwa or JET language-teacher jobs too. Hope you find it interesting. After spending their years as coordinators [...]]]></description>
			<content:encoded><![CDATA[<p><i>Yet another of those translation-related essays for the JET folks. I talk about the &#8220;CIR experience&#8221; below, but there are people with the language skills they need to get onto the low rungs of the translation ladder working Eikaiwa or JET language-teacher jobs too. Hope you find it interesting.</i></p>
<p>After spending their years as coordinators for international relations and picking up some translation skills along the way, some soon-to-be JET graduates think about making the move to the language services industry. There are plenty of people out there working as translators, but how did they get that work? </p>
<p>A quick look at the situation might make it seem like a Catch 22: employers are all looking for someone with relevant experience, but you can’t get that without finding an employer to take you on. This might come across particularly in specialized fields like financial or legal translation. </p>
<p>Not all is hopeless, though. There are ways to market yourself more effectively to potential employers, and there are things you can do right now to prepare yourself for the job search when the time comes. The first of these things is fairly obvious:</p>
<h3>Get Good</h3>
<p>You’ll have an easier time getting a job as a translator if you’re more talented in translation to begin with. There are four tasks you’ll want to pursue during your time as a CIR in this connection: </p>
<ol>
<li>Do jobs. This goes without saying, really. If your CIR assignments involve translation, focus on that work and polish your skills while you produce the texts your employer needs. If you aren’t doing much translation, look around for projects you could propose—a multilingual municipal website, signage for local tourist sites, and so on.</li>
<li>Get feedback. This is something that’s not always easy to do, but ideally you want to show your work to native Japanese speakers, who will tell how you’re doing in staying faithful to the source material, and native speakers of your language, who will set you straight when what you write looks like it came from a robot instead of a human author.</li>
<li>Network. If you’re involved in an online forum focused on your current job you’re doing this already, to some extent; take part in discussions on translation techniques to focus that networking. (This could be a good way to get the feedback you need, too.) Consider joining groups like JAT or SWET (see the links below), or at least attending their meetings when you can; you don’t need to be a member for that. Go to IJET or an ATA meeting. Industry people you’ve met in person are people who will remember you later when you come looking for a way into the industry.</li>
<li>Pay attention. Read plenty of Japanese—to get better at it, but also to get more knowledgeable about what’s being written about. Read plenty in your own language, too. You need to develop an ear for appropriate, persuasive voices in the different fields where you may one day do work of your own.</li>
</ol>
<h3>Get Focused</h3>
<p>Most established translators will tell you that the way to success in this business is not to do anything and everything that comes your way, but to specialize in an area you enjoy. (This should also be an area with real demand for translation services. Lots of people like manga, but the population that’s paying real money for translated manga isn’t large enough to support a lot of well-paid translators in that segment. In other words, don’t think of entering a field where your competition is a bunch of college students working for free.) </p>
<p>It can help to think of high-quality, high-paying translation as a donut. In the middle are all those people (I was one) who started off with language skills and not much else: Japanese majors, linguists, aimless bilinguals. On the outside of the donut are all the industries that make up the modern economy. It looks like this:</p>
<p><img align="center" src="http://durf.org/images/translation-industry.png"></p>
<p>As the pure linguists develop an interest in some particular field, they learn more about it. The more field-specific knowledge they gain and pair with their language talent, the better they are at translating things related to that field, and the more money they can charge for it. The people on the outside, meanwhile—many high-paid translators fall in this category—begin with a career and experience and gain the language skills as they go on. In the end we all find ourselves in the donut. (Needless to say, we all continue learning on both sides of this equation throughout our careers; nobody starts off with perfect command of two languages, or encyclopedic knowledge of an industry.) </p>
<h3>Get a Job</h3>
<p>There are freelance and in-house translators, and the former will often claim that they are in the best position: they make more money, they pick their clients, they set their hours. The latter, meanwhile, will point out that they don’t have to do sales, write estimates, bill clients, withhold their own taxes, or pay for their own office space. There are pluses and minuses on both sides.</p>
<p>In the early part of your career, though, the pluses are overwhelmingly on the in-house translation side. It’s possible to start out by marketing your services directly to clients, but it’s far easier to let the company’s sales department do that job, while you focus on becoming a better translator. </p>
<p>The <i>Japan Times</i> carries classified ads on Mondays that usually contain at least a few translation job offers. The paper also has an <a href="http://jobs.japantimes.jp/">online ads section</a>, so take a look there, too. The Honyaku, SWET, and JAT mailing lists all see occasional job postings. Lurk on the lists (membership is only required for the last one) and respond to things that interest you. </p>
<p>Joining JAT, as mentioned above, is a way to meet translators; it’s also a way to create your very own <a href="http://members.jat.org/users/pdurfee">member profile</a> on the JAT website. I get a few emails each month asking me to sign up for freelance work or get in touch regarding a project. You can also set up a profile at <a href="http://honyakuhome.org/user/132">Honyaku Home</a>, which doesn’t cost a thing.</p>
<p>What about that Catch 22 described earlier? You need experience to get the job to get experience . . . But you can get some of that experience earlier. Freelance work is a way to get your feet wet, and can be done on the side in some cases. (All situations are different, of course; you may want to check with your employer to confirm that this is all right to do.) In addition to the above sites that let you put together an online profile, magazines like <a href="http://www.tsuhon.jp/">通訳翻訳ジャーナル</a> and websites like <a href="http://www.alc.co.jp/">スペースアルク</a> contain lots of information on translation agencies. The shotgun approach can work: send your resume to 50 agencies and do the trials that some of them send back. You can apply directly with companies like Simul International, too; see the <a href="http://www.simul.co.jp/corporate/recruit/interpreters-and-translators.html">Simul website</a> for information on doing a trial and registering as a freelancer. Even my employer has an <a href="http://www.japanecho.co.jp/job.html">open invitation</a> to people who want to do work for us. </p>
<p>When a company says something like “three years experience required,” it often isn’t a hard requirement. When applying for jobs, don’t forget to add a mental <i>or equivalent</i> to the end of phrases like those, and boldly send your application in just the same. The worst that can happen is a “No thank you” note or phone call, and you won&#8217;t have a job with that firm—but that&#8217;s exactly where you are right now. Be confident, too. You don’t have years of experience as a full-time translator, but CIR experience shows that you’ve functioned in a Japanese office setting, doing many of the tasks these employers are looking for. </p>
<p>Consider also casting your net a bit wider. You may want a job as a translator, but look at the ads for positions like “in-house editor” and “communications specialist” as well. These are jobs that can involve lots of brushing up other people’s translations, but once you’re on the inside of an organization doing this work you will have a shot at taking it on yourself. And because translation is a writing skill in the target language, producing copy for a company is a good way to get better at all forms of writing, including translation. Even executive secretaries do their fair share of translation work, and can find themselves transferred to divisions doing purer word work later on. </p>
<h3>Get Informed</h3>
<p>Below are some links to online information that you might find helpful:</p>
<p><a href="http://www.languagerealm.com/xlationarticles/xlation_articles.php">Articles About Translation</a> (Language Realm)<br />A good collection of essays on the language services industry. The “Translation as a Profession” series in particular is worth a look. </p>
<p><a href="http://gally.net/translation/gettingstarted.htm">Getting Started as a Translator: Gleanings from Honyaku</a><br />A collection of posts from Honyaku mailing list threads going back to 1994. Very applicable to the field, even a decade or more later. </p>
<p><a href="http://flickr.com/photos/tr4nslator/sets/72157594582358296/">Translation as Vocation</a><br />A slideshow that accompanied a March 2007 presentation on ways to break into the field of J-E translation. </p>
<p><a href="http://whatever.scalzi.com/2004/12/17/john-scalzis-utterly-useless-writing-advice/">John Scalzi’s Utterly Useless Writing Advice</a><br />Not on translation per se, but it’s a worthwhile read for all people who want to write words for money. </p>
<p><a href="http://groups.google.com/group/honyaku">Honyaku</a><br />This is a mailing list where translators facing problems in a job ask for help. There&#8217;s also occasional discussion of matters peripherally related to dealing with words on pages, so it can be good to lurk and learn. Job offers come down this pipeline from time to time, too.</p>
<p><a href="http://swet.jp/">The Society of Writers, Editors, and Translators</a><br />This group holds monthly meetings on topics you may find interesting. The mailing list is free to join for nonmembers; become a member for reduced admission to those meetings and a spot in the SWET directory.</p>
<p><a href="http://www.jat.org/">The Japan Association of Translators</a><br />This group also holds monthly meetings in Tokyo, as well as other places in Japan and around the world from time to time. The profile you can create here as a member will attract messages from agencies looking to add people to their rosters. JAT organizes the annual IJET conferences (coming up next in <a href="http://ijet.jat.org/ijet-21/">Miyazaki</a> in April 2010), which are great to attend. The organization was also crazy enough to elect me director as of May 2009.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2009/05/25/breaking-into-the-industry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Correct Translation</title>
		<link>http://www.durf.org/2009/03/11/the-correct-translation/</link>
		<comments>http://www.durf.org/2009/03/11/the-correct-translation/#comments</comments>
		<pubDate>Wed, 11 Mar 2009 09:37:29 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=384</guid>
		<description><![CDATA[Posting another one of those translation essays I wrote for some people on the JET Program: “Can you look over this translation to make sure it’s correct?” This is the sort of request you might hear from time to time. What does correctness mean in this case, though? There are many ways to measure how [...]]]></description>
			<content:encoded><![CDATA[<p><i>Posting another one of those translation essays I wrote for some people on the JET Program:</i></p>
<p>“Can you look over this translation to make sure it’s correct?” This is the sort of request you might hear from time to time. What does correctness mean in this case, though? There are many ways to measure how good a translation is—its accuracy, its effectiveness, and even its beauty might be yardsticks to use. But the yardstick you choose depends on context. And context, as we have seen, means more than just words on the page. </p>
<p>Let’s start with this short statement from the website of the <a href="www.tatemonoen.jp/about">Edo-Tokyo Open Air Architectural Museum</a>:</p>
<blockquote><p>江戸東京たてもの園は、1993年（平成5年）3月28日に開園した野外博物館です。都立小金井公園の中に位置し、敷地面積は約７ヘクタール、園内には江戸時代から昭和初期までの、27棟の復元建造物が建ち並んでいます。当園では、現地保存が不可能な文化的価値の高い歴史的建造物を移築し、復元・保存・展示するとともに、貴重な文化遺産として次代に継承することを目指しています。</p></blockquote>
<p>This is fairly straightforward information. We’ll begin by putting together a similarly straightforward English version along these lines: </p>
<blockquote><p>The Edo-Tokyo Open Air Architectural Museum is an outdoor museum that opened on March 28, 1993 (Heisei 5). Located in Tokyo Metropolitan Koganei Park, the museum is about 7 hectares in size; on its grounds are 27 restored buildings dating from the Edo period to the early Showa era. Historical structures with high cultural value that cannot be preserved on their original sites are moved to the museum, where they are restored, preserved, and displayed, with the goal of handing them on to the next generation as a precious cultural heritage. </p></blockquote>
<p>This translation adheres closely to the original Japanese in the order in which it presents the information. Does this make it the correct translation? . . . Maybe.</p>
<h3>What is the purpose of this translation?</h3>
<p>If your boss asked you to translate this site because he wanted a quick look at what it says, your job is done at this point. You’ve provided all the relevant information, and your translation is a correct fit for the task at hand. </p>
<p>If, however, your job is to create an English version of the site to inform potential visitors who don’t read Japanese, you need to work on this text some more. You aren’t just laying out information; you’re advertising the museum, and that means making your translation more attractive. Present the place as exciting, educational, and worth a trip to Koganei. </p>
<blockquote><p>The Edo-Tokyo Open Air Architectural Museum, located in Koganei Park, features 27 restored buildings dating from the Edo period to the early Showa era. These culturally valuable structures were moved to the museum when they could no longer be preserved on their original sites. Here they are carefully restored, displayed, and preserved as a precious cultural heritage to be passed on to future generations.</p></blockquote>
<p>It’s shorter now, and we’ve lost some information. But that wasn’t likely to motivate people to come see the preserved structures—readers won’t care so much when the place was established, and “Heisei 5” is particularly unhelpful; the full name of the park is similarly unneeded here. It’s no longer an exact match for the Japanese, but for our advertising purposes this might be a correct translation.</p>
<h3>What do the readers need?</h3>
<p>Above we took out the Heisei year designation. Japanese readers may appreciate that information, but foreign readers aren’t apt to count years according to imperial reigns. We need to consider what our readers will want from the text, and provide them with a translation that serves their needs. </p>
<p>Perhaps the English website will help direct visitors to this place. In that case we’ll need some geographic pointers. Perhaps the visitors would benefit from additional historical background—not everyone knows when the “Edo period” was, for instance. Here we go again:</p>
<blockquote><p>The Edo-Tokyo Open Air Architectural Museum opened in March 1993 in Koganei Park, north of Musashi Koganei station in western Tokyo. The expansive outdoor museum contains 27 restored buildings dating from the eighteenth through the mid-twentieth centuries. Historical structures from around the Tokyo area that cannot be preserved on their original sites are restored, preserved, and displayed on the museum grounds, with the goal of handing these precious cultural properties on to the next generation.</p></blockquote>
<p>Note also that not all readers will be familiar with the hectare as a unit of area, and the exact size of this place isn’t vital information in any case. This isn’t a history essay, so we don’t need to give the precise years for the Showa era. A quick look around the website lets us know that the buildings date from the middle of the Edo period to the early postwar era; we use that information here.</p>
<h3>What does the client want?</h3>
<p>In addition to thinking about the sort of text you’re writing and the needs of your readers, you have to consider what the client wants to see in your translation. Japanese bureaucrats often prefer to see a particular flavor of English writing—a “governmentese” that isn’t necessarily natural, but is a very straight translation with which they are comfortable. (The first draft above might be a good fit for them.) </p>
<p>Maybe this client wants to put together a pamphlet for kids. You’ll be asked to write for younger readers in this case: </p>
<blockquote><p>The Edo-Tokyo Open Air Architectural Museum was founded in 1993. This large museum in Tokyo’s Koganei Park contains 27 historical buildings. Some of these are very old, dating all the way back to the middle of the Edo period—that was hundreds of years ago! When these important buildings from around Tokyo were about to be torn down, people worked to save them, bringing them all the way to this museum. Here these cultural structures are preserved so people can continue enjoying them today, and into the future.</p></blockquote>
<p>The sentences are shorter. The vocabulary is simpler. And the text is more energetic, to hold the children’s attention. (We might also note that some of the buildings here inspired Miyazaki Hayao’s art in <i>Spirited Away</i>.) If the client comes to you with a request for a certain kind of language, it’s your job to produce that. Stay flexible!</p>
<p>In its most basic form, translation requires you to include all the information in the original, adding nothing and taking nothing away. But translators are called on to do jobs closer to copywriting much of the time. The examples above show some very different approaches to the same paragraph in Japanese, but depending on the kind of writer you are, the needs of your readers, and the demands of your client, they might all be correct. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2009/03/11/the-correct-translation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keeping things cool</title>
		<link>http://www.durf.org/2008/07/07/keeping-things-cool/</link>
		<comments>http://www.durf.org/2008/07/07/keeping-things-cool/#comments</comments>
		<pubDate>Mon, 07 Jul 2008 11:31:59 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[Japan]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.durf.org/2008/07/07/keeping-things-cool/</guid>
		<description><![CDATA[A quick post to note that I&#8217;ve uploaded more photos to the Flickr set of shots from Hokkaido. I wrote about what&#8217;s happening over on the SWET blog, so I&#8217;ll just point you that direction instead of reprinting everything here. One update to that previous post: I haven&#8217;t been arrested or interrogated about the bits [...]]]></description>
			<content:encoded><![CDATA[<div style="float: right; margin-left: 10px; margin-bottom: 10px;">
 <a href="http://www.flickr.com/photos/durf/2645101625/" title="photo sharing"><img src="http://farm4.static.flickr.com/3120/2645101625_3095fc0d13_m.jpg" alt="" style="border: solid 2px #000000;" /></a>
</div>
<p>A quick post to note that I&#8217;ve uploaded more photos to the <a href="http://flickr.com/photos/durf/sets/72157605983000112/">Flickr set</a> of shots from Hokkaido. I wrote about what&#8217;s happening over on the <a href="http://www.swet.jp/index.php/weblog/live_from_toyako/">SWET blog</a>, so I&#8217;ll just point you that direction instead of reprinting everything here. </p>
<p>One update to that previous post: I haven&#8217;t been arrested or interrogated about the bits of electronic detritus in the hotel wastebasket. Apparently someone here could tell the difference between a broken SD card reader and a left-over missile timing device. Lucky me.<br />
<br clear="all" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2008/07/07/keeping-things-cool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
