<?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 for Catacombs: The ISV Blog</title>
	<atom:link href="http://isv.org/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://isv.org/blog</link>
	<description>Holy Bible: International Standard Version Q&#38;A</description>
	<lastBuildDate>Fri, 04 May 2012 21:33:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Welcome to The Catacombs by William P. Welty, Ph.D.</title>
		<link>http://isv.org/blog/?p=1#comment-314</link>
		<dc:creator>William P. Welty, Ph.D.</dc:creator>
		<pubDate>Fri, 04 May 2012 21:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-314</guid>
		<description>The first citation is correct. The second citation (the PDF file) contains a content error. We will have Davidson Press correct the text to conform with the first citstion from our web site. To sum up, the MT was consulted, along with various ancient languages editions such as the Septuagint texts and the dead Sea Scrolls, for the entire text of the ISV Old Testament, except that in the case of the Book of Isaiah, Qumran Cave One (1QIsa) was used as the base text for translation, with the MT, LXX, and other DSS documents secondarily consulted.</description>
		<content:encoded><![CDATA[<p>The first citation is correct. The second citation (the PDF file) contains a content error. We will have Davidson Press correct the text to conform with the first citstion from our web site. To sum up, the MT was consulted, along with various ancient languages editions such as the Septuagint texts and the dead Sea Scrolls, for the entire text of the ISV Old Testament, except that in the case of the Book of Isaiah, Qumran Cave One (1QIsa) was used as the base text for translation, with the MT, LXX, and other DSS documents secondarily consulted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by Mike Allen</title>
		<link>http://isv.org/blog/?p=1#comment-313</link>
		<dc:creator>Mike Allen</dc:creator>
		<pubDate>Fri, 04 May 2012 21:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-313</guid>
		<description>There seems to be a conflict in the translation source used for the Tanakh on your website.  First, as given here, http://isv.org/principles.php, you state:

&quot;For the Tanakh, or Old Testament, the Masoretic text as published in the latest editions of Biblia Hebraica Stuttgartensia and Quinta is used as the base text, in consultation with other ancient Hebrew texts such as the Dead Sea Scrolls, the Samaritan Pentateuch, and a select number of ancient versions (the Septuagint, the Vulgate, the Syriac Peshitta, and the Targums). All significant departures from the base text, as well as all significant textual variants, are indicated in footnotes. With respect to the book of Isaiah, Qumran Cave 1&#039;s Great Isaiah Scroll (1QIsa) was used, along with certain other Dead Sea Scroll manuscripts, as the base text for translation, with the MT secondarily consulted for variants to 1QIsa.&quot;

But, on the .pdf version found here, http://isv.org/ISV_Features_and_Benefits.pdf, you say the following:

&quot;The ISV® respects the scholarship of the Dead Sea Scrolls. Unlike other modern English translations of the Bible, the ISV® does not use the traditional Masoretic Text of the Hebrew Scriptures as the base language original for rendering much of the English language translation of the ISV® Old Testament. Instead, the book of Isaiah was translated directly from the text of the Great Isaiah Scroll (1QIsa), which was found among the Qumran Cave 1 collection of manuscripts and dates from the mid-second century BC. In contrast, the Masoretic Text dates much later, from c. 950-1050 AD.&quot;

My question: Is the Masoretic Text the base for most of the translation or not?</description>
		<content:encoded><![CDATA[<p>There seems to be a conflict in the translation source used for the Tanakh on your website.  First, as given here, <a href="http://isv.org/principles.php" rel="nofollow">http://isv.org/principles.php</a>, you state:</p>
<p>&#8220;For the Tanakh, or Old Testament, the Masoretic text as published in the latest editions of Biblia Hebraica Stuttgartensia and Quinta is used as the base text, in consultation with other ancient Hebrew texts such as the Dead Sea Scrolls, the Samaritan Pentateuch, and a select number of ancient versions (the Septuagint, the Vulgate, the Syriac Peshitta, and the Targums). All significant departures from the base text, as well as all significant textual variants, are indicated in footnotes. With respect to the book of Isaiah, Qumran Cave 1&#8242;s Great Isaiah Scroll (1QIsa) was used, along with certain other Dead Sea Scroll manuscripts, as the base text for translation, with the MT secondarily consulted for variants to 1QIsa.&#8221;</p>
<p>But, on the .pdf version found here, <a href="http://isv.org/ISV_Features_and_Benefits.pdf" rel="nofollow">http://isv.org/ISV_Features_and_Benefits.pdf</a>, you say the following:</p>
<p>&#8220;The ISV® respects the scholarship of the Dead Sea Scrolls. Unlike other modern English translations of the Bible, the ISV® does not use the traditional Masoretic Text of the Hebrew Scriptures as the base language original for rendering much of the English language translation of the ISV® Old Testament. Instead, the book of Isaiah was translated directly from the text of the Great Isaiah Scroll (1QIsa), which was found among the Qumran Cave 1 collection of manuscripts and dates from the mid-second century BC. In contrast, the Masoretic Text dates much later, from c. 950-1050 AD.&#8221;</p>
<p>My question: Is the Masoretic Text the base for most of the translation or not?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by Jose Sanchez</title>
		<link>http://isv.org/blog/?p=1#comment-265</link>
		<dc:creator>Jose Sanchez</dc:creator>
		<pubDate>Wed, 25 Apr 2012 21:48:29 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-265</guid>
		<description>Hey, don&#039;t listen to people who are satisfied with stale bread. This translation has been a breath of fresh air, and I can&#039;t wait until it comes out in print.

Yes it&#039;s true, that God does not change, but the bible is not God. It is the work of our hands and it is subject to time and new developments.

As a matter of fact, God is the author of Time and Growth. God is not afraid of change, He is the guiding hand of the whole process. This is what makes him sovereign and unchangeable.

As knowledge increases, new wisdom and understanding is revealed. Were previous individuals from past ages wrong? No, they were simply walking in faith. What was blind faith to them, is common knowledge to us now. and What is faith for us, will be common knowledge to our children and grand children. 

&quot;For the earth shall be filled with the knowledge of the glory of the LORD, as the waters cover the sea.&quot;

If this is God&#039;s ultimate goal, then do not allow yourselves to be boggled down by the shadows of archaic language and let the living waters flow to reawaken our hearts to yearn more for God.

If God wanted to be inaccessible to mankind, then He would have never sent His unique Son to do a work that no one on this planet, before or after, will every complete.

What makes Jesus Unique? He&#039;s the only one who can fulfill the following passage:

Proverbs 8:22-36

Does it matter to the Lord if you call him Jesus or Yeshua?

Does it matter to the Lord if you&#039;re Asian or American?

Let&#039;s leave the childish games behind and lets move to newer levels of growth in Spirit and truth.

Zechariah 14:9 &quot;And the LORD shall be king over all the earth: in that day shall there be one LORD, and his name one.&quot;

And everyone will know that name. for the name of God is That He Is. God is Active, Living, Life, not letters written on some ancient parchment. It takes spiritual maturity to understand this.

God bless.</description>
		<content:encoded><![CDATA[<p>Hey, don&#8217;t listen to people who are satisfied with stale bread. This translation has been a breath of fresh air, and I can&#8217;t wait until it comes out in print.</p>
<p>Yes it&#8217;s true, that God does not change, but the bible is not God. It is the work of our hands and it is subject to time and new developments.</p>
<p>As a matter of fact, God is the author of Time and Growth. God is not afraid of change, He is the guiding hand of the whole process. This is what makes him sovereign and unchangeable.</p>
<p>As knowledge increases, new wisdom and understanding is revealed. Were previous individuals from past ages wrong? No, they were simply walking in faith. What was blind faith to them, is common knowledge to us now. and What is faith for us, will be common knowledge to our children and grand children. </p>
<p>&#8220;For the earth shall be filled with the knowledge of the glory of the LORD, as the waters cover the sea.&#8221;</p>
<p>If this is God&#8217;s ultimate goal, then do not allow yourselves to be boggled down by the shadows of archaic language and let the living waters flow to reawaken our hearts to yearn more for God.</p>
<p>If God wanted to be inaccessible to mankind, then He would have never sent His unique Son to do a work that no one on this planet, before or after, will every complete.</p>
<p>What makes Jesus Unique? He&#8217;s the only one who can fulfill the following passage:</p>
<p>Proverbs 8:22-36</p>
<p>Does it matter to the Lord if you call him Jesus or Yeshua?</p>
<p>Does it matter to the Lord if you&#8217;re Asian or American?</p>
<p>Let&#8217;s leave the childish games behind and lets move to newer levels of growth in Spirit and truth.</p>
<p>Zechariah 14:9 &#8220;And the LORD shall be king over all the earth: in that day shall there be one LORD, and his name one.&#8221;</p>
<p>And everyone will know that name. for the name of God is That He Is. God is Active, Living, Life, not letters written on some ancient parchment. It takes spiritual maturity to understand this.</p>
<p>God bless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by William P. Welty, Ph.D.</title>
		<link>http://isv.org/blog/?p=1#comment-223</link>
		<dc:creator>William P. Welty, Ph.D.</dc:creator>
		<pubDate>Thu, 12 Apr 2012 14:26:37 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-223</guid>
		<description>We&#039;re working on typesetting and choosing a printing house. We think the completed ISV might be available sometime this summer in leather-bound and hardback editions.</description>
		<content:encoded><![CDATA[<p>We&#8217;re working on typesetting and choosing a printing house. We think the completed ISV might be available sometime this summer in leather-bound and hardback editions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by David McLenachen Sr.</title>
		<link>http://isv.org/blog/?p=1#comment-222</link>
		<dc:creator>David McLenachen Sr.</dc:creator>
		<pubDate>Thu, 12 Apr 2012 13:58:24 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-222</guid>
		<description>When will the complete ISV be available?</description>
		<content:encoded><![CDATA[<p>When will the complete ISV be available?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by Andrew T.</title>
		<link>http://isv.org/blog/?p=1#comment-194</link>
		<dc:creator>Andrew T.</dc:creator>
		<pubDate>Tue, 03 Apr 2012 20:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-194</guid>
		<description>My comments indeed contained a few presuppositions.  I presuppose that if a strategy is employed to ensure integrity of Hebrew name appearing in the NT is used in one place, it should be employed in all places.  Likewise, I presuppose that when scholars sit down to translate bibles, they generally seek to be consistent in their efforts.  I was pointing out that by sticking with &#039;traditional&#039; names here; you&#039;re not being consistent linguistically, but no worries – you are in very good company!  Even so, you are correct that my comments were too selective.

That being said, I didn&#039;t need to ask about other traditional names, such as Mary, Joseph or others, because my point about consistency is true, whichever name is translated; none of the traditional names translated from the Greek are Greek.   Therefore all of the traditional names, translated as such, are being translated through a Greek filter.  This makes the question more urgent.  The ISV seems to simply follow this trend, without question (and I would add substantiation).

I suppose, as long as the ISV&#039;s translation strategy is transparent, that tradition is considered before linguistic fidelity, the only critique remaining would be to ask why this should be the case that tradition is given such precedence?  However, I disagree that this question does not merit a response (even after having read your Translation Strategy page).  If you knowingly render Hebrew names into English indirectly through a Greek filter, you either do so knowingly or unknowingly.  If this approach is done knowingly, there must be a reason, whether or not other translations had one.  If it is done unknowingly because of convention, that still does not justify the approach unquestionably.</description>
		<content:encoded><![CDATA[<p>My comments indeed contained a few presuppositions.  I presuppose that if a strategy is employed to ensure integrity of Hebrew name appearing in the NT is used in one place, it should be employed in all places.  Likewise, I presuppose that when scholars sit down to translate bibles, they generally seek to be consistent in their efforts.  I was pointing out that by sticking with &#8216;traditional&#8217; names here; you&#8217;re not being consistent linguistically, but no worries – you are in very good company!  Even so, you are correct that my comments were too selective.</p>
<p>That being said, I didn&#8217;t need to ask about other traditional names, such as Mary, Joseph or others, because my point about consistency is true, whichever name is translated; none of the traditional names translated from the Greek are Greek.   Therefore all of the traditional names, translated as such, are being translated through a Greek filter.  This makes the question more urgent.  The ISV seems to simply follow this trend, without question (and I would add substantiation).</p>
<p>I suppose, as long as the ISV&#8217;s translation strategy is transparent, that tradition is considered before linguistic fidelity, the only critique remaining would be to ask why this should be the case that tradition is given such precedence?  However, I disagree that this question does not merit a response (even after having read your Translation Strategy page).  If you knowingly render Hebrew names into English indirectly through a Greek filter, you either do so knowingly or unknowingly.  If this approach is done knowingly, there must be a reason, whether or not other translations had one.  If it is done unknowingly because of convention, that still does not justify the approach unquestionably.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by Andrew T.</title>
		<link>http://isv.org/blog/?p=1#comment-192</link>
		<dc:creator>Andrew T.</dc:creator>
		<pubDate>Tue, 03 Apr 2012 18:22:28 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-192</guid>
		<description>Many traditional English bibles transliterated biblical names from OT Hebrew into English directly as &#039;Elijah&#039;, &#039;Jeremiah&#039;, and &#039;Hezekiah&#039; (for example), but transliterated the same names from the Greek indirectly into English as &#039;Elias&#039;, &#039;Jeremy&#039;, and &#039;Ezekias&#039;.  This confused people because well-known biblical names would adopt multiple forms having been morphed through Greek case systems (such as nominative).

Many modern translations, including this ISV, &#039;minimize&#039; this type of confusion by translating obvious biblical names found in NT Greek directly from their Hebrew roots, ignoring the influence of Greek language cases.  Such examples are:  Elijah rather than Elias in [Matt 11:14] and [Mark 6:15]; Jeremiah rather than Jeremy in [Matt 2:17] and [Matt 27:9]; and Hezekiah rather than Ezekias in [Matt 1:9-10].  This seems to be a great translation strategy, so why did the ISV translation committee (like so many others) decide to do this selectively?

&lt;blockquote&gt;&lt;strong&gt;&lt;em&gt;In a word, we didn&#039;t translate names &quot;selectively&quot;. More on your presuppositional errors, below&lt;/strong&gt;&lt;/em&gt;&lt;/blockquote&gt;

The Greek name of the anointed one Ἰησοῦς (G2424) is a transliteration (in nominative form) of the beautiful Hebrew name יהושוע (H3091) meaning ‘Yahweh is salvation’.  Even the genitive form of the name in Greek is closer to the Hebrew original.  Although the name יהושוע is normally transliterated into English as Joshua, your strategy may be to avoid confusion with the OT Joshua and yet still treat the Messiah’s name uniquely by denoting it from others.  If so, perhaps you could transliterate it more directly as one of its modern recognizable forms, such as Yahshua, Yehshua, Yeh’shua, or something else.

So the question is:  Why are you using this Hebrew name normalization strategy in every other instance except where the name of the anointed one appears? 

&lt;blockquote&gt;&lt;strong&gt;&lt;em&gt;The name &quot;Jesus&quot; isn&#039;t the only place where we employ traditional name translation. The names &quot;Mary,&quot; &quot;Joseph,&quot; and other names are also translations.&lt;/strong&gt;&lt;/em&gt;&lt;/blockquote&gt;

Do you believe the Messiah was Greek? 

&lt;blockquote&gt;&lt;strong&gt;&lt;em&gt;No, we don&#039;t.&lt;/strong&gt;&lt;/em&gt;&lt;/blockquote&gt;

Or perhaps you’ve decided against adopting a consistent approach because the sheer weight of tradition is too great a thing to resist?

Whatever the case, simply avoiding the issue by sticking with a corrupted Greek form of the name for traditional reasons simply seems to lack exegetical courage, and inconsistent with your otherwise sound translation strategy.

&lt;blockquote&gt;&lt;strong&gt;&lt;em&gt;Our view of this last paragraph is that the view contained in it is far too insulting to merit response by us. We do not lack &quot;exegetical courage,&quot; whatever that phrase might mean to you. We suggest you read our Principles of Translation page on our web site.&lt;/strong&gt;&lt;/em&gt;&lt;/blockquote&gt;

</description>
		<content:encoded><![CDATA[<p>Many traditional English bibles transliterated biblical names from OT Hebrew into English directly as &#8216;Elijah&#8217;, &#8216;Jeremiah&#8217;, and &#8216;Hezekiah&#8217; (for example), but transliterated the same names from the Greek indirectly into English as &#8216;Elias&#8217;, &#8216;Jeremy&#8217;, and &#8216;Ezekias&#8217;.  This confused people because well-known biblical names would adopt multiple forms having been morphed through Greek case systems (such as nominative).</p>
<p>Many modern translations, including this ISV, &#8216;minimize&#8217; this type of confusion by translating obvious biblical names found in NT Greek directly from their Hebrew roots, ignoring the influence of Greek language cases.  Such examples are:  Elijah rather than Elias in [Matt 11:14] and [Mark 6:15]; Jeremiah rather than Jeremy in [Matt 2:17] and [Matt 27:9]; and Hezekiah rather than Ezekias in [Matt 1:9-10].  This seems to be a great translation strategy, so why did the ISV translation committee (like so many others) decide to do this selectively?</p>
<blockquote><p><strong><em>In a word, we didn&#8217;t translate names &#8220;selectively&#8221;. More on your presuppositional errors, below</em></strong></p></blockquote>
<p>The Greek name of the anointed one Ἰησοῦς (G2424) is a transliteration (in nominative form) of the beautiful Hebrew name יהושוע (H3091) meaning ‘Yahweh is salvation’.  Even the genitive form of the name in Greek is closer to the Hebrew original.  Although the name יהושוע is normally transliterated into English as Joshua, your strategy may be to avoid confusion with the OT Joshua and yet still treat the Messiah’s name uniquely by denoting it from others.  If so, perhaps you could transliterate it more directly as one of its modern recognizable forms, such as Yahshua, Yehshua, Yeh’shua, or something else.</p>
<p>So the question is:  Why are you using this Hebrew name normalization strategy in every other instance except where the name of the anointed one appears? </p>
<blockquote><p><strong><em>The name &#8220;Jesus&#8221; isn&#8217;t the only place where we employ traditional name translation. The names &#8220;Mary,&#8221; &#8220;Joseph,&#8221; and other names are also translations.</em></strong></p></blockquote>
<p>Do you believe the Messiah was Greek? </p>
<blockquote><p><strong><em>No, we don&#8217;t.</em></strong></p></blockquote>
<p>Or perhaps you’ve decided against adopting a consistent approach because the sheer weight of tradition is too great a thing to resist?</p>
<p>Whatever the case, simply avoiding the issue by sticking with a corrupted Greek form of the name for traditional reasons simply seems to lack exegetical courage, and inconsistent with your otherwise sound translation strategy.</p>
<blockquote><p><strong><em>Our view of this last paragraph is that the view contained in it is far too insulting to merit response by us. We do not lack &#8220;exegetical courage,&#8221; whatever that phrase might mean to you. We suggest you read our Principles of Translation page on our web site.</em></strong></p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by William P. Welty, Ph.D.</title>
		<link>http://isv.org/blog/?p=1#comment-112</link>
		<dc:creator>William P. Welty, Ph.D.</dc:creator>
		<pubDate>Sat, 03 Mar 2012 15:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-112</guid>
		<description>We have referred your suggestion to Davidson Press for further discussion.</description>
		<content:encoded><![CDATA[<p>We have referred your suggestion to Davidson Press for further discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by Brian Moyer</title>
		<link>http://isv.org/blog/?p=1#comment-111</link>
		<dc:creator>Brian Moyer</dc:creator>
		<pubDate>Sat, 03 Mar 2012 03:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-111</guid>
		<description>Moody Publishers has decided not to renew its contract with Zondervan, so once the current stock of 1984 NIV Ryrie Study Bibles is sold, the Ryrie Study Bible will no longer be published using the NIV. Zondervan has discontinued the 1984 edition of the NIV and will only publish the 2011 NIV with gender modified language.   

I would encourage you to consider contacting Moody Publishers to utilize the ISV as a replacement for the NIV? Thank you,</description>
		<content:encoded><![CDATA[<p>Moody Publishers has decided not to renew its contract with Zondervan, so once the current stock of 1984 NIV Ryrie Study Bibles is sold, the Ryrie Study Bible will no longer be published using the NIV. Zondervan has discontinued the 1984 edition of the NIV and will only publish the 2011 NIV with gender modified language.   </p>
<p>I would encourage you to consider contacting Moody Publishers to utilize the ISV as a replacement for the NIV? Thank you,</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome to The Catacombs by wpwelty</title>
		<link>http://isv.org/blog/?p=1#comment-84</link>
		<dc:creator>wpwelty</dc:creator>
		<pubDate>Sun, 29 Jan 2012 16:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://isv.org/blog/?p=1#comment-84</guid>
		<description>Cadre&#039;s edition was released 15 days after the Kindle version, and is the latest edition. Kindle was sent the new edition but has not yet updated it. We do not control the frequency with which the electronic publisher updates its ebook copies of the ISV, but our arrangement with them calls for them automatically to send free updates to the text of the ISV to their registered users, similar in fashion to the policies and practice of iPhone or iPad apps. But in practice they don&#039;t do this very often. 

We don&#039;t have access to their list of purchasers of the electronic editions of the ISV, either, so we cannot notify them of the availability of free updates. That&#039;s the main reason we would prefer that ISV purchasers obtain them from the Davidson Press sales page at http://davidsonpress.com/EmbedEULA.htm.

The build numbers for the ISV follow the format &quot;vn.n YYYY.MM.DD&quot; where &quot;v.n.n&quot; is the version number, &quot;YYYY&quot; is the year, &quot;MM&quot; is the month in numbers, and &quot;DD&quot; is the day of the month of the release.


William O, Welty, Ph.D.
ISV Foundation</description>
		<content:encoded><![CDATA[<p>Cadre&#8217;s edition was released 15 days after the Kindle version, and is the latest edition. Kindle was sent the new edition but has not yet updated it. We do not control the frequency with which the electronic publisher updates its ebook copies of the ISV, but our arrangement with them calls for them automatically to send free updates to the text of the ISV to their registered users, similar in fashion to the policies and practice of iPhone or iPad apps. But in practice they don&#8217;t do this very often. </p>
<p>We don&#8217;t have access to their list of purchasers of the electronic editions of the ISV, either, so we cannot notify them of the availability of free updates. That&#8217;s the main reason we would prefer that ISV purchasers obtain them from the Davidson Press sales page at <a href="http://davidsonpress.com/EmbedEULA.htm" rel="nofollow">http://davidsonpress.com/EmbedEULA.htm</a>.</p>
<p>The build numbers for the ISV follow the format &#8220;vn.n YYYY.MM.DD&#8221; where &#8220;v.n.n&#8221; is the version number, &#8220;YYYY&#8221; is the year, &#8220;MM&#8221; is the month in numbers, and &#8220;DD&#8221; is the day of the month of the release.</p>
<p>William O, Welty, Ph.D.<br />
ISV Foundation</p>
]]></content:encoded>
	</item>
</channel>
</rss>

