See for more themes.
| Q6: Scripture Secrets : Translation of words So if you're a beginner to Scripture, the KJV translation is a good start and gives you the milk you need to learn about Jesus. Ever since the "tower of mixing (Babel)", 201 years after the Great Flood, God mixed the sounds of language for a reason, to stop the flow of evil, and to preserve the truth. How does mixing preserve truth you say? Well if a book contained "truth in easily found places" would not an evil person tamper with it? However many Jewish scribes were pious and considered the letters holy, God has seen to it that the transcription process has been very, very accurate. So readers can feel confident they have all the original words carefully preserved. See UTube videos, "the Dead Sea Scrolls. Dr Patton". Now of course doubters will doubt, and mockers mock, so do a few errors here and there really matter? What are we looking for ? Words or Words Personifed? Remember on the previous webpage, we really are looking for the "imrah" or the "Words-personified", the message of Jesus hidden in the words, and a few errors in letters and words do not destroy the message of Jesus hidden there; this we must find. But if you're not really wanting to find Jesus, there is always room for doubting. If you listen to Utube videos of translators they often say this about the translation process:- Bill Mounce was a translator on the NIV team, and says in his UTube video:- Am I going to err on the side of words or meaning? (1.33 minutes) Author: Bill's first assumption is translation begins with words. But actually translation should begin with letters. In Ancient Hebrew, meanings come from letters, not words per se'. Bill Mounce has not even considered this idea in his translation techniques. Do I follow Greek or Hebrew structure, or do I convey the meaning? (2.35) Author: show Hebrew for both OT and NT Here gives the example "Romans 16:16 Salute one another with an holy kiss". where do we go with meaning? Do we go with words, or work a little hard and get the meaning of the passage? (4.49 minutes) Author: show Hebrew words, and add footnote to explain meaning of "idioms" Than he gives another example: Romans 6:15 What then? shall we sin, because we are not under the law, but under grace? God forbid. Here KJV makes the Greek terms into a strong negative for English, God forbid. This is an example of conveying meaning. Rather than words. (6.27 minutes) Author: show Hebrew words, and add footnote to explain meaning "God forbid" as KJV used, and what Hebrew used. Personally, the Author would like to see an entire Bible; in Hebrew, both OT and NT, with the Ancient Hebrew pictograph s above each word (the suffix or prefix shown using a -dash-), and each word written consistently all the time for every Hebrew word. Where there are problems, write footnotes.., and be honest. Keep the human away from the Hebrew. Also in choosing the English words for each Hebrew word, follow Ancient Hebrew rules. Present the Hebrew verses as poetry, with structured lines for seeing the poetry. Again use footnotes if things are hard to read. Let's begin with a good translator, Jeff Benner, showing Genesis 1:1 He shows the Hebrew on top, right to left, on the left the English meanings for every Hebrew word with prefixs and suffixs with ~ symbols ~ , and on the right the English translation. It's a good mechanical translation, faithful to the Hebrew words, but does not show Ancient Hebrew pictographs. Jeff Benner uses modern Hebrew here, rather than Ancient Hebrew, to gain popularity from scholars. The Author is not sure of the prefix or suffix letters used, as my child like understanding of Hebrew is poor, so here is a humble attempt in showing Jeff's work in Ancient Hebrew:- Let's read what the pictographs tell us. You can't do this with modern Hebrew, or modern English, as letters make no sense, but they do in Ancient Hebrew. Such an assumption completely changes our approach to language. If we approach the "one lip" GOD gave mankind in the beginning, shouldn't we find pictographs preserve something of the original sounds? "(The) home head strong presses actively towards an important mark, (the) home head "strongs", (from the) Strong Authority secured (by our) Father flowing, strongly towards an important mark, (the) pressed flow, active flows, strongly towards as important mark, (the) strong Head travels." Notice the "home head strongs" is written as a verb. In Hebrew we assume the "bull's head letter" means "strong" as a noun or completed action, but sometimes the verb or incompleted action is used, as in the Hebrew word "BaRA". The pictographs in the Hebrew word "earth" tells us the "Strong Head travels" meaning the "earth" or "large land masses" move, relative to where GOD was during Creation. The Author would translate this passage as: Gen 1:1 "In the beginning the Divine Family Power engineered the heavens and the earth. Notice this translation is not following Hebrew flow, but an English flow. The Hebrew word "elohiym" means "Divine Family Power". The Hebrew word "bara" means to "engineer". (1) Study of create or engineer or fill Sometimes the Hebrew word "elohiym" is written in a plural context: Ge 20:13 And it came to pass, when God caused me to wander from my father's house, (KJV) Ge 20:13 And it came to pass, when the God's caused me to wander from my father's house, (Ancient Hebrew) Ge 20:13 And it came to pass, when "the Divine Family Powers" caused me to wander from my father's house, (Author translation) A devout Jew known as Nehemia Gordon agrees that in this verse "elohiym" is a plural in this context, but refuses to acknowledge the rare cases such context means. Jews are not allowed to read the NT about Jesus as messiah, and so do not see the term "elohiym" defined as "family" in Ephesians 3:15,16. Scholars twist and fight over words for translation, because it doesn't fit with their human world view and their human opinions of human religion. Gordon invents words like "majestic plurals" and "numerical plurals" for "elohiym" so he can justify what "Translation" he can use f or different contexts of "elohiym", in other words he sees "elohiym" as a "polysemous word". Polysemy is a human word invented to make any word humans choose, have multiple meanings in different contexts. The Author notes that sentences can suggest different nuances from words. These slight differences in meanings really come from our desire for details. Why can't we accept that the meaning of words as a broad action? Why do we have to invent countless smaller meanings, when a broad meaning is so much easier? This is what Hebrew is about, and it's really an attack on GOD who inspired originally a Semitic language with broad meanings. For example consider this Hebrew word:- Ge 2:22 And the rib, which the LORD God had taken from man, made he a woman, and brought her unto the man. Ge 2:24 Therefore shall a man leave his father and his mother, and shall cleave unto his wife: and they shall be one flesh. The Hebrew word "ishshah" means "woman" for all hundreds of contexts, but the KJV changes the meaning slightly if the woman is a married woman. Does this make "ishshah" on its own polysemous? No. Thus, translate the word always as "woman". Consider the meaning of "bara" or "B-RA":- The Author shows readers Jeff Benner's lexicon dictionary for 1043, showing all Hebrew words related to "bara". If you look at the Ancient Hebrew pictograph level, where the original sounds were sounded, the meaning should come from here. Genesis 1:1 begins with the "home head" strongly presses actively towards as important mark. In our own culture, we say the "head of the home" is our dad.But we are told in the NT that Jesus created the heavens and the earth. Eph 3:9 ..(In) the beginning of the world hath been hid in God, who created all things by Jesus Christ: (KJV) So from a Hebrew viewpoint, the "home head" is Jesus. So back to our translation: Genesis 1:1 "Jesus strongly presses towards as important mark, the strong head strongs..." or Genesis 1:1 "Jesus strongly presses towards as important mark, Jesus strongs..." Now we have a problem with the Hebrew word "bara", which Jeff Benner "translates" as fatten or fill. The Ancient Hebrew pictographs tells us the meaning is the "home head strongs". Jeff Benner is a great translator, but often the Author does not agree with his translation, even though his influence is good. Notice the context of "create" here:- Jos 17:15 And Joshua answered them, If thou be a great people, then get thee up to the wood (country), and cut down for thyself... Jos 17:18 But the mountain shall be thine; for it is a wood, and thou shalt cut it down: and the outgoings of it shall be thine: Ps 51:10 Create in me a clean heart, O God; and renew a right spirit within me. And a related Hebrew word: Jg 3:17 And he brought the present unto Eglon king of Moab: and Eglon was a very fat man. So Jeff Benner believes as I do that words in any language (before mixing mixes the languages) have a single basic meaning for the word, translates the sentences as: Jos 17:15 go up into the forest and "fatten" it for thyself.... Jos 17:18 But the mountain shall be thine; for it is a wood, and thou shalt fatten it: Ps 51:10 Fatten in me a clean heart, O God... Jg 3:17 And he brought the present unto Eglon king of Moab: and Eglon was a fattened man. The Author also believe s words in any language (before mixing mixes the meanings) have a single basic meaning regardless of it's context. The lowest broadest meaning for "bara""the home head strongs" is the concept of "engineering". The Hebrews uses the strong bull or the strong ox in a "stronging function" to plough the fields, they designed and set up technology to use the strength of the ox, thus the verb "stronging" is the picture of "strong engineering".When body cells have excess of material they engineer that material into other material, and hence we get "Fat", the Author would add a footnote to explain this. The Author would translate the sentences as: Jos 17:15 And Joshua answered them, If thou be a great people, then get thee up to the wood (country), and engineer it for thyself... Jos 17:18 But the mountain shall be thine; for it is a wood, and thou shalt engineer it: and the outgoings of it shall be thine: Ps 51:10 Engineer in me a clean heart, O God... Jg 3:17 And he brought the present unto Eglon king of Moab: and Eglon was a biologically-engineered "as a fat" man. Notice the Author is getting very close to the theme of "bara" for all contexts. How does the Author know this? Because all the contexts make sense, even the related words. Now Jeff Benner rearranges the Hebrew flow for English flow, making a NOUN-VERB-NOUN sentence. But this sentence in Genesis 1:1 has the NOUN already embedded in the prefix with the word summit or beginning. So if we read the Hebrew flow as it is, this is a NOUN-VERB; NOUN, NOUN, NOUN. If we look at the "home head" as a picture of Jesus, and the word "elohiym" as a picture of "family", the Hebrew is saying a member within the family is engineering. However if scholars who translate are not aware of the Ancient Hebrew pictographs they would never see this connection, and if they never read the definition of "elohiym" as "family" from Ephesians 3:15,16, they would never understand that Hebrew word; thus "their mixing would mix" their translation. So let's translate Genesis 1:1 "Jesus (from) the beginning, engineered (from) Divine Family Power, the heavens and the earth". ( Ancient Hebrew) or if you want an Ancient Pictograph reading: "The Home-Head (Jesus) strongly presses actively towards an important mark, (the) home head strongs, (the) strong authority secured (by the) Father flowing; strongly towards an important mark, (the) pressed flow active flows, strongly towards and important mark, the strong head travels." Readers might find reading this rather strange. It is like comparing lower level language with higher level language. At the pictograph level there are no words or groupings of meanings into a concept. Using words we can group themes into more complex meanings. But the cost of making things more complex (using words), makes things more difficult to translate. When a programmer writes a program, he uses a high level of language because it makes writing complex instructions easier and faster. A computer reads code only at a lower level of language, and this process is very long, tedious and boring to humans reading the code, but this is how computers read human instructions. The Ancient Hebrew pictographs is much the same idea, and why using it would be difficult for readers reading sentences at that level. If you want a taste of low level language, try reading the DNA language GOD wrote there regarding the instructions for living, using only four letters of code. Science has yet to read other DNA code telling the cells where to build, when to stop, and so forth. Science hasn't even began to read all the DNA code GOD wrote there. For those who might not know, our computers read only two letter code in their language. English today, is a langua ge using 26 letters. Translation is similar to programming. In olden times you could never get Microsoft languages to understand Macintosh languages, but now you can thanks to low level languages like Unix. A programmer writes a message for a computer to understand. There are two kinds of errors in a language created before hand by some Designer, that other programmers use during communication:- The most deadly error is "syntax error". This is where the person makes a fatal flaw in writing a language that the other person can't understand at all. Common examples of "syntax errors" are spelling mistakes, grammar mistakes or adding or removing special words that are required. The most confusing mistakes of all is the "logic errors". The communication message works but it is confusing because the message is not the right kind of message. This is why most Bible translations make fuzzy communication of messages. They not consistent with word meanings, so they translate what they think the word is saying. We live in a world of mixing and so things get mixed up. So what do we do?We need some advice from other scholars other than Bill Mounce. Let's ask our Hebrew English translator for help with translation. Next we look at advice concerning translation. |
Created by Rob Thompson. Hosted since 10/01/2012. Visitors HOSTED by Prologic, my Son. A thin website.
Translators did not know about Ancient Hebrew and so translated as best they could using their precepts of men and traditions they learned about language.
The dead sea scrolls tell us this story, that the letters of Scripture remain as pure as the very first time they were written thousands of years ago. 
Even the Greek translation of the latter rain teachings of Jesus is accurately preserved as shown in fragments from AD 50 in the 'Dead Sea scroll' caves. 
But the translation process is another story. To make truth certain to remain in Scripture, God hids it so evil men can't tamper or destroy it. So the truth is there, mixed with other things, but you have to go looking for it. Or you trust men to do the hard work for you?
