|
Register | Sign In |
|
QuickSearch
EvC Forum active members: 64 (9164 total) |
| |
ChatGPT | |
Total: 916,745 Year: 4,002/9,624 Month: 873/974 Week: 200/286 Day: 7/109 Hour: 3/0 |
Thread ▼ Details |
|
Thread Info
|
|
|
Author | Topic: Fulfilled Prophecy | |||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
i.e. it doesn't refer to a specific word, as Buzsaw claimed. It refers to a prefix to a word. yup, "and" (or in this case "but") is a vav-prefix. exciting, i know. one little letter.
Moreover the "and" translation" is at least as valid as the "but" whcih Buz relies on even though it doesn't really support his case. it's generally translated "and." unfortunately, prefixes aren't cataloged in concordances, so i can't give you statistics on that. so you'll have to trust me. it means "and."
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
Arach: 1:1? yes it is. the rest of the chapter, no. Make that 2:1. It was a typo error, Arach. ok, just checking.
I was responding to quotes of Jar from chapter 2 in which his liberal NIV translation has added the name Ninevah into the text though it is not in the Hebrew manuscripts from which the verse was translated. yes, i know. i had the hebrew in front of me when i asked jar what translation he was using. it's clear from the context who nahum is talking to (well, it's clear to everyone here whose name isn't "buzsaw" anyways). but inserting it explicitly when it is not in the original isn't exactly ethical.
2. According to my Hebrew/English Interlinear which supplies the nearest English equivalent to the Hebrew text, no, obviously it does not.
verse 8 begins with the significant little word "but as per the Hebrew word of that text. sorry buz, the hebrew says "and."
In order to understand at what point Ninevah is being honed in on, one must note that word, "but." Why? Because it implies that the chariots of Ninevah are likely not the same chariots described in verse one. you're hanging your point on a misreading of a vav-prefix? lol buz. lol.
Are you trying to convince the www that you are a more knowledgeable and accurate translator of Hebrew to English than the Hebrew scholar than JP Green, editor and translator of the Hebrew/English Interlinear which has gone through 12 editions? it's a vav-prefix, buz! this is elementary hebrew. bet-prefixes are "of." mem-prefixes are "from." vav-prefixes are "and." this isn't a matter of me convincing anyone of this. it's just another instance of you hanging some ridiculous misreading on forced vagueries and misrenderings of the text. yes, your interlinear text says "but." big deal, buz. it's commonly translated "but" when that particular translator wants to make a more abrupt transition. but the prefix means "and" and is simply a standard way of starting sentances in the bible. it starts the majority of sentances in the text, buz. that's how incredibly basic this point is. you wanna check a few translations of this? half the ones i have available leave off the "but" or "and." most of those have a "though" (which applies to the "but" later in the sentance).
Since the Hebrew language has relatively few words, perhaps either words are acceptable, depending on the context. yes, buz. depending on the context. infering context from a vav-prefix is entirely backwards.
At the time of restoration of Jacob's splendor, at the time of Israel's preparation, appearing like torches, made of steel (to be soon burned up) crashing in the broadways, et al?? I don't think so in these verses. are you really having this much trouble picture the charioteers of judah crashing throug the streets of nineveh, lighting everything in sight on fire? i can't tell if you have too much imagination or too little.
1. From my understanding of the post Babylonian Judah, it was nowhere near a restoration of the splendor Judah once had under David and Solomon, et al. read it again, buz. pre-babylon judah. dates BC count backwards. assyrian fell (as predicted by nahum) in 612 bc. 26 years LATER in 586 bc, judah was conquered by babylon. nahum is tlaking about the time between then -- he can't be talking about the solution to the babylonian captivity that hasn't happened yet, when the assyrian invasion is still going on. especially since all the text ever mentions is assyria. why is this so hard for you? Edited by arachnophilia, : No reason given.
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
Were those prophets historians as most of you prophecy skeptics appear to imply or were they prophets of future events which were to be fulfilled at some period after they were given? it's a fundamental misunderstanding of the prophets to think of them as "predictors of the future." they were religious leaders, and thinkers. they delivered messages and sermons to the people of judah and israel. they were the voice of god to the jewish people. most of what they said actually pertained to the present, and most of their predictions regarded near-future things. the coming babylonian exile, etc. often, their messages were thinly veiled rants or threats at foreign occupying powers, in an attempt to rally the nationalistic strength of their people. something that was, itself, entirely responsible for seeing the jewish people come back from babylonian captivity. without a prominent leader urging resistance and emphasizing hebrew identity, they would have been successfully integrated in the babylonian populace. ezekiel, for instance, didn't so much predict the return from exile as much as he actually made it happen. one of our earliest descriptions of a prophet is aaron. moses cannot speak to pharaoh, so god appoints aaron to speak for moses. god says that moses will be like a god to pharaoh, and aaron will be his prophet. so our earliest clear image of prophecy is of one man speaking for god. if it's not implied from that, deuteronomy spells out that moses is a prophet. joshua takes up his role -- joshua is a prophet too. did these mean predict the future? no, they spoke for god to israel, and lead israel through troubled times. that is what a prophet does. to think that "prophetic" means "predictive" is a product of another anachronism of colloquial usage. the hebrew word has no sense of predicting the future; only speaking.
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
So the use of tense indicates that 1:2-1:10 are not specific predictions - they are simply statements abouts God's power and what he does to His enemies. yes, exactly. they are nice simple verbs, which are hard to justify translating as anything other than present. the sense is definitally that they are general statement about god's power, from the context, and how the next argument follows from it: "don't f' with god." i'm just not entirely sure that every instance of present tense cannot be predictive, as style varies. for instance, see ezekiel 37, which predicts the restoration from babylonian exile (and spawned the famous "head bone connected to the neck bone" song). it's entirely in past tense, yet predicts a future event. the text describes a vision (which takes place in the past, of course) but the vision has symbolic meaning for the future (wrt ezekiel and co). the style demands past tense, yet it's still predictive prophecy. all i mean to say is that "style varies" and you should be able to tell from context. your analysis of nahum is spot on, and anyone reading it should be able to see that. it's fairly obvious. why buz doesn't get it, i don't know.
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
Is it vav at the center of a similar switcheroo in the Song of Songs? yes.
quote:
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
(I didn't check them all, so I can't say for sure that they all come from the vav-prefix. ) there's a fair chance that all of the "and"s are vav's. i'm not positive on the "but"s. there is a modern hebrew word that means "but," but i have yet to actually find it in the bible. the hebrew vav-prefix seems to just be a generic conjunction -- insisting on it meaning "but" and the using that "but" to imply a shift is somewhat contradictory to the purpose of the prefix, and really grasping at straws.
For what it's worth, in the Old Testament (KJV): "and" appears 40987 times in 18292 verses, "but" appears 2324 times in 2193 verses. so, about 94.6% of the time, at least. what is it with these distortionists that they take a word (or in this case, not even a word), and attempt to redefine it with an alternate translation that's used 3% of the time? if i had to gamble, i'd go with the 97%. wouldn't you?
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
How does one translate 'uhh' to a foreign tongue? our argentinian neighbors say "che...."
Can you think of any instance where 'uhh' might be substituted for vav? i don't think people write with "uhs" and other verbal pauses. it's an interesting idea, but it seems like a far more formal thing than that, and is definitally used to say "[this] AND [that]."
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
You appear to indicate that there's no other Hebrew prefix for "but." none that i am aware of. i knew there's a modern word for it, but it's taken me a little time to track down a good searchable concordance to verify that it is indeed used in biblical hebrew. those words would be:
keep in mind that these are just the most likely ones. there are a few other words that could acceptably be translated "but," but i i have listed them, imho, in order of their probability of usage, as i understand it. the first two are commonly used in modern english.
Since the Hebrew is a language of relatively few words, relatively few? they've got five common words up there for "but."
translators must often determine by context what English word most accurately depicts what the nearest English equivalent is to the manuscript message being translated. this is bs. of course there's some subtle variations in wording dependent upon translation and best matching equivalents and context. everyone knows that, i hope. but you are attempting to make the bible a vague and flexible document, which you can then bend to your will. your argument is circular -- "green thought the context was this, so he rendered this word this way, so that tells me the context is this." wow, buz. wow. i am amazed at this observation. no one else here can believe you are hanging this point on a single letter, which you are forcibly misreading.
Hence scholar/translator/interlinear editor Green apparantly sees the "but" as the most linguistically accurate rendering in one of his translations, but not another? this is really convincing, buz. you're forcing a reading that simply is not present in (incredibly) elementary grammar of this one singular letter attached to a proper name. had this actually been as important a point as you seem to think it is, nahum could easily have used one of the choices above that does mean a contradiction. at best, you have a maybe. you're straining at gnats.
"waw" (ancient) "vav" (modern) you say tomato, i say tomato. i guess that doesn't sound as good written.
Obviously in English "and" can depict a much different meaning than "but" such as in this case. if one wants to sell a contradictory conjunction, there are choices that actually represent this, and they are related to much different words. aval is related to the concept of mourning or lamenting. ak and aken come from negations of a positive. ulam comes from "perhaps." none of them are simple prefix connections that join one thing to another. in english "and" and "but" are used as similar conjunctions, but in hebrew they are not even close.
After all, the "but" implies separation whereas "and" implies conjunction. the vav-prefix is a conjunction, and implies joining things together. it's totally the opposite.
Green appears to lend support to my contention that the verses relative to Jacob's restoration is not directly revelant to the city of Ninevah. i don't think that's even the case. i think you are reading a sloppy translation, and i think your understanding of context and figures of speech in english is sloppy, BUT i think your interpretation is even sloppier. Edited by arachnophilia, : typo
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
When I study Hebrew terminology I am always amazed at how many words one can create by applying different vowel marks. As I understand it, these marks were first applied a thousand years after the Hebrew scripture was written (of which nothing original survives) Yes? kind of. the differences are generally either very subtle (different cases, tenses, etc) or dramatic (something like homonyms, in which i suspect it's just coincidence).
I have seen, in Strong's Concordance, as many as half a dozen supposedly distinct usages with identical primitive spelling. i am truly mystified at strong's concordance. it doesn't do what *i* would have done to catalog things at all. i've often seen one entry with multiple (distinct) meanings depending on context (homonyms), which i would have given separate entries. but then i run across multiple entries for the same word: just tonight, we were discussing genesis 18 in the chat, and why abraham addresses three people as one "lord." genesis 18:3 has an entry for "adonai" but genesis 19:2 has an entry for "adon" with the yud-possesive on it, rendering "my lords" with an s instead. they're both the same root word, with the same possesive. one or both are plural, but spelled exactly the same. why two entries for one word?
The fact of identical primitive spellings is often exploited by translators who can, if they like, put a different and sometimes equally plausible spin on a word by changing the vowel marks. do you have an example? i mean, a legitimate one, not buz.
I exaggerate the problem, of course, for the sake of argument but you know there's a fundamental problem when you have a thousand different Bible thumping organizations selling a thousand different versions of the One and Only "truth." ironically, most of them are fairly similar. Edited by arachnophilia, : No reason given.
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
hmm. i'm curious about conrete examples. i'll go looking...
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
That's what I said. The Hebrew language has relatively few words relative to English which I'm sure you're aware. buz. i didn't get out of the alef's. want me search the bet's? the gimmels?
You're trying your best to make a fool out of me. why would i need to try?
There are around 37000 words in Hebrew and nearly twice that in old English. There are many times that in modern English, well over a half million. the number of words in the english language, vs hebrew isn't exactly the point. you are attempting to distract from the fact that there are five better alternatives to the use of a vav-prefix to mean "but," if the emphasis is to be placed on contrast.
That there is no "but" prefix in Hebrew there are five words up there that serve the same function. if nahum had wished to make the kind of contrast you seem to think he did, he would have used one of those words, not the vav-prefix.
at least in the earlier editions to satisfy the context with the but prefix for whatever reason. not "whatever reason." i told you the reason. starting every second sentance with "and" gets downright boring. in hebrew, it has a nice ring to it, a kind of alliteration. in english, it's dull. translators generally change the vav-prefix conjunction at the beginning of sentances to make the text more interesting to read. i've explained to you what the hebrew means. i've explained the grammatical connotations. i've explained the logic of the translation. i refuse to believe that you simply don't understand this -- you want to continue to misrepresent the text in every detail to support your failed interpretations. and to continue to hang this point a single letter that at best is rendered your way SIX PERCENT of the time? no one is convinced, buz. especially since most of that "six percent" are probably those five words above.
There are many instances where English statements call for a but prefix, so if you don't have a Hebrew but prefix you may have a problem in which some improvision is needed. At least that's the way it appears. it appears that way because you simply know nothing about translation or the hebrew language. waht's more, this has to be on purpose -- i gave you example verses, and they word they use to mean "but." and guess what? when the authors of the bible needed to start a sentance with "but" they had words for it.
Anyhow, this thread is not suppose to be a lesson on Hebrew, nor a lesson on Nahum, so hopefully we can move on. no, we can't move on at all. it is completely evident from this discussion that you do not read or interpret in good faith. what can we possibly hope to discuss with you if you cannot read a single letter of the bible correctly? what kind of debate is it, if you refuse to accept logic, and that maybe someone here knows a little more about translation than you? you don't want to debate. you don't want to discuss. because debating and discussing might force you to acknowledge that you didn't know something, or that you were wrong about something. no, you want to preach. and it's painfully obvious to everyone here.
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
That's just not true. All of the Biblical books are not prophetic books as per the common meaning of the word "prophecy." History is not generally known as "prophecy." really, buz? then why are joshua, judges, samuel, and kings in the book of prophets? Nevi'im - Wikipedia
Prophecy, in a broad sense, is the prediction of future events. The etymology of the word is ultimately Greek, from pro- "before" plus the root of phanai "speak", i. e. "speaking before" or "foretelling", but prophecy often implies the involvement of supernatural phenomena, whether it is communication with a deity, the reading of magical signs, or astrology. It is also used as a general term for the revelation of divine will. that's great, but the prophets we're speaking of are hebrew, not greek. and in hebrew, "prophet" or ‘ navi comes from a word meaning, literally, "to bubble up," implying words rapidly coming from the mouths of the prophets. "prophet" means, literally, something like "spokesperson."
It took no more of a miracle to predict latter day events than the Babylonian exile. not the point. the point is that they talked about stuff that actually concerned their audiences. and yes, a small portion of that was end-times stuff. but most of it had to do with stuff that actually affected the lives of those that heard the prophets speak.
In Exodus 2:1 does not say that Aaron will be God's prophet. God knew how Pharoahs regarded miracle workers as gods so God said Moses would be regarded by Pharoah as a god and Aaron would be regarded by Pharoah as Moses's prophet. Get it? To Pharoah: Moses=god, Aaron=Moses's prophet. perhaps my pronouns and antecedants were unclear; that was precisely what i meant. the relationship we are given is: prophet:god::aaron:moses. if moses is like a god, aaron is like a prophet -- aaron speaks for moses. so a prophet is someone who speaks for god.
Aaron was no more of a prophet of God than Moses was a god, however. Aaron was designated by God to be the spokesman for Moses to tell God the message God gave to Moses. there's the word: "spokesman." aaron spoke for moses, like a prophet speaks for god. that's the biblical definition of a prophet. one who speaks for god.
I'm not saying this is a hard and fast rule, but as a rule of thumb so to speak, the prophets and prophetic books had much to do about future events as wikapedia bears out by definition. can you read?
quote: it's on the first sentance, and the definition. oh, look, it goes on:
quote: really, buz. really.
quote: are we done yet? Edited by arachnophilia, : typo
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
PaulK, you miss my point that the "but" separates whereas "and" conjuncts. good. vav is a conjunction that joins things. sorry buz, you lose. thank you for playing.
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
You continue to miss and obfuscate my point. it's not obfuscation simply because you fail to understand it.
1. Though there are Hebrew words for "but" there is no in-word prefix for "but." this tells me there is something greviously wrong with the logic of your argument. you seem to be working from two presuppositions: "the text has to use a prefix" and "the text means but." you are, essentially, putting the cart before the horse. we start the original, when we translate. not the translation -- the translation is the final result. and we certainly do not start with the interpretation. that comes after we know what the text says.
Since there is no Hebrew "but" prefix for the purpose of translation the word "but" must be added i gave you five examples of how the authors would emphasize difference with a "but" in the text. if they authors wanted to say "but" they would have used one of those words. there is no prefix for "but" -- why would it have to be a prefix, buz? because there's a vav-prefix in the text? that prefix means "and."
for whatever reason the translator had to use it. you are assuming a reason. i gave you another.
2. That the usage of the word but divides/separates is indicative that possibly translators who added the word "but" for the English language translation saw a division/separation as I do (abe: in the context.) so at best you have a "possible." great argument. clearly, your contextual reading if very flawed. i doubt that one simple word indicates that knowledgeable translators read as badly as you do.
3. None of the major translators of the English Bible used the "and" prefix in their translations and no less than five of them used either the word "but" let's look at why, shall we?
quote: "the queen is carried away, but the city does nothing." contrary to your logic, "but" (in english) is a conjunction, and it connects things. this "but" connects it to the earlier sentance. nineveh does nothing while her queen is carried away. it does not point to a major transition in the text, just a contrast in the sentance. because that contrast is implied in the hebrew, "but" is an acceptable english translation. but it really says "and." context does not agree with you here.
or the word "though," though having the same connotation as "but." "though" is not the same word as "but." it changes around the dependent and independent clause.
quote: there's the contrast -- nineveh used to be calm, now it is not. neither of these plausible interpretations of the grammar support your implausible position that the preceeding verses are not about nineveh. in fact, your chosen translation, "but," actually contradicts your view, because it indicates that the prior sentance has to be about nineveh.
Arach, it's fine for you to disagree with Buz but though your viewpoint may be a viable and debatable one, Buz is not a fool, as per your implications. this is reading comprenehsion 101, buz. it's not "my viewpoint." it's what the text says. Edited by arachnophilia, : typos
|
|||||||||||||||||||||||
arachnophilia Member (Idle past 1369 days) Posts: 9069 From: god's waiting room Joined: |
3. You do not know any more than I do, in fact, buz, i do.
|
|
|
Do Nothing Button
Copyright 2001-2023 by EvC Forum, All Rights Reserved
Version 4.2
Innovative software from Qwixotic © 2024