Threads from Henry's Web

Tag: linguistics

  • Link: Linguistics and Gospel Origins

    Dave Black had some interesting notes on this subject today, which I posted to The Jesus Paradigm. There is a constant debate on what is “correct” usage. We have this with regard to modern usage. I’ll have authors cite some manual against their editor, usually on optional items.

    So why do we expect all usage to be equal in Koine Greek?

    Here’s Dave’s money quote, I think:

    Lately it’s become clear to me that the question concerning correctness and incorrectness in language is not so much a linguistic one but a sociolinguistic one. In other words, it is people who determine what is correct and incorrect in language, not textbooks. In a sense, then, if everybody says “It’s me,” then this construction is correct. 

  • How People Mess Up Interpretation

    How People Mess Up Interpretation

    No, this is not a post about the crazy ways people interpret the Bible. It’s about the way in which people make precision difficult in communication. Am I thinking about biblical interpretation? Of course I am. If you have to guess what I’m thinking about and I don’t give you a clue, “biblical interpretation” is a good bet.

    When I teach Greek or Hebrew, and as I’ve mentioned, this is to people by ones and twos, not in seminary classes, I try to emphasize basic linguistics. How does language work in day to day usage. I can illustrate what I mean by people messing up interpretation using a one line rule I give my Greek or Hebrew students: People are lazy. This rule applies, for example, to the reason why sounds tend to drop out of common phrases. “Good day” becomes “g’day,” an expression that may be more commonly used in Australia. (I say this so that I can get in a bit of a pet peeve. Check this sort of stereotypical thing out if you can. In this case, I find “g’day” in an article titled Outrageous Aussie Stereotypes Debunked. Not promising!)

    But my “people are lazy” rule has many problems (or exceptions, if you wish), which also illustrates one of the problems of language. People are diverse. What I think is easy to pronounce someone else may find next to impossible. I remember vividly trying to learn to pronounce a few Hungarian words while driving with my translator. She would pronounce the word and I would imitate. It always went downhill from there. In Hungarian actual vowel length, i.e. the length of time a vowel sound is sustained in speech, is phonemic (i.e., it impacts the meaning). In English, this is not the case. I was taught long and short vowels, but they were not sustained for different periods of time, but were actually different sounds. (That’s a very loose way to explain it! See? I mess up interpretation too by being lazy.) For me, properly judging the length to sustain a vowel sound was next to impossible. For her, it was second nature.

    So another rule: Things you have become accustomed to doing will seem easy. To you.

    People just don’t follow one set of rules. We may have learned in English class that a paragraph consists of a thesis sentence, followed by three explanatory sentences, and ended with a conclusion. How many paragraphs in this post look anything like that? I tend to paragraph by sound, and often set off a sentence that would either be a conclusion or the introduction of a new element by itself, simulating the pauses for emphasis I might use in public speaking.

    Like this one.

    When I was an undergraduate student, one of my professors (J. Paul Grove at Walla Walla College for those who might know), required me to turn in three sermon outlines a week as part of a course in Hebrew prophets. I thought this was a horrible requirement, as I had no intention of becoming a preacher. I was going to be a biblical scholar. Bless Professor Grove! It turned out to be one of the better exercises of my educational process because it made me think of a connection between the data I was accumulating and the real world. It didn’t result in even one sermon outline that I would ever use in preaching, even though I have preached frequently. That’s because I vigorously eschew three point outlines and diligently work to violent rules of homiletics.

    Which means that I’m human. I don’t always follow the rules.

    I turn this now to structure, which I discussed a bit yesterday. Studying structure is good in interpreting scripture. Just don’t be too structured about it. I’ve been asked if I accept various outlines of Hebrews, such as Vanhoye’s. I guess it depends on what you mean by “accept.” I find a great deal to commend his work, but I don’t find that any structure is followed closely. I believe that in studying Hebrews you have to carefully track what the author has done, the ways in which he connects and interweaves his topics. He’s flexible; the interpreter must be flexible.

    Just like getting stuck on one label when trying to communicate, getting stuck on a structural label can be harmful to your mental health. People rarely follow the rules completely. Most commentaries that I’ve read do provide caveats about their structural conclusions. You should provide more.

    Flexibility is a key to sound interpretations, because people are flexible.

    (Featured image credit: Openclipart.org)

  • Notes on Terms and Language Teaching

    Notes on Terms and Language Teaching

    Dave Black comments some on linguistics and teaching biblical languages in a post today. (Check out the linguistics conference coming up!)

    The difficulty is the difference between teaching someone a language in a classroom and in discussing and describing that language in some detail as a linguist would want to do. Both the framework and the deeper understanding are good and proper goals, though there is often a conflict between the two. When do you teach what?

    Dave covers a good selection of points from the debate over verbal aspect. There are problems with words like “punctiliar” or even “progressive” in terms of verbs. There are also problems in mapping the tense system (and the word “tense” itself) when teaching. But these issues are part of the problem of linguistics generally.

    Consider a label like “tree.” What do I mean by the word tree? Is the plant growing in my yard that is three feet tall a tree, a weed, a plant, or perhaps a bush? It might, under the right circumstances be called any one of those things. A simple, singular label is necessary to communication, but at the same time, a singular, simple label is also a cause of problems. For example, if I say to my wife, “We need to throw that tree out,” I may mean that a potted plant has grown very large, and I’m using tree hyperbolically to refer to it while demanding its exit forthwith. On the other hand, I could be referring to a shoe tree that’s worn out and should be discarded.

    This is why the line, “it’s just semantics” is so often lazy. When someone is playing rule book lawyer with the language, it’s quite appropriate to point out that one is expecting more of language than one is likely to get from it. We get along with ambiguity all the time. The problem comes in when we decide to be picky, or when we accidentally manage to use just the wrong word at the wrong time, meaning one that is almost right, but that can lead one off into a completely different semantic range than intended. But semantics is precisely what “it” is, and what it always is. It is about meaning. What did you expect? So it’s semantics. The word “just” is a bit oddly used. Bad semantics!

    What I try to do is very quickly introduce students to the idea that labels are shorthand. When I use the term “punctiliar,” I point out that this is a shorthand label. Why don’t I change the word then? Because my new shorthand label will also pick up unnecessary connotations, and then I’ll have to explain how it applies. Further, the student is doubtless going to see the word “punctiliar” in commentaries (as Dave points out), and he or she needs to know its intention, and even how to understand the potential fallacy. Commentaries are quite capable of containing incorrect linguistic information.

    It’s easier for me, because I teach by ones and twos, not by large classes of seminarians forced to do their required courses. I had that experience as a graduate student when I tried to tutor marginal or failing Greek students. They wanted me to get them past the test. I wanted to help them understand. Conflict! But those students I have taught since have come to me because they want to learn and understand, so I take the time.

    My conclusion is that no matter how you label it, you’re going to have to make sure students understand how these labels we call “words” work. Even if you take a living language approach, and try to get the students to understand the language as naturally as possible, you’re still going to have to help them understand linguistics if they’re going to translate those words and ideas into their own language for the benefit of those who haven’t learned a foreign language. I’d almost, almost, prefer to teach a student linguistics over teaching that student Greek or Hebrew. If I had to choose, that is. Which I don’t.

    (Featured Image Credit: Adobe Stock #126360408. Not Public Domain)

  • Linguistics Conference at Southeastern Baptist Theological Seminary

    Linguistics Conference at Southeastern Baptist Theological Seminary

    Re: Linguistics and New Testament Greek: Key Issues in the Current Debate

    It’s more than a year away, April 26-27, 2019, but this conference looks like about the most fun you can have on a seminary campus without breaking the rules! I see several names I know, some well, and one Energion author, Thomas Hudgins, who will be talking about Electronic Tools.

    I’m already planning to be there. Maybe we can meet!

     

  • Book Notes: Linguistics for Students of New Testament Greek

    linguistics for greekI try not to call what I do here “reviewing” as I don’t really try to provide an academic review. In fact, I might do better to call these “Ramblings after Reading.” In the case of this book I need to provide an additional caveat. Dave Black is a friend, and I publish several books by him (The Jesus Paradigm, Christian Archy, Why Four Gospels?, Will You Join the Cause of Global Missions?, and The Authorship of Hebrews: The Case for Paul). Since I own the company and have named myself chief editor, the fact that I’ve published that many titles by one author should indicate that I like his work. So don’t get the idea that you’re about to read a scholarly review by an impartial reviewer.

    Probably more important than that, however, is the reason I read this book in the first place. I have long believed that we might do the church a favor if, rather than one semester (or even quarter) of a biblical language, we gave them one quarter of introductory linguistics. This is not because I don’t believe in the value of biblical languages for biblical teaching and preaching. Quite the contrary!

    The problem is that there are many people using Greek or Hebrew in the pulpit, their Sunday School classes, small groups, etc. who don’t actually know enough of the language to support the use their making of it. I have come to the place where I tell those I can to beware. If a pastor or teacher says something like “What the Greek really says here is …” you’re about to be misinformed.

    There are teachers and preachers who do have a solid knowledge of the languages and use them in their study. They’re not that likely to say “what the Greek really says” when they introduce their discussion of a Greek word or phrase.

    Generally those who do that read the answer in a commentary or other study resource, and often they lacked even the skill to correctly interpret the commentary. In addition, the commentary itself may well have been wrong. I know it’s shocking, but even PhD’s whose books go through a serious editorial process can make mistakes.

    There has been a great deal of effort put into correcting some of the most common errors, and so we have lists of exegetical fallacies, such as D. A. Carson’s aptly named book Exegetical Fallacies. I’ve even published one (via my company Energion Publications) titled “In the Original Text It Says …” which provides examples of some fallacies and suggests how to avoid them.

    These tools are useful, but they only deal with the problem partially. Exegetical fallacies are committed because they often appear to work. Etymology often does point one to meaning, and thus one may become convinced, or just lazily assume, that etymology determines meaning. From valid observation to fallacy may not take that many steps.

    There is no real substitute for some understanding of how language works, and to get that understanding you need to do more than learn the vocabulary of a foreign language. I don’t teach Greek or Hebrew regularly, but from time to time I’ll have a few students in the church who want to learn. I try to introduce some linguistics right from the start. I tell them I hope that they’ll keep going with their study of the language until they can use it regularly, easily, and fruitfully in study. But if they don’t, I hope they will at least remember a bit of how languages are put together. If you’re wondering whether I’m qualified to comment, you can discover how I pat myself on the back via footnote 1.1

    So having outlined my view of the problem(s), what about the book?

    I wish every person who was going to study the Bible using the original languages would read this book. I’ll concede the possibility of getting the same knowledge elsewhere, but it would be difficult, I think, to find a book that both sticks with the basics with such rigor, and then applies them so well to the problems of translation and exegesis. Both of those issues were problems for me in my study. I recall being told that “Greek doesn’t have syntax,” an obviously silly statement, and having to discover the details of syntax as I went through those later courses. We didn’t have a good text. I did read other texts, such as Barr’s The Semantics of Biblical Language (a more recent and less widely accepted book in those days!) but getting down to what it meant for me was harder.

    Even though I have read a number of the works Dave Black cites or suggests for further reading, I still found this book helpful, because it helps provide a framework and make sure one hasn’t missed niggling details that will catch up with one later. You can find more detailed information on every topic (Dave provides a suggested list at the end of each chapter), but you will do well to get some landmarks by reading the chapters first. I’m reminded of one of my professors who said he’d like to see an introductory style course in Old Testament and New Testament given at the end, rather than the beginning, of one’s Bible study, because of the value of tying things together and drawing connections. I fully agree! Many people know quite a number of details, but fail to understand how these details fit into a bigger picture.

    So what does this book cover?

    It starts by introducing linguistics. This is valuable again in setting the boundaries. There are those who think I am a linguist because I have learned a number of languages. Not so! Linguistics is a field of study with many subfields, some of which will become topics for later chapters. (One will get a helpful idea of what is to come if one reads the preface, but that may be too much to ask! In particular, “read not consulted”–this book is an introduction, not a reference.)

    Following this are chapters on phonology, morphology, and then syntax. The latter is greatly neglected in biblical languages courses of which I am aware. If the teacher can force the students through enough vocabulary and basic morphology, perhaps that is all that can be expected with the limited time. A particular strength of this chapter is the presentation of the basics of immediate constituent analysis and later of transformations. Both of these concepts can look very difficult, but they are basic to being able to understand. We do some of this when we outline, but few people have the patience for that. Never fear! Dave will show you how.

    Chapter 5, “Semantics: Determining Meaning,” however, is the core of this presentation. Don’t imagine you can just jump to it, but a great deal centers on the concepts presented here. You’ll learn about etymology (what it’s good for and what it’s not), the difference between word and concept, semantic range, polysemy, synonymy (and many others) and why those terms are important. I find myself over-using the term “semantic range” and several paragraphs in this chapter helped me come up with some better ways of expressing the necessary concepts in less time and less technical language.

    Chapter 6 is a very nice introduction to the history of the Greek language. You’ll find such an introduction in most grammars, but those chapters won’t be this detailed, and they won’t give you the practical applications. After you read this chapter you should know why understanding how language develops is important to both language student and exegete.

    I’m glad that the final chapter, “Discourse Analysis” was added to the second edition. I was fortunate to have teachers who got me started in this areas, though the field has developed some since I was a student. My personal observation is that the thing that prevents people from doing more discourse analysis is that it seems to be too much work. Unfortunately, you can’t reap the benefits until you have done all that work, so you don’t realize what the rewards are.

    Well, follow Dave through Philippians. See how discourse analysis can shed light on many pesky questions regarding that letter. You can agree or disagree on details, but you will be much better prepared to understand any particular verse.

    May I also appeal to students at this point to learn how to do this for yourself. Don’t just depend on someone else who has done the work. It is absolutely helpful and a good idea to look at what others have done. But too many people get the meaning of the Bible from the outlines, headings, and notes provided in their study Bibles. You may come to the conclusion that the book is structured precisely as it was in the outline provided. But once you’ve done the work to determine that, I think you’ll feel that the time spent was truly worth it.

    This book requires some knowledge of Greek. Dave mentions advanced students. To some extent he is right. I’d suggest it after you have a good facility with the language. I would also recommend that teachers study it so as to get an idea of how to present this material to students. Many of these concepts can be presented earlier in class, preparing the ground for more serious study later.

    In other words, I think this is an excellent book. I would rate it 5 stars, and I believe it can be useful to a broader audience than the one intended by the author, because there is always value in a book that applies important concepts to actual problems.



    1. Do I have any business making these kinds of criticisms? After all, I’m a publisher with just an MA degree. Quite true. Yet I’d say one should question my knowledge more when I set out to talk about theology than about languages. My undergraduate degree was in biblical languages, including four years of Greek and three of Hebrew (actually I bypassed first year Hebrew through personal study). I also took a class in textual criticism at the undergraduate level, along with a minor in French. That minor language, along with growing up overseas (four years in Mexico as a child) gave me a different perspective on language as well. We sometimes get a distorted view of Greek and Hebrew because we’re trying to make them fit a preconceived agenda. Studying a language without that religious baggage can be a big help. I often refer to Max Knight’s translation of Christian Morgenstern’s Galgenlieder as an excellent example of the difficulties of translation, expertly overcome. Incidentally, I received a copy of those poems from my undergraduate German teacher, who knew my interest in translation and wanted me to learn from them. I am eternally grateful to him.

    I followed this with an MA in religion, again concentrating in biblical and cognate languages. So unlike many seminarians, I came to my MA ready to make use of the expertise of professors rather than needing to work on the basics, and I also spent all my time on the languages. At the same time, I spent hardly any time on issues of theology, and none at all on things like church administration, church history (I completed a church history requirement by taking patristic Latin!), counseling, homiletics, and so forth.

    Then I took one quarter in another master’s program in linguistics one I did not complete for a number of reasons. Since then I have continued my reading in this area.

  • Greek and Ministry

    Thomas Hudgins is teaching Greek, and he thinks students should study with the intention of actually using their Greek in ministry (HT: Dave Black).

    I’m delighted to see more and more effort put into this type of teaching. I was very frustrated as a graduate student when I saw how students in the MDiv program were merely trying to get by in their Greek course. The structure of their course work helped foster this particular attitude, because basic Greek was largely an effort to get enough knowledge of the basic vocabulary and grammar to slip through the test so Greek could be ignored from there on. The same applied to Hebrew.

    Since my undergraduate degree was in Biblical Languages, and I was in the academic MA program rather than the MDiv program, I got tapped to help tutor Greek students. (My undergraduate program involved the equivalent of five years of Greek, with two year-long courses taken simultaneously, as well as textual criticism.) These students would try to catch me a few hours before their tests so I could drill them on the things they would have to regurgitate on a test paper. They had no patience for any of my efforts to help them understand the material.

    Starting with a mastery of grammar actually works well for me. I learn languages fairly easily, but more importantly, I was already convinced of the value before I started my first Greek class, and I was willing to put in the effort necessary to learn the language well enough so I could use it. But for someone who is not planning to specialize, the focus needs to be a bit different.

    One of the major differences is simply attitude, both on the part of teacher and of student. Are we acquiring data in order to check off a box on our list of requirements, or are we acquiring a tool?

    I think linguistic concepts should be introduced right at the beginning. How does language work? Why do you have a hard time with pronouncing certain sounds? How does etymology help you learn vocabulary, and how can that in turn lead you astray? How can you study deeply, yet share with the people in the pews or in Sunday School classes in a way that is accessible?

    I like Dr. Hudgins’ approach and his brochure. I’m sure his students will be blessed. As Dave said, may his tribe increase!

  • Is that Idiom Right?

    We all use idioms, mostly unconsciously. There are a number that bother me that are in common usage, such as “I could care less” which developed from the more logical “I couldn’t care less.” But idioms often aren’t about logic. They’re about what people actually say, and what other people understand by what they say.

    There’s a great article on this from a few weeks ago on Lingua Franca. Enjoy!

  • Some Basic Linguistics

    One of the great problems I find in teaching biblical languages, or in explaining Bible translation to lay audiences, is that people don’t understand meaning very well. They assume that words have fixed, narrow ranges of meaning, and that if you search carefully, you can find a word or phrase to precisely represent that word in the target language.

    Most of them have some idea that this might not be right, but that hasn’t seeped through to their practice. A few questions usually suffices to get the process started.

    I’m embedding a video from Wycliffe Bible Translators (UK), or rather audio with a slide show, that does a good job with the basic concepts. This one doesn’t go in depth. What it does is clear a lot of the ground and get some basic structures in place. (HT: Kouya Chronicle.)

     

     

  • Linguistics and Exegesis – a Link

    A Living Sacrifice provides a link to some material on linguistics and exegesis, particularly word studies.  The articles are by Benjamin Baxter and are in the McMaster Journal of Theology and Ministry.  One is The Meaning of Biblical Words, and the other is Hebrew and Greek Word-Study Fallacies. I highly commend both.

    The key element in the Fallacies article is that the author provides substantial examples in Hebrew, Greek, and English for each fallacy.  I was already acquainted with these types of fallacies, yet I am certain I will find myself using the examples in this article frequently.  It’s the sort of thing you keep on file for ready reference.

  • Dave Black: Ten Best Books for Studying New Testament Greek

    David Alan Black has posted a new essay, Ten Best Books for Studying New Testament Greek.  The majority are books I have read and/or are on my shelves, but there are a couple that are just on my “need to read this list” and a couple more I’m going to add.

    I note that when I teach Greek classes locally, usually to a couple of people at a time, I use the #1 and #2 books on his list.  I know that as one of his publishers I should perhaps use one of his books as my text, but I will plead historical reasons–I picked the textbooks before I was his publisher!

    If I might underline a couple of books on his list:  #5. Peter Cotterell and Max Turner, Linguistics and Biblical Interpretation, and Dave’s related book, Linguistics for Students of New Testament Greek: A Survey of Basic Concepts and Applications. I take a small risk in recommending books I haven’t personally read. My introduction to linguistics started with my graduate advisor, Dr. Leona Running at Andrews University, and continued with some graduate work in linguistics at the University of Illinois Chicago Circle. Those linguistics classes did more for my understanding of translation and exegesis than did many of my exegesis classes.

    I always spend time talking about linguistics with my Greek or Hebrew students.  It makes a great deal of difference to how valuable one’s technical language knowledge will be.  When I studied Greek, I found that even syntax was neglected to some extent.

    Finally, #10. Rodney Decker, Koine Greek Reader: Selections from the New Testament, Septuagint, and Early Christian Writers.  In particular note the “Septuagint” and “Early Christian Writers.”  In my opinion, if your reading is limited to the New Testament, you cannot claim to really understand New Testament Greek.  I include the LXX in my regular reading, and I’m including more and more literature from the early church.  It will be well worth your while to do so.