<?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"
	>
<channel>
	<title>Comments on: Even More on the ESV</title>
	<atom:link href="http://bluecord.org/biblioblog/2007/05/even-more-on-the-esv/feed/" rel="self" type="application/rss+xml" />
	<link>http://bluecord.org/biblioblog/2007/05/even-more-on-the-esv/</link>
	<description>A biblioblog</description>
	<pubDate>Wed, 07 Jan 2009 09:57:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: TNIV Truth</title>
		<link>http://bluecord.org/biblioblog/2007/05/even-more-on-the-esv/#comment-17496</link>
		<dc:creator>TNIV Truth</dc:creator>
		<pubDate>Tue, 08 May 2007 16:38:44 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/05/even-more-on-the-esv/#comment-17496</guid>
		<description>&lt;strong&gt; Is the TNIV a Dynamic Equivalent translation?...&lt;/strong&gt;

(UPDATE, May 8: Today Kevin has blogged another irenic post, Even More on the ESV, in response to my comments. Stay tuned. There may be more to come. Isn't it great that we can discuss these matters without any anger, put-downs, or name-calling! How s...</description>
		<content:encoded><![CDATA[<p><strong> Is the <acronym title="Today's New International Version">TNIV</acronym> a Dynamic Equivalent translation?&#8230;</strong></p>
<p>(UPDATE, May 8: Today Kevin has blogged another irenic post, Even More on the <acronym title="English Standard Version">ESV</acronym>, in response to my comments. Stay tuned. There may be more to come. Isn&#8217;t it great that we can discuss these matters without any anger, put-downs, or name-calling! How s&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne Leman</title>
		<link>http://bluecord.org/biblioblog/2007/05/even-more-on-the-esv/#comment-17495</link>
		<dc:creator>Wayne Leman</dc:creator>
		<pubDate>Tue, 08 May 2007 16:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://bluecord.org/biblioblog/2007/05/even-more-on-the-esv/#comment-17495</guid>
		<description>&lt;i&gt;Before ending this post, I should point out that Lehman was talking a good deal about TNIV, while I have hardly mentioned it.  I have never read TNIV and do not own a copy, so I donâ€™t feel free to comment on it.  When I have categorized it in my posts, I have done so based on what others have said about it&lt;/i&gt;

Kevin, in spite of claims by anti-TNIV crusaders that the TNIV has changed the NIV so significantly, the translation approach is the same in both. The TNIV is slightly more literal in a number of passages. Craig Blomberg has documented this.

You can still download the entire TNIV for free by &lt;a href="http://www.tniv.info/pdf/TNIV_Bible.pdf" rel="nofollow"&gt;clicking on this link&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p><i>Before ending this post, I should point out that Lehman was talking a good deal about <acronym title="Today's New International Version">TNIV</acronym>, while I have hardly mentioned it.  I have never read <acronym title="Today's New International Version">TNIV</acronym> and do not own a copy, so I donâ€™t feel free to comment on it.  When I have categorized it in my posts, I have done so based on what others have said about it</i></p>
<p>Kevin, in spite of claims by anti-<acronym title="Today's New International Version">TNIV</acronym> crusaders that the <acronym title="Today's New International Version">TNIV</acronym> has changed the <acronym title="New International Version">NIV</acronym> so significantly, the translation approach is the same in both. The <acronym title="Today's New International Version">TNIV</acronym> is slightly more literal in a number of passages. Craig Blomberg has documented this.</p>
<p>You can still download the entire <acronym title="Today's New International Version">TNIV</acronym> for free by <a href="http://www.tniv.info/pdf/TNIV_Bible.pdf" rel="nofollow">clicking on this link</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
