<?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; web</title>
	<atom:link href="http://www.durf.org/category/web/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 Dec 2011 03:34:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>It&#8217;s ice cream time</title>
		<link>http://www.durf.org/2011/06/28/its-ice-cream-time/</link>
		<comments>http://www.durf.org/2011/06/28/its-ice-cream-time/#comments</comments>
		<pubDate>Tue, 28 Jun 2011 02:53:16 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[fun]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=694</guid>
		<description><![CDATA[I have to admit, I liked Stoyn.com a whole lot better when I thought there were actually booze-flavored popsicles shaped like Marxist revolutionaries and Disney characters and the like. Still a fun site put together by an &#8220;ambient advertising agency.&#8221;]]></description>
			<content:encoded><![CDATA[<p>I have to admit, I liked <a href="http://stoyn.com/">Stoyn.com</a> a whole lot better when I thought there were actually booze-flavored popsicles shaped like Marxist revolutionaries and Disney characters and the like. Still a fun site put together by an &#8220;ambient advertising agency.&#8221;</p>
<p><a href="http://www.durf.org/wp-content/uploads/2011/06/mario.jpg"><img src="http://www.durf.org/wp-content/uploads/2011/06/mario.jpg" alt="Mario popsicle" title="mario" width="330" height="500" class="alignleft size-full wp-image-695" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2011/06/28/its-ice-cream-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Full Frontal Translation</title>
		<link>http://www.durf.org/2011/02/07/full-frontal-translation/</link>
		<comments>http://www.durf.org/2011/02/07/full-frontal-translation/#comments</comments>
		<pubDate>Mon, 07 Feb 2011 08:38:41 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=658</guid>
		<description><![CDATA[That&#8217;s right, totally nude, letting you see it all. In December I posted about EtherPad, an online tool that lets you type up a document while keeping track of every single change made to it—every character typed, moved, replaced, or deleted. I went ahead and did a short translation with EtherPad last month, which you [...]]]></description>
			<content:encoded><![CDATA[<p>That&#8217;s right, totally nude, letting you see it all. In December I <a href="http://www.durf.org/2010/12/22/letting-writers-hit-rewind-play/">posted about EtherPad</a>, an online tool that lets you type up a document while keeping track of every single change made to it—every character typed, moved, replaced, or deleted. I went ahead and did a short translation with EtherPad last month, which you can view <a href="http://ietherpad.com/ep/pad/view/ZiQFES0pbD/rev.2">right here</a>. (Click the play button at top right to see the Japanese get overwritten with my English.)</p>
<p>This isn&#8217;t a particularly splendid translation of mine, but I&#8217;m tossing it out there as a general example of how I tend to zip through a quick translation when it lands on my desk. One shortcoming of this approach to sharing the translation process with others is that it doesn&#8217;t let you indicate where you went offline to look at a dictionary or other reference. I did stick in a couple URLs that I used while putting the text together, though. This translation was for a competitive bid on a project that our company ended up not getting—not sure if that&#8217;s because my translation was outclassed or because our price outclassed all the others. Oh well.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2011/02/07/full-frontal-translation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The death of etymology</title>
		<link>http://www.durf.org/2011/01/25/the-death-of-etymology/</link>
		<comments>http://www.durf.org/2011/01/25/the-death-of-etymology/#comments</comments>
		<pubDate>Tue, 25 Jan 2011 12:16:55 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[language]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=654</guid>
		<description><![CDATA[An update to this post from a few days ago. The site now looks considerably less amazing: That&#8217;s a shame. I hope he has the data from the site and will be able to get up back up onto a new server soon. EDIT: Next day, and the site is online once again, with this [...]]]></description>
			<content:encoded><![CDATA[<p>An update to <a href="http://www.durf.org/2011/01/19/chinese-characters-through-time/">this post from a few days ago</a>. The site now looks considerably less amazing:</p>
<div id="attachment_655" class="wp-caption aligncenter" style="width: 368px"><a href="http://www.durf.org/wp-content/uploads/2011/01/sitehacked.png"><img src="http://www.durf.org/wp-content/uploads/2011/01/sitehacked.png" alt="The site right now" title="sitehacked" width="358" height="139" class="size-full wp-image-655" /></a><p class="wp-caption-text">An unfortunate update</p></div>
<p>That&#8217;s a shame. I hope he has the data from the site and will be able to get up back up onto a new server soon.</p>
<p>EDIT: Next day, and the site is online once again, with this message at the top: &#8220;My web site was hacked, by a bad guy, but 汉字叔叔 is back.&#8221; Nice to see.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2011/01/25/the-death-of-etymology/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chinese characters through time</title>
		<link>http://www.durf.org/2011/01/19/chinese-characters-through-time/</link>
		<comments>http://www.durf.org/2011/01/19/chinese-characters-through-time/#comments</comments>
		<pubDate>Wed, 19 Jan 2011 07:15:17 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[Asia]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=643</guid>
		<description><![CDATA[This Chinese Etymology website looks pretty amazing. Input a single hanzi (kanji input with a Japanese IME work just fine) and the site gives you lists of older variants—the versions of the characters used in seals, old oracle carvings, on and on. Click the image to see what it gives you when you search for [...]]]></description>
			<content:encoded><![CDATA[<p>This <a href="http://www.chineseetymology.org/">Chinese Etymology website</a> looks pretty amazing. Input a single <i>hanzi</i> (<i>kanji</i> input with a Japanese IME work just fine) and the site gives you lists of older variants—the versions of the characters used in seals, old oracle carvings, on and on. Click the image to see what it gives you when you search for 熊 (&#8220;bear&#8221;):</p>
<div id="attachment_644" class="wp-caption aligncenter" style="width: 310px"><a href="http://www.durf.org/wp-content/uploads/2011/01/hanzi_forms.png"><img src="http://www.durf.org/wp-content/uploads/2011/01/hanzi_forms-300x261.png" alt="Old bears" title="hanzi_forms" width="300" height="261" class="size-medium wp-image-644" /></a><p class="wp-caption-text">Old bears</p></div>
<p>(Via <a href="http://languagelog.ldc.upenn.edu/nll/?p=2910">Language Log</a>, in an informative piece that&#8217;s also worth a read.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2011/01/19/chinese-characters-through-time/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Letting writers hit rewind, play</title>
		<link>http://www.durf.org/2010/12/22/letting-writers-hit-rewind-play/</link>
		<comments>http://www.durf.org/2010/12/22/letting-writers-hit-rewind-play/#comments</comments>
		<pubDate>Wed, 22 Dec 2010 10:25:29 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[language]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=637</guid>
		<description><![CDATA[Here&#8217;s an interesting piece from James Somers in The Atlantic. He talks about the discovery of numerous versions of T. S. Eliot&#8217;s &#8220;The Waste Land&#8221; and goes on to discuss some software that lets you go back and review every stage of the process of creating a piece of writing. But why hasn&#8217;t this sort [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.theatlantic.com/technology/archive/2010/12/the-simple-software-that-could-but-probably-wont-change-the-face-of-writing/68364/">Here&#8217;s an interesting piece</a> from James Somers in <i>The Atlantic</i>. He talks about the discovery of numerous versions of T. S. Eliot&#8217;s &#8220;The Waste Land&#8221; and goes on to discuss some software that lets you go back and review every stage of the process of creating a piece of writing. But why hasn&#8217;t this sort of solution caught on?</p>
<blockquote><p>We must not want to write using a tool that tracks our every move. Because when people want something, and the tech to make it happen is readily available, it tends to happen.</p>
<p>I have a few theories, but they all start with the fact that writing is fundamentally about the final draft. It&#8217;s not like writing code, say, where recording one&#8217;s every change is standard practice. (Ask any coder worth her salt whether she uses a &#8220;version control system.&#8221; If she says &#8220;no,&#8221; well, she&#8217;s not worth her salt.)</p>
<p>That&#8217;s because code is so fragile, and simple changes can propagate in complex and unpredictable ways. So it would be stupid not to keep old versions &#8212; i.e., versions that worked &#8212; close at hand.</p>
<p>Writing is different. A writer explores, and as he explores, he purposely forgets the way he came.</p>
<p>I&#8217;m reminded of how the word &#8220;essay&#8221; derives from the French &#8220;essayer,&#8221; a verb meaning &#8220;to try.&#8221;</p>
</blockquote>
<p>The piece is worth reading on its own, but then you get to the link at the end and you go to <a href="http://ietherpad.com/ep/pad/view/somers-atlantic/latest">this page</a>, where you can hit the &#8220;play&#8221; button at top right and watch every keystroke that went into its writing. It&#8217;s fascinating stuff because EtherPad appears to be an interesting tool, but more importantly because it shows you how this particular writer crafts the skeleton of his essay and populates it with links to his references and then goes back and fleshes it all out. (And then gets it published in <i>The Atlantic</i>.)</p>
<p>I&#8217;d like to use this for a short translation at some point. I don&#8217;t think it would end up being as illuminating to watch the playback, since translators can start at the beginning and slog steadily to the end more readily than an essayist can, but if you could paste in the source text as step one and overwrite it as you go through the translation phases of the job that might be something worth showing others.</p>
<p>(Via <a href="http://twitter.com/#!/craigmod/status/17478356727500800">@craigmod</a>.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/12/22/letting-writers-hit-rewind-play/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The surgical mask in the universe</title>
		<link>http://www.durf.org/2010/12/21/the-surgical-mask-in-the-universe/</link>
		<comments>http://www.durf.org/2010/12/21/the-surgical-mask-in-the-universe/#comments</comments>
		<pubDate>Tue, 21 Dec 2010 02:32:05 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[fun]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=634</guid>
		<description><![CDATA[A helpful graphic to explain why all those masks people wear on the train won&#8217;t keep them safe from all the airborne diseases in that Chūō Line car: Screen capture taken from this cool Flash exploration of the sizes of things in the universe.]]></description>
			<content:encoded><![CDATA[<p>A helpful graphic to explain why all those masks people wear on the train won&#8217;t keep them safe from all the airborne diseases in that Chūō Line car:</p>
<div id="attachment_635" class="wp-caption aligncenter" style="width: 371px"><a href="http://www.durf.org/wp-content/uploads/2010/12/universe-sizes.png"><img src="http://www.durf.org/wp-content/uploads/2010/12/universe-sizes.png" alt="Virus goes in!" title="universe-sizes" width="361" height="197" class="size-full wp-image-635" /></a><p class="wp-caption-text">Virus goes in!</p></div>
<p>Screen capture taken from <a href="http://primaxstudio.com/stuff/scale_of_universe/">this cool Flash exploration</a> of the sizes of things in the universe. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/12/21/the-surgical-mask-in-the-universe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twitter plugin</title>
		<link>http://www.durf.org/2010/11/15/twitter-plugin/</link>
		<comments>http://www.durf.org/2010/11/15/twitter-plugin/#comments</comments>
		<pubDate>Mon, 15 Nov 2010 03:36:41 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=619</guid>
		<description><![CDATA[Yesterday this post alerted me to a plugin that looks like it might be useful if you run a WordPress blog and post tweets to it from time to time. Testing a new Twitter plugin for WordPress: http://is.gd/h62Uw 2010/11/15 12:37 via Tweetie for MacReplyRetweetFavorite @Durf Peter Durfee The Twitter Blackbird Pie plugin lets you produce [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday <a href="http://en.blog.wordpress.com/2010/11/05/bring-tweets-to-your-content/">this post</a> alerted me to a plugin that looks like it might be useful if you run a WordPress blog and post tweets to it from time to time. </p>
<p><!-- tweet id : 4015050876526592 --><br />
<style type='text/css'>#bbpBox_4015050876526592 a { text-decoration:none; color:#8A3314; }#bbpBox_4015050876526592 a:hover { text-decoration:underline; }</style>
<div id='bbpBox_4015050876526592' class='bbpBox' style='padding:20px; margin:5px 0; background-color:#9ae4e8; background-image:url(http://a2.twimg.com/profile_background_images/613562/pattern01.gif);'>
<div style='background:#fff; padding:10px; margin:0; min-height:48px; color:#695953; -moz-border-radius:5px; -webkit-border-radius:5px;'><span style='width:100%; font-size:18px; line-height:22px;'>Testing a new Twitter plugin for WordPress: <a href="http://is.gd/h62Uw">http://is.gd/h62Uw</a></span>
<div class='bbp-actions' style='font-size:12px; width:100%; padding:5px 0; margin:0 0 10px 0; border-bottom:1px solid #e6e6e6;'><img align='middle' src='http://www.durf.org/wp-content/plugins/twitter-blackbird-pie//images/bird.png' /><a title='tweeted on 2010/11/15 12:37' href='http://twitter.com/#!/Durf/status/4015050876526592' target='_blank'>2010/11/15 12:37</a> via <a href="http://twitter.com" rel="nofollow" target="blank">Tweetie for Mac</a><a href='https://twitter.com/intent/tweet?in_reply_to=4015050876526592' class='bbp-action bbp-reply-action' title='Reply'><span><em style='margin-left: 1em;'></em><strong>Reply</strong></span></a><a href='https://twitter.com/intent/retweet?tweet_id=4015050876526592' class='bbp-action bbp-retweet-action' title='Retweet'><span><em style='margin-left: 1em;'></em><strong>Retweet</strong></span></a><a href='https://twitter.com/intent/favorite?tweet_id=4015050876526592' class='bbp-action bbp-favorite-action' title='Favorite'><span><em style='margin-left: 1em;'></em><strong>Favorite</strong></span></a></div>
<div style='float:left; padding:0; margin:0'><a href='http://twitter.com/intent/user?screen_name=Durf'><img style='width:48px; height:48px; padding-right:7px; border:none; background:none; margin:0' src='http://a0.twimg.com/profile_images/1261501181/images_normal.jpeg' /></a></div>
<div style='float:left; padding:0; margin:0'><a style='font-weight:bold' href='http://twitter.com/intent/user?screen_name=Durf'>@Durf</a>
<div style='margin:0; padding-top:2px'>Peter Durfee</div>
</div>
<div style='clear:both'></div>
</div>
</div>
<p><!-- end of tweet --></p>
<p>The <a href="http://wordpress.org/extend/plugins/twitter-blackbird-pie/">Twitter Blackbird Pie</a> plugin lets you produce all that stuff up there ↑ by dropping in the tweet&#8217;s URL on a line of its own. Handy. (Assuming it works . . . &#8220;There may be a short delay,&#8221; as it says on the first page I linked. If this doesn&#8217;t start looking right soon I&#8217;ll edit this post into a rant.)</p>
<p>EDIT: Looks like you have better luck dropping in the old-style URL for your tweet, which doesn&#8217;t include the <code>#!/</code> bit before your user name.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/11/15/twitter-plugin/feed/</wfw:commentRss>
		<slash:comments>2</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>Sorry for the link spam</title>
		<link>http://www.durf.org/2010/04/06/sorry-for-the-link-spam/</link>
		<comments>http://www.durf.org/2010/04/06/sorry-for-the-link-spam/#comments</comments>
		<pubDate>Tue, 06 Apr 2010 08:04:41 +0000</pubDate>
		<dc:creator>Durf</dc:creator>
				<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.durf.org/?p=499</guid>
		<description><![CDATA[My WordPress installation has been allowing some spammer to inject links into the header.php code. I think I&#8217;ve zapped them and made the proper permissions changes to the files in question to prevent it from happening again, but if you see any link insanity please contact me to let me know! Mmmm, links. Oddly enough [...]]]></description>
			<content:encoded><![CDATA[<p>My WordPress installation has been allowing some spammer to inject links into the header.php code. I think I&#8217;ve zapped them and made the proper permissions changes to the files in question to prevent it from happening again, but if you see any link insanity please <a href="mailto:durfee@gmail.com">contact me</a> to let me know!</p>
<p><img src="http://www.durf.org/wp-content/uploads/2010/04/imageslinks.jpg" alt="links.jpg" border="0" width="385" height="300" /></p>
<p>Mmmm, links. Oddly enough these things don&#8217;t show up at all for me when I view the site with Safari 4.0.x. For those of you who&#8217;ve spotted the things, what were you using to do so? (Are they designed to stay invisible to a person logged in as an administrator, I wonder?)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.durf.org/2010/04/06/sorry-for-the-link-spam/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>
	</channel>
</rss>

