<?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: Style and tradition in translation</title>
	<atom:link href="http://heissufficient.com/2007/12/18/style-and-tradition-in-translation/feed/" rel="self" type="application/rss+xml" />
	<link>http://heissufficient.com/2007/12/18/style-and-tradition-in-translation/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=style-and-tradition-in-translation</link>
	<description>A personal walk in a wilderness of words</description>
	<lastBuildDate>Wed, 08 Feb 2012 04:32:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: ElShaddai Edwards</title>
		<link>http://heissufficient.com/2007/12/18/style-and-tradition-in-translation/#comment-539</link>
		<dc:creator>ElShaddai Edwards</dc:creator>
		<pubDate>Thu, 20 Dec 2007 18:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://heissufficient.net/2007/12/18/style-and-tradition-in-translation/#comment-539</guid>
		<description>Thanks for following up. I think we&#039;re on the same page -- I&#039;ve just always been a &quot;big picture&quot; guy and detail-level things like awkward grammar always prove to be a distraction to my process of comprehension. I like being able to read, for example, Paul or John&#039;s logic statements and think about the implications, rather than try to work out the logic twists itself. For me, the application of the logic is the &quot;result&quot;, not the logic itself.

So the &quot;elevated&quot; language of the Tyndale tradition that is deliberately archaic only creates another hurdle for me to understanding the meaning. I don&#039;t see that as requiring &quot;no thinking&quot;, just different thinking. And yes, it&#039;s good to have multiple translations for different language comprehension styles - we truly are blessed to have this store of riches available!</description>
		<content:encoded><![CDATA[<p>Thanks for following up. I think we&#8217;re on the same page &#8212; I&#8217;ve just always been a &#8220;big picture&#8221; guy and detail-level things like awkward grammar always prove to be a distraction to my process of comprehension. I like being able to read, for example, Paul or John&#8217;s logic statements and think about the implications, rather than try to work out the logic twists itself. For me, the application of the logic is the &#8220;result&#8221;, not the logic itself.</p>
<p>So the &#8220;elevated&#8221; language of the Tyndale tradition that is deliberately archaic only creates another hurdle for me to understanding the meaning. I don&#8217;t see that as requiring &#8220;no thinking&#8221;, just different thinking. And yes, it&#8217;s good to have multiple translations for different language comprehension styles &#8211; we truly are blessed to have this store of riches available!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geocreationist</title>
		<link>http://heissufficient.com/2007/12/18/style-and-tradition-in-translation/#comment-540</link>
		<dc:creator>Geocreationist</dc:creator>
		<pubDate>Thu, 20 Dec 2007 18:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://heissufficient.net/2007/12/18/style-and-tradition-in-translation/#comment-540</guid>
		<description>&lt;i&gt;but I’d prefer to wrestle with understanding the meaning rather than understanding the grammar.&lt;/i&gt;
I am wondering if you misunderstood me.  What I meant is that I ultimately understand the scripture&#039;s &lt;b&gt;meaning&lt;/b&gt; better because the presentation causes me to think about the text more.   I enjoy dwelling on each part of the author&#039;s thought, and pondering their choice of words; I internalize it better.  While it is true that the more modern translations require no thinking for me to understand them, it is because someone else has already done the pondering and is presenting me with the answer.  Sure, it decreases my reading time, but in doing so, I don&#039;t remember the scripture as well.  That&#039;s just how my brain works.  My wife&#039;s brain is like a steal trap; mine is not.

Perhaps I should have written about my pastor, who hates those older translations.  They don&#039;t speak to him... all the thy&#039;s and thous and shalts.  The NLT was the first translation that ever presented God&#039;s word to him in a manner that made sense the first time he read it, and obviously the HCSB does this for people to.  I applaud that.

So, I agree with you that understanding God&#039;s meaning is indeed the bottom line.

I was hoping to support your original point, that there is a purpose in having multiple translations, because different people are impacted differently.  But again, I agree that any impact is meaningless if the communication of God&#039;s message is not the final result.</description>
		<content:encoded><![CDATA[<p><i>but I’d prefer to wrestle with understanding the meaning rather than understanding the grammar.</i><br />
I am wondering if you misunderstood me.  What I meant is that I ultimately understand the scripture&#8217;s <b>meaning</b> better because the presentation causes me to think about the text more.   I enjoy dwelling on each part of the author&#8217;s thought, and pondering their choice of words; I internalize it better.  While it is true that the more modern translations require no thinking for me to understand them, it is because someone else has already done the pondering and is presenting me with the answer.  Sure, it decreases my reading time, but in doing so, I don&#8217;t remember the scripture as well.  That&#8217;s just how my brain works.  My wife&#8217;s brain is like a steal trap; mine is not.</p>
<p>Perhaps I should have written about my pastor, who hates those older translations.  They don&#8217;t speak to him&#8230; all the thy&#8217;s and thous and shalts.  The NLT was the first translation that ever presented God&#8217;s word to him in a manner that made sense the first time he read it, and obviously the HCSB does this for people to.  I applaud that.</p>
<p>So, I agree with you that understanding God&#8217;s meaning is indeed the bottom line.</p>
<p>I was hoping to support your original point, that there is a purpose in having multiple translations, because different people are impacted differently.  But again, I agree that any impact is meaningless if the communication of God&#8217;s message is not the final result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ElShaddai Edwards</title>
		<link>http://heissufficient.com/2007/12/18/style-and-tradition-in-translation/#comment-541</link>
		<dc:creator>ElShaddai Edwards</dc:creator>
		<pubDate>Thu, 20 Dec 2007 14:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://heissufficient.net/2007/12/18/style-and-tradition-in-translation/#comment-541</guid>
		<description>&lt;i&gt;Personally, I like the NKJV and the NIV for similar reasons: the grammar is imperfect and causes me to dig.&lt;/i&gt;

No pain, no gain?! I suppose there&#039;s something to be said for learning by wrestling with the text, but I&#039;d prefer to wrestle with understanding the meaning rather than understanding the grammar. That&#039;s been a significant factor in my attraction to translations like the HCSB and REB - modern English grammar.

&lt;i&gt;I hadn’t heard of the hcsb before finding it on your site, but I imagine I’d say the same of it&lt;/i&gt;

For more on the HCSB, be sure to check out &lt;a href=&quot;/2007/12/19/interview-with-dr-ed-blum-general-editor-for-the-hcsb/&quot; rel=&quot;nofollow&quot;&gt;the transcript&lt;/a&gt; of an interview with Dr. Ed Blum, General Editor of the HCSB.</description>
		<content:encoded><![CDATA[<p><i>Personally, I like the NKJV and the NIV for similar reasons: the grammar is imperfect and causes me to dig.</i></p>
<p>No pain, no gain?! I suppose there&#8217;s something to be said for learning by wrestling with the text, but I&#8217;d prefer to wrestle with understanding the meaning rather than understanding the grammar. That&#8217;s been a significant factor in my attraction to translations like the HCSB and REB &#8211; modern English grammar.</p>
<p><i>I hadn’t heard of the hcsb before finding it on your site, but I imagine I’d say the same of it</i></p>
<p>For more on the HCSB, be sure to check out <a  href="/2007/12/19/interview-with-dr-ed-blum-general-editor-for-the-hcsb/" rel="nofollow">the transcript</a> of an interview with Dr. Ed Blum, General Editor of the HCSB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geocreationist</title>
		<link>http://heissufficient.com/2007/12/18/style-and-tradition-in-translation/#comment-538</link>
		<dc:creator>Geocreationist</dc:creator>
		<pubDate>Wed, 19 Dec 2007 18:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://heissufficient.net/2007/12/18/style-and-tradition-in-translation/#comment-538</guid>
		<description>I agree that we should not get too caught up in finding an innerrant translation... there is no such thing in my opinion.

I find purpose in several translations.  Personally, I like the NKJV and the NIV for similar reasons: the grammar is imperfect and causes me to dig.  Furthermore, because each is an attempt at using accurate words, I can usually find the significant words in my Strong&#039;s concordance to get a better understanding of a given verse.  If I need yet more insight, I can always use the tools on blueletter.

NLT is good for me when I just want to read the scripture afresh without triggering my preconceived notions of what the scritpure means, and just let the LORD speak to me like He did Moses, &quot;as a man to another man.&quot;  Studying with the NLT is too difficult for me, but when I am reading for inspiration, devotional, or bottom line message, I really am not missing out on much.  (I hadn&#039;t heard of the hcsb before finding it on your site, but I imagine I&#039;d say the same of it).

In short, I like the 3-legged stool analogy.  I think it describes a constructive use of scripture and its various translations quite well.</description>
		<content:encoded><![CDATA[<p>I agree that we should not get too caught up in finding an innerrant translation&#8230; there is no such thing in my opinion.</p>
<p>I find purpose in several translations.  Personally, I like the NKJV and the NIV for similar reasons: the grammar is imperfect and causes me to dig.  Furthermore, because each is an attempt at using accurate words, I can usually find the significant words in my Strong&#8217;s concordance to get a better understanding of a given verse.  If I need yet more insight, I can always use the tools on blueletter.</p>
<p>NLT is good for me when I just want to read the scripture afresh without triggering my preconceived notions of what the scritpure means, and just let the LORD speak to me like He did Moses, &#8220;as a man to another man.&#8221;  Studying with the NLT is too difficult for me, but when I am reading for inspiration, devotional, or bottom line message, I really am not missing out on much.  (I hadn&#8217;t heard of the hcsb before finding it on your site, but I imagine I&#8217;d say the same of it).</p>
<p>In short, I like the 3-legged stool analogy.  I think it describes a constructive use of scripture and its various translations quite well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

