<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>Japanese-to-English Prestidigitator</title>
        <link>http://mediaefx.net/blog/nathan/</link>
        <description>(login)</description>
        <language>ja</language>
        <copyright>Copyright 2009</copyright>
        <lastBuildDate>Fri, 09 Jan 2009 16:43:24 +0900</lastBuildDate>
        <generator>http://www.sixapart.com/movabletype/</generator>
        <docs>http://www.rssboard.org/rss-specification</docs>
        
        <item>
            <title>Clarity is vital</title>
            <description>A clear, easy-to-understand translation can contribute greatly to a product&apos;s success. Suppose a product has a new interface that improves productivity but that is difficult to get used to at first. A customer who reads a poorly written, difficult-to-understand description of the interface will have a poor impression of the product itself. But a customer who reads a clear description that explains the benefits of the interface and how to take advantage of them will be excited about the product and have a positive impression of it. </description>
            <link>http://mediaefx.net/blog/nathan/2009/01/clear-eas.html</link>
            <guid>http://mediaefx.net/blog/nathan/2009/01/clear-eas.html</guid>
            
            
            <pubDate>Fri, 09 Jan 2009 16:43:24 +0900</pubDate>
        </item>
        
        <item>
            <title>The virtue of doubt</title>
            <description><![CDATA[Doubt isn't often listed as a virtue, but I think that it's something that all translators need. Because nobody is perfect, it's important to ask yourself: "is this the right word in the right phrase in the right sentence?" Of course, if a translator plans well and has a full understanding of the document that they're working on, the answer to that question should almost always be yes. Still, I think that the doubt one needs to notice a mistake and the patience one needs to figure out how to correct it are indispensable for good translation.<br /> ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/09/the-virtue-of-doubt.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/09/the-virtue-of-doubt.html</guid>
            
            
            <pubDate>Mon, 29 Sep 2008 14:23:31 +0900</pubDate>
        </item>
        
        <item>
            <title>Function before form</title>
            <description><![CDATA[Ever since my first part-time job, and maybe even before that, I've believed that the dress code that a company imposes upon its workers should be as sensible as possible, and that in most cases, sensible means comfortable.&nbsp; Fortunately, my current company has a very flexible dress code.&nbsp; This allows me to focus on getting work done without being bothered by hot and stifling clothing.<br /><br />In general, the company that I work at now prioritizes comfort at the office.&nbsp; I believe that this is a very good thing because comfort improves productivity.<br /> ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/07/function-before-form.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/07/function-before-form.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">dress code</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">productivity</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">work</category>
            
            <pubDate>Tue, 29 Jul 2008 17:05:11 +0900</pubDate>
        </item>
        
        <item>
            <title>Adventures in desk work</title>
            <description><![CDATA[I tried changing the position of my monitors today to make work more comfortable.&nbsp; They used to be lower on my desk, but I decided to raise them up so that they're easier to look at when I'm sitting straight. I think that I have decent posture, but because I've had my monitors placed close to the desk up until today, I had a tendency to slouch down when I wanted to look at something more closely.&nbsp; So far the new setup is working pretty well. It may not usher in a new era of productivity, but it should at least make me a little more comfortable. ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/07/adventures-in-desk-work-1.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/07/adventures-in-desk-work-1.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">comfort</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">desk work</category>
            
            <pubDate>Thu, 10 Jul 2008 14:24:32 +0900</pubDate>
        </item>
        
        <item>
            <title>MediaEFX lingo</title>
            <description><![CDATA[When I discuss how something should be written with my boss, we refer to "the Overlords" and "the other Overlords" quite often.&nbsp; Of course, as translators we draw upon a variety of resources to figure out what the best English expression for a particular Japanese term is, but there are two sources that we probably use more frequently than any others.&nbsp; "The Overlords," refers to Microsoft.&nbsp; If Microsoft prefers a certain way of writing something, that's usually what we stick with.&nbsp; But sometimes "the other Overlords" (Google) will reveal that Microsoft's preferred way of writing something is not in fact the norm, in which case we have to discuss which of these two mighty forces to side with.&nbsp; Oddly, we also reference the Chicago Manual of Style quite often, but it doesn't get any kind of fancy name.&nbsp; Since my boss is from Chicago, maybe he feels that saying "according to Chicago" is a powerful enough statement in and of itself. &nbsp; ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/06/mediaefx-lingo.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/06/mediaefx-lingo.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">references</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">style guides</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">writing</category>
            
            <pubDate>Mon, 16 Jun 2008 09:43:57 +0900</pubDate>
        </item>
        
        <item>
            <title>The awesome power of Japanese</title>
            <description><![CDATA[I remember that even in college, my Japanese studies used to influence the way that I wrote English, sometime for the worse.&nbsp; Now that I'm a translator the danger of this happening is even greater.&nbsp; I stumbled across a good example of this recently.&nbsp; The verb "exists" is used sparingly in most English writing, but Japanese uses verbs that mean "to exist" much more frequently.&nbsp; If I'm not careful I can find myself using it more often than I should.<br /><br />Here's an example of what I'm talking about:<br /><br />"When a signal disturbance exists..."<br />versus<br />"When there is a signal disturbance... "<br /> ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/06/the-awesome-power-of-japanese.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/06/the-awesome-power-of-japanese.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">Japanese</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">translation</category>
            
            <pubDate>Fri, 06 Jun 2008 16:03:09 +0900</pubDate>
        </item>
        
        <item>
            <title>Caffeine efficiency</title>
            <description><![CDATA[I read an article recently that said that tea is supposed to be better for boosting brain performance than coffee, because it gives you a more steady supply of caffeine than coffee, which provides more of a jolt.<br /><br />Since big translation jobs tend to require sustained concentration, I suppose that tea is the way to go.&nbsp; But coffee is very delicious.&nbsp; Maybe if I just sip it...<br /> ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/06/caffeine-efficiency.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/06/caffeine-efficiency.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">caffeine</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">concentration</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">translation</category>
            
            <pubDate>Tue, 03 Jun 2008 12:40:59 +0900</pubDate>
        </item>
        
        <item>
            <title>Scientific vacationing</title>
            <description><![CDATA[I was thinking about how my Golden-Week-centered vacation happened to coincide nicely with a lull and then a subsequent surge of work when it occurred to me that it would probably be a good idea to look at the company work schedules of the past and see if there is enough consistency in workload fluctuations to create some kind of seasonal busyness chart.&nbsp; Such a chart would probably be a very handy vacation planning tool. ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/05/the-science-of-taking-time-off.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/05/the-science-of-taking-time-off.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">vacations</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">work management</category>
            
            <pubDate>Wed, 14 May 2008 18:12:59 +0900</pubDate>
        </item>
        
        <item>
            <title>The challenges of technical translation</title>
            <description><![CDATA[I used to assume that translating a technical document such as a user's manual for an oscilloscope would always be easier than translating a well-written novel.&nbsp; The reason for this is that while every word in a literary masterpiece may be packed with meaning and nuance, an instruction manual tends to be more straightforward.<br /><br />But after further thought and experience, I've concluded that one of the special challenges of technical writing is that the translator must always be clear.&nbsp; When a master novelist writes an unclear sentence, we can assume that he intends for the sentence to be unclear, thus the job of the translator is to write a similarly ambiguous sentence, but when an engineer writes an unclear sentence in an instruction manual, we can usually just assume that he had a hard time expressing the concept that he was trying to convey, and then it's up to the translator to figure out what the engineer was really trying to say.<br /><br />This can be a trying process.&nbsp; I've pointed out countless mistakes to clients in my less than one year working as a full-time translator.&nbsp; This helps the client to know that you understand the material, and it is probably good for business in the long run, but it also takes up a good deal of time.&nbsp; Recognizing that a sentence is unclear usually only takes an instant, but then I have to explain to the client why the sentence is unclear and ask them how they would like to clarify it.&nbsp; This is time I could be spending translating something else and making more money. I'm hoping though that in the long run, the time I invest into this process of improving upon the clarity of the original document will not only be good for business, but will also make my own writing lucid enough to make even most novelists jealous.<br /> ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/05/the-challenges-of-technical-tr.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/05/the-challenges-of-technical-tr.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">technical translation</category>
            
            <pubDate>Tue, 13 May 2008 18:10:16 +0900</pubDate>
        </item>
        
        <item>
            <title>What this blog is about, and how to avoid going blind</title>
            <description><![CDATA[In this blog I am going to discuss aspects of my job as a Japanese to English technical translator.&nbsp; I've been working for about a year now as a translator, but I used to do translation occassionally for my previous job as well.<br /><br />Once I started translating full time I noticed that my eyes were getting very tired at the end of each day.&nbsp; It wasn't that I wasn't used to reading in Japanese, as I'd been reading novels rather frequently for many years, but rather that translation is just harder on the eyes than ordinary reading.&nbsp; For most of the day my eyes have to dart back and forth between my two computer screens as I search for the best possible way to express some Japanese term or concept in English.&nbsp; At first this was a daily problem, and I was worried about possible long-term effects, but now my eyes are fine even at the end of a very long day.&nbsp; One reason is simply that my eyes have become stronger, but I also owe much of my newfound comfort to these simple steps that I took to take some of the burden off of my eyes:<br /><br />1. Make text bigger. I regularly set the text size in word processors and PDFs high enough so that the text I want to read just barely fits into the screen, or sometimes even larger than that.&nbsp; Bigger text = happier eyes.<br /><br />2. Close your eyes when thinking.&nbsp; When I used to stumble across a difficult to translate passage, I would keep reading it until I thought of a good translation.&nbsp; Now I read a passage until I understand it, then I close my eyes so that they don't keep wandering over the passage as I'm thinking about how to best render it in English.<br /><br />3. Use search features as much as possible.&nbsp; Skimming through a document to find a particular word or passage puts lots of strain on your eyes.&nbsp; It's always better to just let the computer do the searching for you.&nbsp; You can also save time by remembering search keyboard shortcuts and making new shortcuts of your own.<br /><br />4. Excercise.&nbsp; I find that getting up and moving around for even just a few minutes works wonders for my eyes.&nbsp; I suppose that the increased circulation helps to reduce muscle fatigue.  <br /> ]]></description>
            <link>http://mediaefx.net/blog/nathan/2008/05/what-this-blog-is-about-and-ho.html</link>
            <guid>http://mediaefx.net/blog/nathan/2008/05/what-this-blog-is-about-and-ho.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">English</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">Japanese</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">eye fatigue</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">translation</category>
            
            <pubDate>Mon, 12 May 2008 14:06:01 +0900</pubDate>
        </item>
        
    </channel>
</rss>
