Threads from Henry's Web

Tag: Biblical Languages

  • The Comprehensive Aramaic Lexicon Site

    (Edited July 10, 2018 to update link.)

    I discovered this site some time ago and have used the Comprehensive Aramaic Lexicon site it as a reference before, but P. J. Williams on Evangelical Textual Criticism reminded me today that it’s nice to link to and recommend resources such as this.

    You have to be ready to do a bit of work to find what you want but there are some wonderful resources, including lexical information and texts linked to a lexical breakdown.  For someone like me, who uses Aramaic occasionally, and thus lacks some of the best library materials, this site is extremely helpful.

    Spend a little bit of time scouting around and looking for the options.  The information on how to use it is there; it’s just not always obvious.

  • Is it Necessary to Know the Biblical Languages?

    I previously answered this question for myself here, but there’s a good and gracious answer today from Brian Fulthorp.

    I would repeatedly emphasize that there are many advantages to knowing Biblical languages.  There are some areas and methods of study that really are closed to you if you don’t know the languages.  Having said that, we have such wonderful tools for study in English that you do have many ways in which you can study seriously without learning the source languages.

  • Mounce on What the Greek Says

    Bill Mounce, author of the wonderful Basics of Biblical Greek, which I have used in teaching, has a post at Koinonia titled <em>Matthew 7:26-Is a moros a moron</em>, with the very proper answer–NO!

    There are two things I’d like to call attention to in this post.  The first is an excellent illustration of the false allure of etymology or seeking cognates.  This is more for the serious Hebrew student, but while sometimes one must look for ideas for a “hapax legomenon” in cognate language, one should be aware that the cognate provides ideas, not proof of a new meaning.  Context provides the final judgement, and if a word occurs once, that means that humility is called for regarding that final judgment.

    The second is the sprinkling of “what the Greek says” (or Hebrew) into sermons, especially by those who don’t really know, which is the vast majority of times I’ve heard this used.

    Mounce says:

    I know it is tempting to show a little Greek knowledge and try to create a helpful word picture, but unless you are absolutely confident that your Greek is absolutely right, I strongly urge you not to display your Greek knowledge.

    Which brings me to the general point. I encourage my students to never say, “In the Greek ….” Why would you do that? To impress the audience with your academic acumen? To convince them that you are right when you can’t prove your point with biblical logic? Perhaps I am being a little harsh, but I am sensitive to pastors claiming to be an authority and putting themselves up on a pedestal. That’s not where servants belong.

    Just so.  I have rarely been privileged to quote two paragraphs from a blog post with which I agree more completely.

    PS:  You’ll have to read Mounce’s whole post to discover more about morons!

  • Added to my Blogroll

    I’m adding Bob’s Log to the Bible study blogs section of my blogroll. Bob deals with a great deal of Hebrew poetry, especially the Psalms, and is very interested in structure. I think it will be valuable to look over his shoulder as he works on this interesting material.

  • Word Study Dangers: Overview

    [This is the first in a short series on word studies, especially the type of study done using an English concordance keyed to the Biblical languages, such as Strong’s Concordance.]

    A few years back in the pre-blog days when most online discussions took place on various forums, someone proposed to me a new translation and interpretation of a particular verse. I don’t even recall the verse any more. What I do recall was the process of figuring out what the gentleman had done in order to produce the words he presented to me. That text was totally unlike any English translation of that verse that I knew of, and completely impossible by my reading of the Hebrew. He said he had worked on the translation using Strong’s, so I knew my starting point.

    Slowly I worked my way back through Strong’s and discovered that he had simply looked through the possible translations for each word, and then selected one that he wanted to use. He had combined those English words in the fashion of one putting together a difficult jigsaw puzzle, and then had dealt with minor issues such as verb tenses and the syntax according to the sense that he was looking for. As a result, the verse consisted of a series of words, correct in the sense that they came from a Hebrew/English dictionary, but none of which were actually possible translations in that particular context.

    He was extremely disappointed when I was not enthusiastic about his creative efforts. Surely I was not dogmatic enough to simply reject his translation out of hand! After all, it came from Strong’s, surely a standard authority on the meaning of the Hebrew text, and one used by many, many Christians! And yet I was just that dogmatic.

    Now this is not a series on the inadequacies of Strong’s as a Biblical languages resource, though it does have many such inadequacies. It provides glosses, rather than definitions, and those glosses are taken from out of date sources. Discovering the meaning of precise forms varies from extremely difficult to impossible. Nobody who was actually skilled with the languages would make use of it as a serious resource for knowledge of the source languages. There are other English concordances, keyed to other Bible versions, that are based on more accurate sources, yet they still suffer from the other inadequacies.

    The larger problem, however, is the people who try to use these concordances as a resource to study Bible words. There are things you can learn making use of such resources, but finding more accurate definitions of Bible words than those found in standard language resources is not one of those things. A student who does not understand the source languages would do better with one of the many Bible dictionaries or word books that are available.

    The problem is in the nature of word studies. Similar issues come up in discussion when one tries to define a word. There are two extremes in discussing English words. On the one hand we have those who believe words mean whatever they want them to, and on the other we have the dictionary addicts. The first group doesn’t care to use standard definitions and creates a great deal of confusion for obvious reasons. The second group looks in the dictionary, and if a word is not being used according to the particular definition (often the first one presented) found in their particular dictionary, they are annoyed. The dictionary rules.

    There is a subset of this group who are fascinated by older dictionaries. “I want a dictionary that comes from a time when words had meaning and weren’t subject to the whim of the uneducated masses,” they say. That there never was such a golden age of language doesn’t other them at all. The word should mean what their older dictionary says it means, and anyone who disagrees is just the product of a “dumbed down” educational system.

    But dictionaries are merely reporters. The writers of dictionaries do not, for the most part, create meaning, except as any other writer does. People create meaning when they make use of words to communicate. A single word doesn’t have only one meaning; generally it has many. Its meaning doesn’t generally remain unchanged over time. What lexicographers (the writers of dictionaries) do, is survey the usage of words over a wide body of literature and formulate and report appropriate definitions. Multiple definitions per word are required, because words get used in many different ways with different meanings. There are scholarly meanings, technical meanings, popular meanings, regional meanings, and so forth.

    For example, when I talk about computers I use “CPU” (central processing unit) to mean the little chip on the motherboard that does the processing. I got used to that usage years ago. Frequently these days someone will call me for service on a computer, and they will ask, “Should I just bring my CPU or do you need the monitor and keyboard as well?” This usage bugs me, even though I truly believe what I said in the last paragraph. They’re not wrong; they’re just using a quite common popular usage. Most of my readers probably find CPU used in that sense to be more appropriate than its use to refer to the chip. In terms of the way meaning develops, CPU is an acronym, yet many who use it would not know what the letters stand for. It has become a “word.” Similarly “car” can mean many things, from the part of the elevator that one actually rides in, to the car on a train, to the automobile that one drives. This is generally true of words. One determines from the context just what definition is appropriate. Our minds are wonderfully adept at figuring this out.

    Words in Hebrew and Greek are no different. The reason a concordance like Strong’s has quite a number of glosses (words of phrases provided as possible translations of a particular Greek or Hebrew word) is that those Greek and Hebrew words have many potential meanings in different contexts. You can’t simply take the list of meanings, choose one that you’d like to read in this location, and run with it. There are many factors that go into the particular choice of an English word, factors that the mind of a native speaker would process naturally and quickly.

    Some of these factors are:

    • The immediate context
      For example, you can tell what definition I’m using for “car” easily in each of the following sentences. I drove my car to work. and The locomotive was pulling 25 cars..
    • The particular form of the word
      Both Greek and Hebrew are inflected, and sometimes such inflection will result in a completely different meaning for the word. The lexical form (the one you find at the head of the dictionary entry) will be the same, but the meaning will be substantially different. If you don’t know about these different forms, you may well come up with an impossible answer.
    • The type of literature
      Words are used differently in different types of literature, and you have to be conscious of that effect. For example, priestly texts will use words about sacrifices in a much more technical way than general historical texts.
    • Syntax
      The structure of the sentence may indicate a difference in the meaning of the word. In Greek, this is a very important thing to remember about prepositions. One common mistake made by those who do not know Greek is to list the possible definitions of a preposition and then choose the one best suited to their desired translation, without considering the form of the preposition’s object. That doesn’t work in Greek!
    • Time period, particularly in Hebrew
      Meaning can vary based on when a text was written. This is generally important in translating Hebrew, though not so much for New Testament Greek because the New Testament was written over such a short period of time.
    • Peculiarities of usage by the particular author
      Just as modern writers and speakers may use words in unexpected ways, the Bible writers could do likewise.

    In my next entry I’m going to go over the process of doing a good word study, and examine the level of knowledge of the Biblical languages required to handle certain information.

  • Building Your Knowledge of Greek Grammar

    When I took second year Greek, the grammar to use in getting beyond basic introductory material was Dana and Mantey’s Manual Grammar of the Greek New Testament which is very hard to get. But as a replacement, and also a considerable improvement, we now have Daniel B. Wallace’s Greek Grammar Beyond the Basics.

    For those who are just trying to build their knowledge of Greek a bit, it is probably not best to try to read or study through a grammar. There can be a benefit in doing so, and I have read Wallace’s grammar through, but it can be a daunting task unless you already read Greek fairly well and also truly like studying grammar. But you don’t have to take such a boring approach! One of the best features of this and all other New Testament reference grammars is the scripture index.

    You can get started building your grammar knowledge by looking up the verses that you read in the index. This will mean that some days you will have nothing to look up, while on other days you will have several verses. Once you look up the specific page on which the verse is referenced be sure to go back and read the entire section. Don’t be put off if you don’t follow the whole thing. Over time you’ll get to understand the material better.

  • Biblical Languages: Balancing Fast Reading and Slow Study

    Continuing my suggestions for maintaining Biblical languages skills, I want to discuss briefly the balance between fast reading and the more serious, detailed, grammatical study.

    Most students who make an effort to maintain their Biblical languages skill–and unfortunately small percentage in my experience–set out on each passage of scripture to study the text as though preparing to face the professor’s interrogation. Some of you may have had relaxed Greek or Hebrew teachers. I had one in undergraduate Greek and one who covered both Hebrew and Aramaic when I was in graduate school who had high expectations of what you should know about the text. I remember quite clearly the day in Aramaic reading when I had correctly parsed a verb form, and then the professor asked me what it would be in a completely different stem, person, and number.

    If you’ve had that type of learning experience with any of the Biblical languages, you may have gotten into the habit of lingering over each and every word until you hope you know every detail. There is a place for that, and when I’m teaching, I will sometimes ask questions like that especially of students who tend to neglect details. But let me point out that you didn’t learn English that way, assuming it’s your native tongue. Instead, you were exposed to a great deal of the language and absorbed quite a bit of vocabulary and structure before you studied it more formally.

    Most people will face discouragement in their study of the Biblical languages if they proceed at the slow pace required to study out every form in detail. That is why I recommend dividing your time between some serious study, and a program of faster reading. Faster reading will require good tools, such as Bible software of various types, reader’s lexicons (Greek or Hebrew), analytical lexicons (Greek and Hebrew). These are not tools that most Biblical languages teachers will encourage you to use for class, but they will help you cover more ground and expose yourself to more of the language. Accompany these with good English versions, and your reading speed will improve.

    Each person will have a different balance between these two parts of study, depending on your own personality and your goals. If you eventually want to be able to debate serious grammatical issues, you need to lean more and more to serious, detailed study. If you’d like to read devotionally, spend more time building your own speed.

  • Maintaining and Improving Biblical Languages Skills

    This post is for a rather limited subset of what (I hope) my audience is here–those who have some knowledge of Biblical Greek, Hebrew, or both. Tragically, many seminary students learn a little bit of Greek or Hebrew but not enough to really put to use, and then they spend the rest of the career (or at least the next couple of weeks) forgetting what they learned. There are two common results–either a pastor/teacher who presents inaccurate information about Biblical languages in teaching, or one who simply leaves out Biblical languages in study altogether. In the former case we have the tragedy of misinformation confidently presented by an authority figure. In the latter, we have the waste of seminary and seminarian time and money.

    I’m going to post a few short entries here about maintaing and improving your Biblical languages skills. Most of these suggestions are equally applicable to both Hebrew and Greek, or even to Aramaic if you have it. Specific tools, of course, will generally apply to one or the other.

    My first general suggestion is simply that you continue to read material in the Biblical language that you studied. There are several things that tend to prevent students from doing this. You may be overwhelmed and disgusted, and never want to see the material again. You may feel that you can’t really read, so what’s the use in trying. You may decide to try, but set excessively ambitious goals.

    So at the first level, let me suggest just making the opportunity to see some Greek several times a week. (I’m going to use “Greek” here for convenience, but this applies equally well to Hebrew.) There are a number of tools to help you do this. Bible software these days, from e-Sword to the source language texts from the NeXt Bible or Logos Bible Software include tools to take you quickly to the lexical entry on various Greek words. Your teacher probably told you not to do this while you were initially learning, but you’re out of class now, and the problem is maintaining and building. These tools allow you to see more Greek text.

    Then there’s the ultimate crib sheet–a good Bible version. I normally recommend dynamic equivalence translations, but for this purpose you will want a literal translation like the ESV, NRSV, or NASB. These are again available in the various software packages I’ve mentioned.

    If you don’t have the Bible software, take your Greek New Testament and get the Reader’s Greek-English Lexicon of the New Testament. Again, this is a tool you wouldn’t be encouraged to use during first year Greek, but you’re away from the seminary now and trying to maintain your Greek.

    There are some other tools that can help, including grammars, but I’m going to discuss them in a later post. The idea here is that no matter how badly your Greek has faded, you can work your way through a passage. (You will, of course, need to refresh the alphabet.) Don’t be afraid even to just accept the translation in whatever English version you’re using if you don’t understand the material from the text. In later posts I’ll give you suggestions for getting beyond this, but for now you just want to dip your toes in the water.

    At this point don’t get too ambitious. If you can only manage one verse per day, do that. You may have heard of folks who read a chapter each of Greek and Hebrew every day. I read three or four of each besides whatever I read for current research projects. But I’ve been doing this for quite a few years, and I left seminary with five years of Greek and four of Hebrew to which I’ve now added nearly 25 years of reading on my own. Don’t get tangled up with grand goals. Be content to read a verse at a time, and do so several times per week.

    In later posts I’ll discuss solving grammatical issues, reference grammars, building vocabulary, and getting the immediate blessing for your devotional life and your teaching.