• Welcome to Baptist Board, a friendly forum to discuss the Baptist Faith in a friendly surrounding.

    Your voice is missing! You will need to register to get access to all the features that our community has to offer.

    We hope to see you as a part of our community soon and God Bless!

Difficult Words

Logos1560

Well-Known Member
Site Supporter
Baptist4life said:
You know, the whole point of the OP was to show that the claim that the KJV uses archaic words and MV's don't is false. .

Did it prove that point? There is an important difference between "difficult" words and "archaic" words. "Difficult" words are likely words still in use today and are still in common one-volume English dictionaries. "Archaic" words may still be in use today, but they are used with a meaning different from that they had in the 1500's and 1600's. People may assume that they know the meaning of those words and not realize that they were used in that day in a very different sense. Some archaic words are not listed in one-volume English dictionaries, and others, that are listed, are not presented with the definition that fits the way the word was used in the pre-1611 English Bibles and the KJV.

Do KJV-only posters such as the one that started this thread admit the fact that the KJV translators themselves updated a number of archaic words in the pre-1611 English Bibles and made their renderings simpler or easier in a number of verses?
 

Logos1560

Well-Known Member
Site Supporter
KJVBibleThumper said:
According to the Flesch-Kincaid Grade Level test, out of 26 catagories, the King James was graded easier in 23. According to that test, the King James reads at a grade level of 5.8, while the NIV reads at a grade level of 8.4.
Thumper

C4K responded: "Your use of the Flesch-Kincaid Grade Level test has nothing to do with archaic and out of date words. It is based only on the numbers of syllables in a word and the number of words in a sentence. It does not attempt to take out of date words into account and therefore is false measure of readability."

You seem to be repeating a typical KJV-only claim that actually misrepresents the facts as one poster already noted. For example, KJV-only author R. B. Ouellette claimed that it is a false statement to say that the KJV “is harder to read and understand” (A More Sure Word, p. 150). As support for his claim, Ouellette asserted that the KJV “has a significantly lower average syllable count” (Ibid.). Gail Riplinger also maintained that “the KJV averages less syllables per word” (Language, p. 159). Riplinger claimed that the KJV’s average was 1.310 syllables per word and that the NKJV’s average was 1.313 syllables per word (p. 160). Is that a significant difference? Furthermore, there may be some reasons why the KJV may have a lower average syllable count that have no bearing on whether or not it is easier to read. For example, in most editions of the KJV there are several commonly used words that are divided into two or more words where the exact same word united as one word in another translation may count as a longer, multi-syllable word. Some examples include “to day,” “to morrow,” “for ever,” “for evermore,” “son in law,” “mother in law,” “daughter in law,” “strong holds,“ “way side,” “good will,” and “mean while.” There are also other such words. A few words may be united in the KJV that are divided into two words in another translation. Overall, because those words divided in the KJV are more commonly used words, they would contribute to giving the KJV a lower average syllable count. Those words do not actually make the KJV easier to read. By the way, some present KJV editions would unite some of those words such as “to day” to either “to-day” or “today” so that these KJV editions would have a different average syllable count. The 1611 KJV edition had “shall be” united as one, longer word “shalbe,” and it would likely have a different average syllable count. More importantly, the KJV has a number of archaic words or words used with archaic meanings that may be shorter or have fewer syllables than their present equivalents. Some examples could include “turtle” for “turtledove,” “vale“ for “valley,” “dearth“ for “famine,” “trump“ for “trumpet,” “tongue“ for “language,” “even“ for “evening,” “let” for “hinder,” “anon” for “immediately,” “sod” for “boiled,” “mete“ for “measure,” “dure“ for “endure,” “quick“ for “living“ or “alive,” “still” for “continually,” “attent“ for “attentive,” “by and by” for “immediately,” “ere“ for “before,” “minish” for “diminish,” “fine” for “refine,” “astonied” for “astonished,“ and “rid” for “deliver.” While such words may help reduce the KJV’s average syllable count, they do not actually make it easier to read and understand. These reasons or factors indicate why claims concerning “average syllable count” and reading level claims may be misleading.
 

Logos1560

Well-Known Member
Site Supporter
KJVBibleThumper said:
Much as been said on here about the archaic words In the King James, and it is true that there are a number of words in the KJV that have passed out of modern usage. Thumper

How many words in the KJV would you identify as being archaic? Do you claim that it is wrong for archaic words to be updated?
 

Pastor Larry

<b>Moderator</b>
Site Supporter
m saying that some of the words of the NIV are more ARCHAIC than some of the words in the KJV, yet I NEVER hear anyone criticize the NIV for archaic words!
We know you are saying that. We are pointing out that you are wrong. Some of the words are more unknown, but being unknown is not the same as being archaic.

I don't think you compared the "archaicness" of the words in question. You simply showed that the NIV on occasion uses a word this listmaker was ignorant of. He doesn't compare the multitude of the times the situation is reversed, where the KJV uses an archaic or unknown word and the NIV does not.

So it was a misguided study from the very beginning.

I criticized the NIV several times in my comments on each of these occurrences. There are some bad translations and bad word choices in the NIV. I think many of us here have said that before.
 

KJVBibleThumper

New Member
Logos1560 said:
How many words in the KJV would you identify as being archaic? Do you claim that it is wrong for archaic words to be updated?
There is no doubt that there are a number of words in the KJV that have passed out of common usage, but many of them frankly have no "modern" word that that can be used in their place and carry the same weight or idea. Bst just to leave well enough alone. Why mess around with it? Just get a dictionary.
 

Logos1560

Well-Known Member
Site Supporter
KJVBibleThumper said:
There is no doubt that there are a number of words in the KJV that have passed out of common usage, but many of them frankly have no "modern" word that that can be used in their place and carry the same weight or idea. .

Really? Are you aware of the fact that the KJV translators themselves updated a number of those same type words in one or more of the pre-1611 English Bibles with other words that are more up-to-date and they evidently considered them to carry the same sense or idea?

For which words in the KJV are there no "modern" words that can be used in their place and carry the same weight or idea?
 

4His_glory

New Member
KJVBibleThumper said:
There is no doubt that there are a number of words in the KJV that have passed out of common usage, but many of them frankly have no "modern" word that that can be used in their place and carry the same weight or idea. Bst just to leave well enough alone. Why mess around with it? Just get a dictionary.

Please give an example of an archaic word in the KJV that has no modern equivalent.
 

Logos1560

Well-Known Member
Site Supporter
KJVBibleThumper said:
Bst just to leave well enough alone. Why mess around with it? quote]

Are you implying that it was wrong for the KJV translators to update a number of words in the Bishops' Bible of which it was a revision and to make the language of the Bishops' Bible simpler or easier in a number of places? Were the KJV translators wrong to mess around with the words used in the pre-1611 English Bibles of which it was a revision?
 

Logos1560

Well-Known Member
Site Supporter
According to the second rule given the KJV translators, the KJV was a revision of the Bishops' Bible. Here are some examples from the book of Genesis where the KJV could be said to make simpler, to update, or to revise the text of the Bishops' Bible.


Gen. 2:10 And out of Eden there went forth a flood to water the garden (Bishops’)
And a river went out of Eden to water the garden (KJV)
Gen. 3:4 ye shall not die the death (Bishops) Ye shall not surely die (KJV)
Gen. 4:3 an oblation (Bishops) an offering (KJV)
Gen. 4:4 to his oblation (Bishops) to his offering (KJV)
Gen. 4:5 Cain was exceeding wroth (Bishops) Cain was very wroth (KJV)
Gen. 4:5 his countenaunce abated (Bishops) his countenance fell (KJV)
Gen. 4:9 Which said I wot not (Bishops) And he said, I know not (KJV)
Gen. 4:26 make invocation in the name (Bishops) call upon the name (KJV)
Gen. 6:5 malice of man (Bishops) wickedness of man (KJV)
Gen. 6:14 pine trees: habitations (Bishops) gopher wood; rooms (KJV)
Gen. 6:20 feathered fowls (Bishops) fowls (KJV)
Gen. 7:18 waters also waxed strong (Bishops) waters prevailed (KJV)
Gen. 9:7 breed in the earth (Bishops) bring forth abundantly in the earth (KJV)
Gen. 12:20 they convayed him forth (Bishops) they sent him away (KJV)
Gen. 13:1 And so Abram gat him up (Bishops) And Abram went up (KJV)
Gen. 16:2 I may be builded by her (Bishops) I may obtain children by her (KJV)

Gen. 18:6 went apace (Bishops) hastened (KJV)
Gen. 18:6 pecks (Bishops) measures (KJV)
Gen. 18:14 unpossible (Bishops) too hard (KJV)
Gen. 18:22 went to Sodomeward (Bishops) went toward Sodom (KJV)
Gen. 19:15 angels caused Lot to speed him (Bishops) angels hastened Lot (KJV)
Gen. 20:2 fet Sara away (Bishops) took Sarah (KJV)
Gen. 20:6 I wote well that thou diddest it in the singleness of thy heart (Bishops)
I know that thou didst this in the integrity of thy heart (KJV)
Gen. 20:8 betimes (Bishops) early (KJV)
Gen. 23:3 Abraham stood up fro the sight of his corpse (Bishops)
Abraham stood up from before his dead (KJV)
Gen. 23:6 a prince of God (Bishops) a mighty prince (KJV)
Gen. 24:15 ere he had left speaking (Bishops) before he had done speaking (KJV)
Gen. 24:32 he unharnessed the camels and brought litter and provender (Bishops)
he ungirded his camels and gave straw and provender (KJV)
Gen. 24:65 walking against us in the field (Bishops) walketh in the field to meet us (KJV)
Gen. 25:8 Abraham waxing away, died in a lusty age (Bishops)
Abraham gave up the ghost and died in a good old age (KJV)
Gen. 26:1 there fell a famine (Bishops) there was a famine (KJV)
Gen. 27:1 Isahac waxed old (Bishops) Isaac was old (KJV)
Gen. 27:7 dainty meat (Bishops) savoury meat (KJV)
Gen. 27:7 afore my death (Bishops) before my death (KJV)
Gen. 27:15 Rebecca fet (Bishops) Rebekah took (KJV)
Gen. 27:44 fierceness be swaged (Bishops) fury turn away (KJV)
Gen. 29:28 passed out the week (Bishops) fulfilled her week (KJV)
Gen. 30:11 Then said Lea, Good luck (Bishops) And Leah said, A troop cometh (KJV)
Gen. 30:34 go to, would God it might be (Bishops) Behold, I would it might be (KJV)
Gen. 31:18 substance which he had procured (Bishops) goods which he had gotten (KJV)
Gen. 31:36 doest sore pursue after me (Bishops) hast so hotly pursued after me (KJV)
Gen. 32:7 wist not which way to turn him self (Bishops) distressed (KJV)
Gen. 33:6 did their obeisance (Bishops) bowed themselves (KJV)
Gen. 34:19 for to do (Bishops) to do (KJV)
Gen. 35:29 Isahac decayed away (Bishops) Isaac gave up the ghost (KJV)
Gen. 37:20 some naughty beast (Bishops) some evil beast (KJV)
Gen. 37:21 he rid him out (Bishops) he delivered him out (KJV)
Gen. 37:26 keep his blood secret (Bishops) conceal his blood (KJV)
Gen. 37:33 naughty beast (Bishops) evil beast (KJV)
Gen. 38:1 gat him to a (Bishops) turned in to a (KJV)
Gen. 38:14 for because (Bishops) for (KJV)
Gen. 38:19 And she gat her up (Bishops) And she arose (KJV)
Gen. 38:20 for to receive (Bishops) to receive (KJV)
Gen. 39:2 he became a lucky man (Bishops) he was a prosperous man (KJV)
Gen. 40:15 I was privily by stealth taken away (Bishops) I was stolen away (KJV)
Gen. 40:16 me thought also in my dream (Bishops) I also was in my dream (KJV)
Gen. 42:1 why gape ye one upon another (Bishops) why do ye look one upon another (KJV)
Gen. 42:10 buy victual (Bishops) buy food (KJV)
Gen. 43:14 thus I am as one that is quite robbed of his children (Bishops)
If I be bereaved of my children, I am bereaved (KJV)

Gen. 44:28 of a surety (Bishops) surely (KJV)
Gen. 45:1 cause every man to avoid (Bishops) cause every man to go out from me (KJV)
Gen. 45:21 victual also to spend by the way (Bishops) provision for the way (KJV)
Gen. 47:13 the dearth was exceeding sore (Bishops) the famine was very sore (KJV)
Gen. 48:22 which I gat out of the hand (Bishops) which I took out of the hand (KJV)
Gen. 49:4 shalt not be the chiefest (Bishops) shalt not excell (KJV)
Gen. 49:9 spoil (Bishops) prey (KJV)
Gen. 49:28 every one of them blessed he with a several blessing (Bishops)
every one according to his blessing he blessed them (KJV)
Gen. 50:9 exceeding great (Bishops) very great (KJV)
 

Logos1560

Well-Known Member
Site Supporter
Here are some examples from the book of Judges.

Jud. 1:28 waxed mighty (Bishops) was strong (KJV)
Jud. 2:9 in the coasts (Bishops) in the border (KJV)
Jud. 2:14 waxed hot (Bishops) was hot (KJV)
Jud. 3:4 to wit whether (Bishops) to know whether (KJV)
Jud. 3:15 a man lame of his right hand (Bishops) a man lefthanded (KJV)
Jud. 3:23 gat him out (Bishops) went forth (KJV)
Jud. 4:21 he slumbered sore (Bishops) he was fast asleep (KJV)
Jud. 5:17 tarried in his decayed places (Bishops) abode in his breaches (KJV)
Jud. 6:8 I fet you from Egypt (Bishops) I brought you up from Egypt (KJV)
Jud. 6:9 And I rid you (Bishops) And I delivered you (KJV)
Jud. 6:26 in a convenient place (Bishops) in the ordered place (KJV)
Jud. 7:13 and me thought that a cake (Bishops) and, lo, a cake (KJV)
Jud. 8:13 afore the sun was up (Bishops) before the sun was up (KJV)
Jud. 9:26 gat them to Shechem (Bishops) went over to Shechem (KJV)
Jud. 9:29 Make thine host greater (Bishops) Increase thine army (KJV)
Jud. 9:48 speed your selves (Bishops) make haste (KJV)
Jud. 9:54 man that bare his harness (Bishops) man his armourbearer (KJV)
Jud. 10:11 Did not I rid you (Bishops) Did not I deliver you (KJV)
Jud. 11:26 in all that space (Bishops) within that time (KJV)
Jud. 11:31 against me (Bishops) to meet me (KJV)
Jud. 11:38 maidenhead (Bishops) virginity (KJV)
Jud. 12:4 runagates (Bishops) fugitives (KJV)
Jud. 13:16 Manoah wist not (Bishops) Manoah knew not (KJV)
Jud. 14:4 father and mother wist not (Bishops) father and his mother knew not (KJV)
Jud. 14:8 And within a short space after (Bishops) And after a time (KJV)
Jud. 15:11 Wottest thou not (Bishops) Knowest thou not (KJV)
Jud. 16:5 silverlings (Bishops) pieces of silver (KJV)
Jud. 17:2 silverlings (Bishops) shekels of silver (KJV)
Jud. 17:8 find a convenient place (Bishops) find a place (KJV)
Jud. 18:10 a people that casteth no perils (Bishops) a people secure (KJV)
Jud. 19:15 turned thitherward (Bishops) turned aside thither (KJV)
Jud. 19:30 take advisement (Bishops) take advice (KJV)
Jud. 20:10 abomination (Bishops) folly (KJV)
Jud. 20:45 to the wilderness ward (Bishops) toward the wilderness (KJV)
Jud. 21:4 people rose up betime (Bishops) people rose early (KJV)
 

franklinmonroe

Active Member
KJVBibleThumper said:
... I am using part of a useful chart from av1611.org that shows the words in the NIV on one side, with the KJV word on the other side, and the reference in between...
I disagree that this is a "useful chart" from an objective presentational perspective. The false impression given by this arrangement is that the two versions are always attempting the same meaning, and by using equivalent methods. Its just not a fair 'apples-to-apples' comparison.

The NIV's translation method is generally 'freer' than the KJV. However, in several cases on this list the NIV has chosen to be less interpretive than the KJV: for examples "Goiim" instead of "nations", "Hades" rather than "hell", "Magi" instead of "wise men", "mina" rather than "pound", and "Nephilim" as opposed to "giants". Note that the NIV has capitalized four of these words as being proper nouns. This fact was obscured by the way the words were presented in the OP (this always raises the question as to whether this was intentional deception or just sloppiness).

The NIV did not intend the to arrive at the exact same meaning as the KJV. The NIV has merely transliterated these words rather than attempt a rendering that could misrepresent the original language (as "pound" almost certainly does now).
 
Last edited by a moderator:

EdSutton

New Member
Baptist4life said:
I'm saying that some of the words of the NIV are more ARCHAIC than some of the words in the KJV, yet I NEVER hear anyone criticize the NIV for archaic words!


NIV KJV
Colonnade I Ki 7:6 Porch
Dissipation I Pet 4:4 Riot
Filigree Ex 28:20 Enclosings
Floodgates Gen 7:11 Windows
Gadfly Jer 46:20 Destruction
Goiim Gen 14:1 Nations
Hades Rev 20:14 Hell
Incited 1 Chr 21:1 Provoked
Jowls Deut 18:3 Cheeks
Magi Matt 2:1 Wise men
Marauders Job 12:6 Robbers
Mina Lk 19:16 Pound
Naïve Rom 16:18 Simple
Negev Gen 12:9 South
Nephilim Gen 6:4 Giants
Offal Ex 29:14 Dung
Piled Lk 23:9 Questioned
Pinions Deut 32:11 Wings
Porphyry Est 1:6 Red
"Uh- Excuse me! Language Cop, here! I would please like to note a few things things here, if I may. Again, with apologies to the great Amercian sage, 'Yogi' Berra, this appears as if 'It's Deja-Moo(1) all over again.'.

1.) Please check these 'lists' you are '"slashin' and stickin'" - 'er I mean "cutting and pasting"' up, for the supposed benefit of the rest of us, before you post them, if you don't mind. The list purports to show the NIV renderings on the left, and supposedly, the KJV renderings on the right. However, this is misleading in at least one instance, among a few I checked thus far, namely I Peter 4:4, in which case, the renderings are reversed, with the supposed "easier" reading on the right. A bit misleading, I would say, at best.
(FTR, of the ~ 40-odd words, I would have to check a dictionary, if the context of the verse did not already clearly show what was meant, in fewer than half-a-dozen of the cases, off the top of my head. Words are 'the beat' of Language Cop, after all.)

2.) Of course, there is noting like having a chance to push an agenda, specifically the supposed superiority (read KJVO, here) of a personal preference, is there? :thumbs:
(My 'smilie' here should either be :rolleyes: or one of a [Tear!] in the place of the one I just posted, actually.)

3.) This listing can also be a bit misleading , as well, for in more than one instance, a word is cited that is part of a compound phrase or perhaps an attempt to translate an idiom. In such cases, this also may be misleading. (But, what's a little inaccuracy among friends, I guess.)

4.) How is it one gets to arbitrarily 'pick and choose' a particular printing or edition of the KJV, from which to cite, anyway?? Here are a few of the words (or phrases), as they would have appeared in the 1612 edition of the KJV, with the Roman font (I cannot, in any manner, reproduce any Gothic font, from a 1611 Edition.), that are about as close as I can reproduce them , from the 1611 KJV, as found on 'studylight' - 'excefse of riot' - I Pet. 4:4; 'inclofings' - Ex. 28:20; and Deut. 18:3 with 'cheekes', where the verse is speaking of the slaughtered parts of an animal.

FTR, as one who has done this, and been around farm animals most of my life, I can assure you that one does not refer to 'cheeks' but 'jowls', as in 'jowl bacon', in the case of pork, or 'beef jowls' or 'mutton jowls' (in the case of a slaughtered sheep), just as the NIV renders the words here.

I was reared on a farm, and have been a full-time farmer for more than 30 years, after the illness and death of my own father, have slaughtered or helped in the slaughter of at least a dozen animals, been around many more as they were slaughtered and processed, including goats, sheep, hogs, and beef, and the next time I hear someone refer to the facial parts of one of these animals as 'cheeks', will be the first time in the more than 45 years, I can fairly clearly remember.

Incidentally, I have heard some of the contents of the abdominal cavity referred to as the 'maw' (KJV), 'stomach' (NKJV) or 'entrails' (or colloquially as 'innards') which is closely akin to the 'inner parts' (NIV), but the usual designation of the whole is that of 'guts', as one will 'gut' the animal, and does not 'de-maw' or 'de-stomach' the animal, regardless of how UN-'politically correct' or distasteful the word 'gut' may appear. :rolleyes:

4.) You really 'might oughter' (sic) consider plying, to some degree anyway, through a copy of the NIV, especially Luke 23 (along with checking out a dictionary - any reputable dictionary - doesn't particularly have to be one of the 1828 variety), before you ply forth what you are attempting to pile on the table, here. I can assure you there is a definite difference in the meanings of the two words, and the use of the correct word, might serve to give one more of a semblance of credibility." :thumbsup:

Signed, Language Cop

(1) -"Deja-Moo" - The distinct feeling you've heard this bull before.


"Hmmm! Does ol' L.C. seem a mite testy today, or is it just me?? You can't always tell about Language Cop."

'Signed,'

Ed
 
Last edited by a moderator:

franklinmonroe

Active Member
KJVBibleThumper said:
Porphyry Est 1:6 Red
It is quite remarkable how many mistakes, misrepresentations, and misinterpretations can be put into a single OP. The impression from the above would be the "Porphyry" is some strange word which means "red".

But the word "Porphyry" is the name of a variety of igneous rock (that is very often reddish in color). It is NOT a term that means "red" by itself (it actually means 'purple' in Greek). The Hebrew word in Esther 1:6 seems to be behat (Strong's #923) and it does NOT mean "red" by itself either. It is translated in the KJV here properly as "red" plus "marble" (the word "marble" comes at the end of the verse and is separated from "red" by a secession of other colors mentioned). Lexicons add the possible rendering of 'costly stone' (even perhaps Porphyry).
 
Last edited by a moderator:

KJVBibleThumper

New Member
franklinmonroe said:
I disagree that this is a "useful chart" from an objective presentational perspective. The false impression given by this arrangement is that the two versions are always attempting the same meaning, and by using equivalent methods. Its just not a fair 'apples-to-apples' comparison.

The NIV's translation method is generally 'freer' than the KJV. However, in several cases on this list the NIV has chosen to be less interpretive than the KJV: for examples "Goiim" instead of "nations", "Hades" rather than "hell", "Magi" instead of "wise men", "mina" rather than "pound", and "Nephilim" as opposed to "giants". Note that the NIV has capitalized four of these words as being proper nouns. This fact was obscured by the way the words were presented in the OP (this always raises the question as to whether this was intentional deception or just sloppiness).

The NIV did not intend the to arrive at the exact same meaning as the KJV. The NIV has merely transliterated these words rather than attempt a rendering that could misrepresent the original language (as "pound" almost certainly does now).
Regarding the list, I checked out about 75% of the references in my NIV to make sure they were accurate, as for the capitalization, that is merely because I was trained in English classes to always capitalize the first word in a list.

Accusing me of duplicity is neither warranted nor necessary, and shows a poor argument.

It is true that the NIV ends up with a different or obscured meaning here in many places, and I would beg to find out, why? Your argument flies in the face of MV claims that all the versions "read the same".

If it is all right to use a dictionary or check context to determine what a passage says, then why is it not alright to do the same thing for a KJV? This is a duplicitious position.

In Christ,
Thumper
 

Rippon

Well-Known Member
Site Supporter
Thumper,would you be allowed to take your NIV to college with you?Or would you have to sneak it in?
 

NaasPreacher (C4K)

Well-Known Member
KJVBibleThumper said:
If it is all right to use a dictionary or check context to determine what a passage says, then why is it not alright to do the same thing for a KJV? This is a duplicitious position.

In Christ,
Thumper

Nothing wrong with it. Question is 'should folks have to do so?'

It is also tougher to find definitions for archaic words than current words.
 

franklinmonroe

Active Member
KJVBibleThumper said:
... So, the question that I am going to address in this article is the following, “do the archaic words in the King James, merit a new translation?”, this is one of the main reason that the modern version state is their reason for existence, the need for a Bible in language that the common man can understand. They are of the opinion that the King James is too difficult to understand and that their new version reads much easier...
It doesn't seem to me that an answer can be achieved for this question through listing the difficult words of another version. The only thing that discussing difficult words from another version accomplishes is that the other version may merit a new translation. It does nothing to advance the stated goal in the OP.

Was there going to be an honest attempt at answering this question? Baptist4life seemed to think that "the whole point of the OP was to show that the claim that the KJV uses archaic words and MV's don't is false". Was that the purpose? Was Thumper lying when he wrote that the OP was to address the "archaic words in the King James" possibly justifying a revised translation? In post #20 Thumper wrote that "the original point I made seems to have pretty much been ignored". What point was that, Thumper? In post #45 you seem to have already made up your mind --
KJVBibleThumper said:
There is no doubt that there are a number of words in the KJV that have passed out of common usage, but many of them frankly have no "modern" word that that can be used in their place and carry the same weight or idea. Bst just to leave well enough alone. Why mess around with it? Just get a dictionary.
Did Thumper have this mindset all along? Did he honestly ever considered the OP proposition?
 
Last edited by a moderator:

franklinmonroe

Active Member
KJVBibleThumper said:
Regarding the list, I checked out about 75% of the references in my NIV to make sure they were accurate,...
Does checking 75% seem good enough to you now?
KJVBibleThumper said:
... as for the capitalization, that is merely because I was trained in English classes to always capitalize the first word in a list...
A simple admission that you made a mistake will suffice.
KJVBibleThumper said:
Accusing me of duplicity is neither warranted nor necessary, and shows a poor argument.
Actually, I didn't accuse you. I simply commented that there is more than one explanation for it (and it happens a lot). For all I knew, the capitalization could have been original with your source. After all the errors that you have obviously made in your OP, do you really think you should be giving advice about argumentation?
KJVBibleThumper said:
It is true that the NIV ends up with a different or obscured meaning here in many places, and I would beg to find out, why? Your argument flies in the face of MV claims that all the versions "read the same".
I don't believe I made an argument for MVs "read the same" here. Perhaps you'd like to show it to me?

I love you, brother Thumper. I mean you no ill will. I hope you will take this as a learning experience. I wish you well at PCC. BTW, what are you studying?
 
Last edited by a moderator:

KJVBibleThumper

New Member
franklinmonroe said:
Does checking 75% seem good enough to you now?

A simple admission that you made a mistake will suffice.

Actually, I didn't accuse you. I simply commented that there is more than one explanation for it (and it happens a lot). For all I knew, the capitalization could have been original with your source. After all the errors that you have obviously made in your OP, do you really think you should be giving advice about argumentation?

I don't believe I made an argument for MVs "read the same" here. Perhaps you'd like to show it to me?

I love you, brother Thumper. I mean you no ill will. I hope you will take this as a learning experience. I wish you well at PCC. BTW, what are you studying?

Pardon me, but I am still unclear as to what mistake I made, this is absolutely the last time I have three threads running at once. I just spent almost 3 hours working over a post on the Textual Criticism thread and my mind is running a bit slow.

The original list had all small letters if that is the mistake I made, I only checked the NIV references and since every one I checked was accurate, I assumed the rest were, if I made a mistake, I beg pardon.

The point I was attempting to make is that while context can determine the proper meaning of the word in most of these references, why is that alright to do in a MV and not in a KJV?

I was not attempting to personally accuse you of saying that "all versions read the same", it was more aimed at all the MV proponents that I tell me that in regards to this matter.

I bear no body on this board any ill will, you are all my brothers in Christ and I wish all of you the best of God's blessings, if I have given the opposite impression, forgive me. This is a matter I feel very strongly about and I can accidentally offend when no offense is meant.

I meant for my post over in the Pronoun Troubles thread to be my last one, but I realized I needed to wrap up my part in this thread as well, so let me re-iterate, I have placed my PCC email address in my profile, if anybody on here feels that they did not get a fair chance to respond to any of my posts, feel free to email me, and I will respond as fast as I can, classes permitting. IF my inbox fills up however, well...it may take a little longer. ;)

In response to your question, I was a junior Computer Information Systems major, but the Lord recently changed my direction and I am now a History major. Although I should still graduate either in time or maybe one semester late.

God Bless! :godisgood:

Thumper
 
Top