<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Liner Notes for &#8220;County Doctor&#8221;</title>
	<atom:link href="http://www.motleyvision.org/2009/liner-notes-for-county-doctor/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.motleyvision.org/2009/liner-notes-for-county-doctor/</link>
	<description>Mormon Arts and Culture</description>
	<lastBuildDate>Thu, 09 Feb 2012 15:46:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kent Larsen</title>
		<link>http://www.motleyvision.org/2009/liner-notes-for-county-doctor/comment-page-1/#comment-38240</link>
		<dc:creator>Kent Larsen</dc:creator>
		<pubDate>Tue, 13 Oct 2009 21:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.motleyvision.org/?p=2978#comment-38240</guid>
		<description>Great post, William. I&#039;m fascinated by the process you used, and I found parts of it very familiar--I also do much of my translation during my commute, which takes much longer, but both allows me to use time that might be otherwise wasted, and gives a break between translating sessions, which forces me to take a different or fresh look at what I&#039;ve done frequently in the process.

There are a few differences, however:

* I use google translate for a rough first draft. In recent months google translate has become quite good, leaving only higher-level issues (word choice, sentence structure, etc.), since most of the more basic grammar is correct. I can see, however, that for literary translations like yours that might not be the best idea. It also doesn&#039;t work very well when the source document uses archaic or obscure or precise language.

* I like putting the translation and the original side-by-side on the same sheet of paper, ideally with the google first draft translation double-spaced or triple-spaced.

* Once the translation has been corrected to the point that I like it, I then ditch the source and work only with the translation, running it through spell and grammar checkers in addition to my own reading for tone, word choice, etc.

I don&#039;t know if you are planning any future translations (it would help your German, you know), but if you are, or if anyone else is planning on taking a stab at it, my experience might be helpful.

AND, William, there really isn&#039;t any excuse of a lack of resources for keeping up your language skills (lack of time, yes, lack of resources, no). With the Internet, podcasts, online newspapers, etc., it is really possible to maintain a language very easily.</description>
		<content:encoded><![CDATA[<p>Great post, William. I&#8217;m fascinated by the process you used, and I found parts of it very familiar&#8211;I also do much of my translation during my commute, which takes much longer, but both allows me to use time that might be otherwise wasted, and gives a break between translating sessions, which forces me to take a different or fresh look at what I&#8217;ve done frequently in the process.</p>
<p>There are a few differences, however:</p>
<p>* I use google translate for a rough first draft. In recent months google translate has become quite good, leaving only higher-level issues (word choice, sentence structure, etc.), since most of the more basic grammar is correct. I can see, however, that for literary translations like yours that might not be the best idea. It also doesn&#8217;t work very well when the source document uses archaic or obscure or precise language.</p>
<p>* I like putting the translation and the original side-by-side on the same sheet of paper, ideally with the google first draft translation double-spaced or triple-spaced.</p>
<p>* Once the translation has been corrected to the point that I like it, I then ditch the source and work only with the translation, running it through spell and grammar checkers in addition to my own reading for tone, word choice, etc.</p>
<p>I don&#8217;t know if you are planning any future translations (it would help your German, you know), but if you are, or if anyone else is planning on taking a stab at it, my experience might be helpful.</p>
<p>AND, William, there really isn&#8217;t any excuse of a lack of resources for keeping up your language skills (lack of time, yes, lack of resources, no). With the Internet, podcasts, online newspapers, etc., it is really possible to maintain a language very easily.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

