<?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: Mounce on Translating</title>
	<atom:link href="http://boulders2bits.com/archives/2009/10/26/mounce-on-translating/feed/" rel="self" type="application/rss+xml" />
	<link>http://boulders2bits.com/archives/2009/10/26/mounce-on-translating/</link>
	<description>breaking things down to manageable size</description>
	<lastBuildDate>Thu, 29 Jul 2010 18:16:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Kirk Lowery</title>
		<link>http://boulders2bits.com/archives/2009/10/26/mounce-on-translating/comment-page-1/#comment-22965</link>
		<dc:creator>Kirk Lowery</dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://boulders2bits.com/?p=2197#comment-22965</guid>
		<description>I&#039;ve not followed the ins and outs of translation theory for a few years, so this comment may be tangential to the main conversation:

I was one of the translators for the Holman Christian Standard version (1 Kings). I of course ran across many of these same problems. (Translating the building of the Temple was a nightmare!) One of the frustrations was the business of one-to-one correspondence at every level: lexical, morphological and syntactic.

I&#039;ve always wondered why translations don&#039;t take more advantage of margin- and footnotes. If the goal is translating the message correctly, even a very literal translation is going to be a distance from the original. Often, I could not find a one-to-one correspondence. Sometimes English simply had no equivalent that was not very paraphrastic. It wasn&#039;t that the Hebrew was always unclear or ambiguous. To the contrary. But for English, one had to &quot;unscramble&quot; the words.

So why not choose the &quot;best&quot; English equivalent even if it is grammatically distant? And then use notes to explain the problem or issue to the reader. The major translations do this rarely, at least, to my satisfaction.

In this one respect, the most advanced English translation today I know of is the Net Bible.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve not followed the ins and outs of translation theory for a few years, so this comment may be tangential to the main conversation:</p>
<p>I was one of the translators for the Holman Christian Standard version (1 Kings). I of course ran across many of these same problems. (Translating the building of the Temple was a nightmare!) One of the frustrations was the business of one-to-one correspondence at every level: lexical, morphological and syntactic.</p>
<p>I&#8217;ve always wondered why translations don&#8217;t take more advantage of margin- and footnotes. If the goal is translating the message correctly, even a very literal translation is going to be a distance from the original. Often, I could not find a one-to-one correspondence. Sometimes English simply had no equivalent that was not very paraphrastic. It wasn&#8217;t that the Hebrew was always unclear or ambiguous. To the contrary. But for English, one had to &#8220;unscramble&#8221; the words.</p>
<p>So why not choose the &#8220;best&#8221; English equivalent even if it is grammatically distant? And then use notes to explain the problem or issue to the reader. The major translations do this rarely, at least, to my satisfaction.</p>
<p>In this one respect, the most advanced English translation today I know of is the Net Bible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karyn</title>
		<link>http://boulders2bits.com/archives/2009/10/26/mounce-on-translating/comment-page-1/#comment-22951</link>
		<dc:creator>Karyn</dc:creator>
		<pubDate>Mon, 26 Oct 2009 22:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://boulders2bits.com/?p=2197#comment-22951</guid>
		<description>UPDATE: 
Looks like some others have pointed out this post by Mounce too. 

John Hobbins takes the list and smooths it out a little to make it more broadly applicable &lt;a href=&quot;http://ancienthebrewpoetry.typepad.com/ancient_hebrew_poetry/2009/10/bill-mounce-on-the-translation-goals-of-esv.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.

John mentions that he heard about the post from Jim Getz, &lt;a href=&quot;http://jimgetz.org/2009/10/26/all-translation-is-supple/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.

(I had seen it on the Koinonia blog earlier this morning in my Google Reader... we must have all been on the same brain wave!)</description>
		<content:encoded><![CDATA[<p>UPDATE:<br />
Looks like some others have pointed out this post by Mounce too. </p>
<p>John Hobbins takes the list and smooths it out a little to make it more broadly applicable <a href="http://ancienthebrewpoetry.typepad.com/ancient_hebrew_poetry/2009/10/bill-mounce-on-the-translation-goals-of-esv.html" rel="nofollow">here</a>.</p>
<p>John mentions that he heard about the post from Jim Getz, <a href="http://jimgetz.org/2009/10/26/all-translation-is-supple/" rel="nofollow">here</a>.</p>
<p>(I had seen it on the Koinonia blog earlier this morning in my Google Reader&#8230; we must have all been on the same brain wave!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karyn</title>
		<link>http://boulders2bits.com/archives/2009/10/26/mounce-on-translating/comment-page-1/#comment-22942</link>
		<dc:creator>Karyn</dc:creator>
		<pubDate>Mon, 26 Oct 2009 17:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://boulders2bits.com/?p=2197#comment-22942</guid>
		<description>Hi Bob,

Thanks for sharing your thoughts. I agree with you that &lt;a href=&quot;http://ancienthebrewpoetry.typepad.com/ancient_hebrew_poetry/2009/10/the-traditional-goal-of-textual-interpretation.html&quot; rel=&quot;nofollow&quot;&gt;John Hobbins&#039; post&lt;/a&gt; today is very helpful (and one readers should definitely take the time to investigate).</description>
		<content:encoded><![CDATA[<p>Hi Bob,</p>
<p>Thanks for sharing your thoughts. I agree with you that <a href="http://ancienthebrewpoetry.typepad.com/ancient_hebrew_poetry/2009/10/the-traditional-goal-of-textual-interpretation.html" rel="nofollow">John Hobbins&#8217; post</a> today is very helpful (and one readers should definitely take the time to investigate).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob MacDonald</title>
		<link>http://boulders2bits.com/archives/2009/10/26/mounce-on-translating/comment-page-1/#comment-22941</link>
		<dc:creator>Bob MacDonald</dc:creator>
		<pubDate>Mon, 26 Oct 2009 17:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://boulders2bits.com/?p=2197#comment-22941</guid>
		<description>1. concordance - to start with an eirenic comment - yes. But the reason for concordance is in the sound not necessarily in the meaning. When the whole gospel can be reduced to one word: hear, then the sound is important. It is not the train of thought. The training will happen when the hearer has to do some work. What is a &#039;train of thought&#039;? Translate that one into Greek for Paul while composing Romans. &quot;Paul, dear, we simply cannot follow your 55 step argument. Ten is simply too many sections. God forbid we should be dependent on your intellect for salvation! If you will, there are just too many animals in your (camel) train.&quot;
2. one for one - surely this one should be number 1. But there is no way that this can be done with conjugated verbs. It is even funnier when you think of enclitic languages like Hebrew. The DNA of English is all unrolled.
3. Less is definitely more. Mounce&#039;s post on Are ants people is a good example. Of course ants are a people. Even Google translate knows that: les fourmis sont un peuple.
4. Euphony - much more than euphony is required. Dramatic reenactment. Similar sounds. Wordplay. 
5. &#039;must make some sense&#039; is a non-starter. Make sense is too much an abstraction. The pornographers get it quicker than the pious. And at least in the Hebrew Bible, there are plenty of places where the transmitted copy seems to be fully enigmatic to all of us. (I have not tried much translation from Greek - too modern for me).
6. open to misunderstanding. Is it implied that we have already understood or could understand? It must be open to misunderstanding so that our God has something to correct in us as we draw out the words from our texts.

7. Dig. We must dig and reconstruct through language and history what we can around the text that we have. I think John&#039;s argument for reconstruction &lt;a href=&quot;http://ancienthebrewpoetry.typepad.com/ancient_hebrew_poetry/2009/10/the-traditional-goal-of-textual-interpretation.html&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; is a post today is a sound one.</description>
		<content:encoded><![CDATA[<p>1. concordance &#8211; to start with an eirenic comment &#8211; yes. But the reason for concordance is in the sound not necessarily in the meaning. When the whole gospel can be reduced to one word: hear, then the sound is important. It is not the train of thought. The training will happen when the hearer has to do some work. What is a &#8216;train of thought&#8217;? Translate that one into Greek for Paul while composing Romans. &#8220;Paul, dear, we simply cannot follow your 55 step argument. Ten is simply too many sections. God forbid we should be dependent on your intellect for salvation! If you will, there are just too many animals in your (camel) train.&#8221;<br />
2. one for one &#8211; surely this one should be number 1. But there is no way that this can be done with conjugated verbs. It is even funnier when you think of enclitic languages like Hebrew. The DNA of English is all unrolled.<br />
3. Less is definitely more. Mounce&#8217;s post on Are ants people is a good example. Of course ants are a people. Even Google translate knows that: les fourmis sont un peuple.<br />
4. Euphony &#8211; much more than euphony is required. Dramatic reenactment. Similar sounds. Wordplay.<br />
5. &#8216;must make some sense&#8217; is a non-starter. Make sense is too much an abstraction. The pornographers get it quicker than the pious. And at least in the Hebrew Bible, there are plenty of places where the transmitted copy seems to be fully enigmatic to all of us. (I have not tried much translation from Greek &#8211; too modern for me).<br />
6. open to misunderstanding. Is it implied that we have already understood or could understand? It must be open to misunderstanding so that our God has something to correct in us as we draw out the words from our texts.</p>
<p>7. Dig. We must dig and reconstruct through language and history what we can around the text that we have. I think John&#8217;s argument for reconstruction <a href="http://ancienthebrewpoetry.typepad.com/ancient_hebrew_poetry/2009/10/the-traditional-goal-of-textual-interpretation.html" rel="nofollow">here</a> is a post today is a sound one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
