FSSL said:visit the other fundamentalforum...
I believe I'm thru with that joint.
FSSL said:visit the other fundamentalforum...
FSSL said:A functional equivalent vis-a-vis formal equivalent approach both have their weaknesses and strengths. Both are valuable contributions to the translation world.
thethinkingrebel said:One point I read recently, was that the KJV keeps many preachers in a job, as it allows them to simply take a verse, explain what it means for an hour then call it a sermon.
FSSL said:thethinkingrebel said:One point I read recently, was that the KJV keeps many preachers in a job, as it allows them to simply take a verse, explain what it means for an hour then call it a sermon.
......... Our duty, as expositors of God's word is to understand the original author's intent, NOT the understandings of Anglicans in the 1600s.
FSSL said:FSSL Our duty, as expositors of God's word is to understand the original author's intent, NOT the understandings of Anglicans in the 1600s.
Bob H And that's from a formal equivalent translation. I'm glad you see things my way now.
Problem... a formal equivalent translation does not always give the original author's intent... Consider the following example from the NASB
We give thanks to God, the Father of our Lord Jesus Christ, praying always for you, Col 1:3
In the originals, the word "always" does modify the word "praying." The word-for-word translation makes it appear that "always" goes with "praying" because the two are in close proximity to each other.
The problem is that in Koine Greek, an adverb generally follows the verb it modifies. The NIV gets it right:
We always thank God, the Father of our Lord Jesus Christ, when we pray for you...
This is just one example of the weakness of a formal, word-for-word translation...
FSSL said:There is no textual difference here. The Greek texts are the same.
Bob H said:FSSL said:There is no textual difference here. The Greek texts are the same.
My bad. You mentioned the NASB and the NIV, not the KJ. Reading is my friend
Winston said:300 words found in the KJV no longer bear the same meaning
Winston said:Third, the King James Bible has undergone three revisions since its inception in 1611, incorporating more than 100,000 changes. Which King James Bible is inspired, therefore?
FSSL said:Bob H said:First off I'm not a KJVO so I don't want to hear it.
Then why state it? If your position is for all practical purposes different than the KJVO position, it would be very clear and you would not need to begin with this caveat. But, with that in mind... I will not accuse you of being a KJVO, just a defender of their particular tradition.
I'm a FETO {Formal equivalent translation only}..................which leaves out most of them It's our job to interpret scriptures not the translaters. They translate we interpret
To make this claim means that you have never translated from the Greek and Hebrew. If you have, you know very well that translating (formally or functionally), you will need to interpret. ALL Bibles have interpretations including the KJV and ESV.
Excuse my French but Thuppppppppppppp! The KJV is not the problem. It can be preached and taught and understandable. The problem is with the reader/studier... The Elizabethon language excuse is just an ...............................excuse.
The word of God has never been intended to become obscure in a language that the people no longer use. Even the KJV translators recognized this.
I highly recommend this book: http://www.amazon.com/The-Word-God-English-Translation/dp/1581344643/ref=la_B001H6S2UG_1_12?ie=UTF8&qid=1340040187&sr=1-12 {BTW he was on the ESV translation committee}
I highly recommend the ESV... The preface to the ESV states: "Archaic language has been brought to current usage and significant corrections have been made in the translation of key texts."
Since the ESV is more consistent in its formal equivalent approach than the KJV, then "God forbid" why defend the KJV?
To suggest that we are to stay with the KJV in 2012 means that you are given to a tradition, rather than bringing the word of God to current usage and making the much needed significant corrections.
logos1560 said:Winston said:300 words found in the KJV no longer bear the same meaning
Lisa Ruby said:Actually what many object to in the King James Bible is not "archaic" terms, although that is the excuse to abandon it. It is politically incorrect terms and anti-ecumenical terms that are at the core of many people's hatred of this English Bible.
Modern versions usually remove the word,
Ransom said:Why do you like the ESV so much? It removes key words. In Psalm 109:6 "Satan" is removed.
Quit lying, Ruby. It wasn't "removed." It was translated literally, and appropriately for its context. The "accuser" of 6b parallels the "wicked man" of 6a. The psalmist is essentially saying that there is no more fitting retribution than for a wicked man and a liar to to be judged by one just like himself. The "accuser" could be Satan, but there's no reason he has to be (except to prop up a silly prejudice against a translation of the Word of God that happens not to be the one you pretend to worship and obey).
It is politically incorrect terms and anti-ecumenical terms that are at the core of many people's hatred of this English Bible.
Modern versions usually remove the word, sodomites, for example, and replace that politically incorrect word with cult prostitute or male shrine prostitutes, etc.
Lisa Ruby said:logos1560 said:Winston said:300 words found in the KJV no longer bear the same meaning