D
DOShea
Guest
Do you see the leap of logic you are trying to make? You are taking “inerrant” to mean complete and total accuracy in ALL things; scientific, historic, grammar, sentence structure, punctuation, and whatever else you want to throw in. The CC does not agree with that as a definition of “inerrant.” It does not claim ANY inerrant quality as far as historical accuracy, scientific information, etc. ONLY that God’s revelation to us for His plan of our salvation IS inerrantly transmitted.Strongly disagree! If the Scriptures contain even a single, provable error, how can they be trusted as reliable on ANY topic, especially salvation?
You’re partially right. I’m saying that there is no need for the Holy Spirit to protect against bad spelling if it doesn’t impact the transmission of God’s message to us. In any aspect of life, we can get important information in written form - spelled badly - and it doesn’t stop us from gleaning the important information in the document. Likewise with a document that has the wrong nation attributed to a specific King. If that isn’t important in terms of the message, there is no need to protect against it. The Church isn’t trying to use the document to teach history with, so it isn’t important. You don’t seem to want to accept that truth, but instead you are trying to force fit an “all-or-nothing” standard on it when the Church itself isn’t. That makes it a doctrine of you, not a doctrine of the Church.Sounds like you’re saying that God couldn’t (or wouldn’t) preserve His written Word from outright corruptions (which, it seems, you are at least “hinting” is what happened with Judith), and that the Church doesn’t care about historical accuracy or truth because it’s not using Judith as a history book.
Yes, that’s exactly what I’m saying. IF I was using it as a history text, you’d be right, it would be defective. But if I don’t use it for that purpose, what difference does that historical inaccuracy make? You are mistaking “protected from error” with “100% perfection in accuracy.” They are two different terms, and I’ve already addressed what the protection from error is concerned with.The problem is, the book uses names, dates and places that CAN be historically checked and PROVEN to be FALSE (even when compared with other Scripture)! Are you suggesting that it’s OK to have a contradiction in the Scriptures as long as it’s historical?
I’m not saying they are a colloquialism; I’m saying colloquial terms are but ONE example of how a later reviewer might miss the intent of the earlier writer. Maybe there was a purpose for intentionally writing this wrong historical fact, I don’t know. All I’m saying is that in some cases where people view what appears to be an error or contradiction, they misunderstand the writer’s intent. Sometimes recognizing other factors helps put these “errors” into perspective. Case in point:How are the historical errors in Judith “a colloquialism”? How can they seriously be considered anything other than what they are - gross historical ERRORS?
Pro 26:4 Answer not a fool according to his folly, Lest thou also be like unto him.
Pro 26:5 Answer a fool according to his folly, Lest he be wise in his own conceit.
These appear to be a contradiction, by the same author, one sentence apart. But they are only a contradiction if you fail to consider they might be separate pieces of good advice given to different people in different circumstances, not both at the same time. Only if you insist on them being presented simultaneously do they conflict.
Another gross assumption on your part. Your premise is that IF God can protect scripture from error, he must therefore protect it from ANY kind of error. Please explain why God is pinned to that requirement of yours?While it is true that God used many people over a long space of time to put His Words into writing, God is the author of Scripture, and God knows history, and He knows what we know. Seems like you’re suggesting God picked someone that didn’t know history (which seems very strange, considering how well the Jews know their history), and/or was unable to convey the correct words to the human writer. Bottom line - either Judith is not God-breathed Scripture, or God didn’t (or couldn’t) preserve it from gross, historical errors.
Have you ever been in a room where someone is talking on the phone and you needed to get a certain piece of information to the person on the other end? You might say, “Oh, that’s Joe… well tell him we moved the fishing trip to the 17th instead of the weekend of the 24th.” You would obviously be very concerned with the accuracy of that information. But what if they said into the phone, “Joe… the bowling trip has changed from the weekend of the 24th to the 17th,” and you heard Joe say, “Oh, okay, tell him I’ll be there.”
Now Joe knows there is a fishing trip planned, not a bowling trip. He was able to grasp the meaning of what was conveyed even though, on it’s face, it was factually erroneous information transmitted. He understood the information you intended to convey. By your imposed standards, even though Joe got the drift, you would need to re-interject your message and correct the facts, even though Joe might say, “Yeah, I already figured that out.”
You’re assertion is that without that extra corrective step, Joe would be down at the bowling alley on the 17th instead of down at the lake. I content it is quite possible for Joe to get the message you intended and leave his house with his pole and tackle box on the 17th without that extra “100 percent accurate in all things” protection.