Threads from Henry's Web

Tag: Bible Translation

  • Psalm 104

    I’m planning to do some posting on translating and transforming Hebrew poetry over the next few weeks, so I want to start with a couple of links to my existing work on Psalm 104. I did a considerable study of the structure of this Psalm in graduate school. I’m not in a position to repeat the work I did then or even to reaffirm it, but I’m planning to work from the text that I prepared for that paper, and build from there.

    Here are the major links:

    The translation was prepared for technical purposes and not for general reading. The actual translation without the notes follows.

    (1) Bless the Lord, O my inmost being!

    0 Lord, my God, you are very great;
    You are clothed with majesty and splendor.

    (2) He spreads out light like a covering;
    He stretches out the heavens as a tent.

    (3) He fills his upper chambers with water;
    He makes the clouds his chariot;
    He travels on the wings of the wind.

    (4) He makes the winds his messengers,
    Fire and flame his servants.
    (5) He established the earth on its foundations;
    It shall not be moved forever and ever.

    (6) The primeval ocean covered it like a garment;
    The waters stood over the mountains.

    (7) Prom your rebuke they fled;
    From your thunderous voice they rushed away.

    (8) They went up to the mountains, down to the netherworld chasms,
    To the place which you appointed for them.

    (9) You set them a limit which they cannot transgress;
    They will not return to cover the earth.

    (10) He sends forth springs in the wadis;
    They flow between the mountains.

    (11) He makes all the beasts of the field drink;
    He makes the onagers shatter their thirst.

    (12) Near them (the streams) the birds of heaven nest;
    Among them the ravens give forth their voice.

    (13) He waters the mountains from his upper chambers;
    From the fruit of his work, the earth is well supplied.

    (14) He brings forth grain for the animals;
    And grass for those who serve man.

    He indeed brings grain from the earth;
    (15) And wine which gladdens the heart of man.

    He indeed makes their faces shine with oil;
    And bread, which strengthens the heart of man.

    (16) The trees of the Lord have plenty;
    The cedars of Lebanon which he planted,

    (17) Where the birds make their nests;
    As for the stork, her house is among their tops.

    (18) The high mountains are for the mountain goats;
    The rocky places are for the coneys.
    (19) He made the moon for appointed times;
    The sun knows when to go down.

    (20) It darkens, and becomes night;
    In it creep all the beasts of the thicket.

    (21) The lions roar for their prey;
    They seek their food from God.

    (22) The sun rises, so they may be gathered,
    So they may lie down in their dens

    (2)) Man goes forth to his work,
    And to his labor until the evening.
    (24) How marvelous are your works, O Lord!
    You made them all wisely.
    The earth is full of your created things.

    (25) This sea, great and wide across,
    In which are uncountable creatures,
    Living things, both small and great —

    (26) There the ships travel;
    Leviathan which you made,
    Plays in it.

    (27) All of them look to you,
    To give them their food on time.

    (28) You give to them, so they may gather;
    You open your hand, so they may be satisfied with good.

    (29) You hide your face, and they are disturbed;
    You bring their breath to an end,
    And they return to their dust.

    (30) You send forth your breath, and they are created;
    So you renew the face of the ground.
    (31) Let the glory of the Lord. be eternal;
    Let the Lord rejoice in his works —

    (32) He who looks at the earth, and it trembles;
    Who touches the mountains, and they smoke.

    (33) I will sing to the Lord while I live.
    I will sing to my God while I continue to exist.

    (34) Let my song be pleasing to him,
    I will rejoice in the Lord.

    (35) Sinners shall be removed from the earth,
    And the wicked will be no more.

    Bless the Lord, O my inmost being!

    I’ll be working from that basis on my various presentations of the content of this Psalm in different forms.

    See also my recent note on Hebrew Poetry.

  • Nitpicking Translations

    Centuri0n responded, in a way to my post Conscience of a Christian Publisher. I posted a response once, and unfortunately that response was eaten by the server. I was able to restore everything else, but this I have to rewrite. I’m not trying to repeat the other post precisely, so if you read it, don’t look at this as a duplicate, though I am trying to cover the same ground.

    There are a number of things I could respond to, such as his comments on my use of “conscience,” but I think I’ll skip to what I see as the major problem of logic, and it’s one that is not unique to centuri0n. It’s quite prevalent amongst advocates of literal translations. Consider the following quote:

    My complaint about the TNIV, as you can read for yourself, is that it whitewashes the controversial nature of its methodology. Now, if the Bible is just a “signpost”, my complaint is, of course, nit-picking. What the Bible says isn’t actually of first importance but of far secondary importance

  • Prescriptive vs. Descriptive Grammar

    Peter Kirk has a post at the Better Bibles blog discussing what type of language the Bible should be translated into. (Note that I decline to respond to prescriptive grammarians by continuing to use a preposition to end my sentence with.)

    Peter says:

    It seems to me that the only people who have the right to prescribe the form of English are the speakers of the language taken as a whole, exercising their democratic right in the way that they actually speak and write. That implies that the only prescriptive grammar for English is in fact a descriptive one. For if there is any way in which we ought to speak or write, it is the way that the language is actually spoken or written.

    I’m not sure that the language of “rights” is quite appropriate here, though history certainly indicates that whatever the grammarians try to do the people will prescribe the form of the language, and perhaps that is the best form of right!

    Now if any writer or translator wants to communicate with an audience, they (singular they, eh?) must use language that the audience can understand. Thus it seems pretty obvious that a translation should be made into the form of language that people actually speak and understand, assuming that communication is the purpose. I’ve found an interesting phenomenon in classes I’ve taught on Bible translations. People don’t always hold communication to be the primary purpose of a Bible translation. In several classes, substantial minorities, though never a majority, have indicated they would prefer majesty of language. In general, I can get a lively debate going on the question of whether the Bible version used in scripture readings should be targeted at the church members or at whatever group they believe it is their mission to reach.

    One may gather from my ramblings that I think communication is the primary purpose, and that mission tends to define who we are to communicate with. I personally feel very comfortable reading the Revised English Bible, but I tend most commonly to recommend the Contemporary English Version, simply because it is an easier read for my audience.

    But this “prescriptive” vs “descriptive” grammar issue has another dimension, and here I have some appreciation for the prescriptivists. I would suggest that your elementary through high school grammar teachers should be very prescriptivist. In fact, there is a continuing role for prescriptive grammarians in society in trying to keep change in the language to a reasonable minimum. The prescriptive grammarians, represented especially by teachers, also have their democratic vote. All the speakers of a language are equal, one might say, but some are more equal than others.

    None of which changes the final answer to Peter’s question about translating the Bible. For that endeavor, grammar must be strictly descriptive. How does the target audience speak, and what do they understand?

  • Translation and Knowing God

    Paul at Grace rant . . . what? says he has gotten back to reading his Greek New Testament. I congratulate him on this spiritual discipline, and I do believe studying the Bible in its original languages can be a spiritual discipline, but I do think some of his additional thoughts deserve some reconsideration.

    He says:

    The trend in scripture translation is to make it more accessible. For example, The Message, The New Living Translation, and the New Century Versions all purport to render the scriptures in a more affable format. I use these translations often in sermon preparation, but I have begun wondering if this really is a good way to digest the scriptures. I mean, isn’t God worthy of us really struggling to find the meaning of the words on the page? . . .

    There are some serious problems here, I think. I have a great respect for study of the scriptures in the original languages. I took both my undergraduate and graduate degrees in Biblical and cognate languages. There is much to be gained from deep study of the Bible, and the effort that is required to read it in the source languages helps one get into those spiritual depths. But at the same time, the Bible was not inaccessible to the people who first received it. When the New Testament was written in Greek, Greek was the common language. It was the accessible language, much like the English languages that Paul mentions in his quote.

    And while there are some variations, such as Hebrews and Luke-Acts, the New Testament is largely written in everyday language, not complex language.

    And shouldn’t we too know that thousands of Greek manuscripts offer divergent phrasing on nearly every passage in the New Testament? Oh, and isn’t it noteworthy that the Greek language’s vocabulary is much more complex and that translators have to make very important theological decisions about which word they think is the correct word from a Greek word that may or may not be the original word?

    It is quite true that it’s valuable to know all of these things. But it’s also important to know that this complexity is not merely a feature of Greek; there are always variations to deal with in translation from one language to another. It’s not that Greek is more complex than English, though an argument might be made that it is, it is that English and Greek express things differently. Greek was not complicated to people who grew up speaking it. Certainly translators have many theological issues to decide as they translate–to translate is to interpret–but those decisions can be aided by context and by reading multiple English translations.

    But the level of work involved in understanding it is a function of time, and not one of the text. In other words, reading the Bible in Greek requires additional work today, and that is a good spiritual discipline, but it is not a function of the Bible itself.

    I think that the struggle of knowing God is very real, but it is not a matter of struggling to understand the words of scripture. Making the scriptures more accessible doesn’t remove the struggle of knowing God, it just opens the door to more people to get involved in trying to know God. Because of translations they can do so with the same ease as early Christians could, because they can access the information in their own language.

    By all means use the discipline of studying the Bible in Greek or Hebrew if you know those languages, but realize that it is simply a discipline for you; language is not a barrier God intended between people and the word.

  • More on Gender Accuracy

    Suzanne has returned and is carrying on the debate about the approiate use of language for gender in Bible translation. Her response comes in three parts. I’m going to comment briefly on each, and then make some further comments on this controversy. (You can follow Suzanne’s links to Adrian’s posts.)

    First, in Response to Adrian: part1, the lexicons, she deals with the issue of the lexicons. I’m not so concerned with the particular lexicons concerned. I do have all of them in my Logos software, and also have some in the form of good old-fashioned books. But the number of lexicons is not really the point.

    It is an error to simply combine the definitions one finds in a lexicon in order to produce add nuances of meaning. Each context must be examined on its own merits. Now there certainly can be a transfer of meaning between contexts, i.e., one uses a particular word in a new context because of some relationship its existing meaning has with the new situation. The individual definitions are not necessarily disconnected, but they can become so. Let’s take the word “car” as an example, we have cars we drive on the highway, train cars, elevator cars, street cars, and so forth. In each context a specific definition applies. I cannot claim that there must be an element of individual locomotion in the concept of “train car” just because that is an element of the word “car” when speaking of an automobile.

    Similarly, when it was common to refer to “humanity” as “man” in English, one couldn’t claim a special emphasis on maleness. Going back to the language I grew up with, I might have said something like, “That is a man walking down the street.” Doubtless, with the emphasis, I’m referring to a man as opposed to a woman or child. On another occasion I might have said, “God is infinite, but man is finite.” In this second case, should you assume that there is somehow an emphasis on “maleness” in my reference? Absolutely not! The contexts are totally different. In the first case I’m specifiying a male, in the second, I’m contrasting being human with being God. There’s no carryover. The part of the definition that connects is the humanness, not the maleness.

    Now whether it was feminists who got it started or not, I think using “human” is a much better idea, and makes the second sentence clearer. But that is something I have learned in the last few years. Henry the college and graduate student would have used the other terms. But I never intended any male representation by that usage.

    As I tell Greek students: The lexicon doesn’t tell you what a word means; it gives you a set of options. The context tells you what the word actually means.

    In her second post, Response to Adrian: part2, the interlinear, I have to agree with Suzanne, though I’m a bit more laid back on the use of interlinears. (Students are never to use them, as they inhibit actual language learning.) But interlinears do not get you closer to “what the Greek really means.

    In her last post, Response to Adrian: part3, neutering, Suzanne points out that simply not referencing someone’s masculinity does not result in neutering.

    I have to add that I see this concern about neutering as a bit hypersensitive. There seems to me to be a “theological correctness” approach going on here, in which someone has to watch their language closely to make sure they don’t accidentally allow for any feminization of God. I have no sympathy with this theological correctness any more than I do with political correctness. But barring one New Testament that corrected gender language with reference to God, I have not found any of these feminist agitators amongst Bible translators. I have only found a concern for accurate translation, translation that communicates clearly to the audience. I must just run in different circles. 🙂

    On the other hand, I probably do have a feminist agenda from a complementarian point of view. I favor women in church leadership, women as elders, women as pastors, and women in every last position they are gifted and called to fulfill. I don’t need to retranslate the Bible in order to support this view. I merely need to understand the incarnation, and then read the Bible in its cultural context. I believe that God has called the church to move ahead of the world on this issue, not behind, and that it is a scandal that we are still trying to keep women out of leadership.

    I hope for the day when we see such barriers fall in the face of our oneness in Jesus the Christ.

  • An Incarnational View of Translation

    In several previous posts I’ve talked about the incaration and how it is central to Christianity. This post is not a continuation of that series, but rather a very brief detour to look at one of my favorite topics: Bible translation. I had been thinking about this post for a few days, but I was pushed to actually write something when I read nspiration, inerrancy, and the incarnation: grappling with the human and historical dimension of an inspired scripture, by Michael Pahl. Now the post consists of a number of quotations from other authors, each commenting on the unique divine-human combination in the Bible; somehow God inspires without trampling on the humanity of the authors.

    My question is this: How does this impact the way we translate? What translation principles are best suited to translating such a book?

    I’m tempted to answer simply that if the Bible is fully human (without denying that it’s fully divine), then our translation principles should be the same as they are for any other fully human book. As Wayne Leman (Better Bibles Blog) would say, the translation should be clear, accurate, and natural.

    But just as the divine side of Jesus (holy, blameless, undefiled–Hebrews 7:26) draws us away from the failures and the weaknesses and “leads us on toward perfection” (Hebrews 6:1), so I would suggest that our belief in the divine side of scripture should draw us forward toward the best translation effort possible. That best effort, in my view, should be to let the modern reader or hearer hear God in the human language of scripture.

    That’s why I like the term “dynamic equivalence” even over more current terms like “functional equivalence.” Don’t get me wrong. Functional equivalence is a good and descriptive term, but it somehow fails to become a fire in my bones. “Dynamic equivalence,” trying to produce the same effect in a modern audience that the original text (or spoken words) would have produced in their original audience–that’s a worthy, fire-in-the-bones goal.

    I have never actually seen it, though there are passages in numerous versions that do approach it. It’s a bit like the “perfection” of Hebrews 6:1–you keep moving toward it. It’s the north star, drawing you toward it, but light years away. I have never myself produced anything that I even regard as a good translation in writing. They’re just adequate to their purpose most of the time.

    I recall one instance on a mission trip when I was asked to give a devotional. Because I had heard some team members talking about how they were less spiritual than others, and that the officially religious folks (myself included) were doing the “spiritual work,” I used a portion of 1 Corinthians 12. I read it over and over from my Greek Testament until it was rooted in me, and then I just spoke my translation from my heart. I recommended that members of the team read the passage for themselves. One member came to me after the devotional time and said, “What translation were you reading from? I want to read it in that translation.”

    I wish I could produce that effect on demand, but I can’t. Even at that, of course, it was only a translation going on toward perfection, not one that had attained it. I’m guessing that the only way to do it would be to spend as much time with each passage, under as much conviction of the Holy Spirit as I was under at that time, before letting the passage pour forth for your audience as God’s message for God’s people on God’s mission.

    Even though I studied Biblical languages in school, I have never accepted the notion that one must be skilled in the source languages in order to understand the Bible. I suspect this comes from my incarnational view as well. God “got into” the words in Hebrew and Greek, and I think that with the aid of the Holy Spirit, he can “get into” the words in English.

    Translators, teachers, and expositors also become the conduit for God’s power in God’s word to get to God’s people. That’s the guiding star, I think, of truly dynamic–filled with dunamis–Bible translation.

  • More Gender Accuracy Fun

    Adrian Warnock has continued his series with Cows, Dogs, and Political Correctness parts 2 and 3. I’m quite certain that the folks over at Better Bibles will answer some of the major points, and indeed they already have in some comments.

    I want to simply point out that it appears to me that those supporting male representation are trying to create translation rules that serve a particular theology, while they are accusing their opponents of forcing the language to support a politically correct view. No doubt there are those who trying to read political correctness into the Bible. I say “no doubt” because “politically correct” is such a dismally badly defined word that one can hardly defend oneself from the charge of political correctness once made.

    Let me look at just a couple of quick quotes from Adrian’s post:

    All these arguments about how to correctly render specific Greek words in English leaves us in danger of missing what is the main point about this issue. The controversies about these words in modern English translations often fail to discuss a far more fundamental point – especially when it comes to the translation philosophy of the ESV. That point is the desire to have a Bible that is essentially literal, and as much as possible, transparent to the original language.

    But in fact the major issue here is whether it is even possible for a translation to actually be literal and at the same time transparent to the original language. It seems to me that this combination alone suggests some misunderstanding of the function and the possibilities of translation. I am further driven in this same direction by the next paragraph:

    This all becomes very apparent when you examine an ESV reverse interlinar in comparison with almost any other modern translation. The ESV very clearly attempts to translate each Greek word and it doesn’t take a long time of studying with such a tool before you begin to understand something of what each Greek word means in different contexts. Words which have a clear equivalent in English are not arbitrarily changed to other words with different meanings. Thus, the translation attempts not to capture the “broad meaning,” but the actual word-for-word meaning of the text. If we believe that each word of the Bible is breathed out by God, such an approach to translation is vital.

    But an interlinear doesn’t tell you “what the Greek really means.” I see here a bit of that endless pursuit of the one expression that will tell the reader the real story without that person bothering to learn to read Greek. Adrian says, “Words which have a clear equivalent in English are not arbitrarily changed to other words with different meanings.” But there are no such Hebrew or Greek words. Each word has its own range of meaning and they are simply not equivalent between two languages. What one observes by reading an interlinear is a false picture. There is some value in an interlinear, but testing the accuracy of a translation is not one of them.

    In part 2 Adrian stated: “In short, it seems that the words anthropos and aner are loosely synonyms.” That partakes of the same sort of problem that the above paragraphs do–the assumption that some sort of word for word equivalence is a workable method of producing an accurate translation. It is similar to the concept frequently held by beginning Greek students that the real definition of a Greek word is the English gloss. “Anthropos” and “aner” are not loosely synonyms, and even many complementarians would be annoyed to hear it put that way, I suspect, because they want to argue that “aner” is very rarely anything but all masculine. More importantly, however, a translator must regard each of these words as having a range of meaning, which they do, and try to choose the best equivalent in each context. Their ranges of meaning do overlap, but they also have distinctive portions of those ranges as well.

    I recommend reading Adrian’s posts and follow the comments and entries elsewhere, especially from the folks over at Better Bibles.

  • Gender Accuracy Fun

    Adrian Warnock has responded to his perceptions of the approach taken by the folks over at Better Bibles. Since this is a topic that interests me, I thought I’d call attention to it. I don’t have anything to add at the moment, as I think Peter Kirk, both in comments on Adrian’s blog, and in a posting on Better Bibles, has brought up all the points I might have noticed.

    It appears that Adrian is accusing the Better Bibles folks of holding a position that I know they don’t hold. I also think Peter Kirk is asking an excellent question when he wonders what political correctness has to do with it.

    My eyes are glued to my comment trackers. 🙂

    PS: I would possibly be more properly accused of political correctness than any of the folks at Better Bibles. See my essay Gender Neutrality and Bible Translation.

  • Capitalization and Translation

    One of the categories on which I rate trnslations for my Bible Version Selection Tool is on capitalization of divine names. This has resulted many times in people asking me if I’m not being a bit nitpicky in making an issue of something like that.

    Wayne Leman has posted about Psalm 2 and his arguments illustrate my point well. Comparing Acts 13:32-33 with Psalm 2:7 in the NET, Wayne comments:

    Notice that the NET translators, theological conservatives who believe that Jesus is God’s Son, the promised Messiah, uppercase “Son” in Acts 13:33, but not in Hebrew Bible passage which this verse quotes, Psalm 2:7. I personally believe that the NET translators have translated accurately in each passage and indicate appropriately authorial intent with this differing typographical notation.

    Wayne also shows a list of translations that, he says, “Christianize” the Hebrew Bible in this verse. Included among them are the NIV, NASB, ESV, HCSB, and GW. All of this is accomplished by means of the capitalization–something that is a choice of the translators and can be merely stylistic, or can, as in this case, be very meaningful. The choice whether or not to capitalize any pronouns referring to the deity is, in itself, stylistic. But if one chooses to follow that practice, then a verse like Psalm 2:7 cannot be neutral because whether you capitalize certain words or not, it will be taken as an indication of your interpretation.

    Now the indication that I give in my selection tool doesn’t test this level of detail, but it can give you an idea. And I think that the better choice in modern English is to lose the capitalization of the pronouns throughout.

    Wayne concludes:

    Better Bibles should use the least amount of “interpretive translation” necessary for conveying the original meanings of the biblical authors accurately to translation audiences.

    I couldn’t agree more.

  • Bible Translation: ESV

    We pause briefly in these various Bible study series to call your attention to a comment on the English Standard Version (ESV). Wayne Leman has provided a little bit of history, along with some passages for comparison between the RSV and the ESV.

    Wayne does his usual thorough job, so I have very little additional comment here. I recommend his ESV Links as an excellent place to start your research.

    A couple of other Bible translation links amongst my own pages are: