Knowable Word

Helping ordinary people learn to study the Bible

Copyright © 2012–2024 DiscipleMakers, except guest articles (copyright author). Used by permission.

You are here: Home / Archives for Translation

The Demystifying Effect of Modern Bible Translations

By

Nitoy Gonzales writes from a part of the world where the King James Version of the Bible tends to be the most accepted version among those who speak English. Yet he offers some great insights about the power of more modern translations to demystify the Bible for believers.

With its archaic words that feels like it’s so holy and a reverend history taught by Bible Baptist preachers, it creates a mysterious or mystified look at this old version. The mere fact you have it and it’s the version preached at your church feels like a blanket of security that you belong to the “good guys” rather than to read, understand and learn from it. It feels like it’s not meant to be understood but to make a statement that we stand for “truth”. I rather feel that it’s too out there, up above a pedestal. Added to that are preachers acting like gatekeepers so that no one will rock the boat. Sure we are told that you can actually use a modern version for your quiet time or devotional but the damage is already done. Instilled in our minds that the modern translations are unreliable.

At this blog, we don’t get into the details of translation. One of the things we assume but don’t spend much time arguing for is that the Bible should be translated into modern languages so modern people can know it. Many English translations faithfully capture the meaning of the original text.

With that said, Gonzales brings a helpful perspective for those who can mistake high-falutin’ old language with clarity and faithfulness.

Check it out!

Do Bible Translations Matter?

By

Of course they do, otherwise most people reading this blog would have no access to the Scriptures. But Ryanvda has some excellent points to consider on the matter, as he answers a number of questions he regularly hears on the topic. On one level they really matter, and on another level they really don’t.

When we compare a bunch of good Bible translations, at that level, which one we pick does not really matter all that much. For example: If you compare the NIV with the ESV with the CSB, no outright winner emerges. We might have preferences (the CSB for me!), and those preferences might even stem from certain convictions – but for the most part, we are choosing between pretty healthy translations! 

Check it out!

The Best Bible Translation

By

Tommy Keene has another great reflection on his blog, this time about which English Bible is the best version to use. I concur with his conclusion:

There’s a very simple answer to that question: whatever translation your church uses.

In most cases, your default translation should be the one that the majority of people that you are talking to on a weekly basis are regularly using themselves. That doesn’t mean that it’s the only translation you should consult (we will talk about how to do that in a subsequent post), nor does it mean that you need to wave a “Best Translation Ever” flag every time you quote it, but it does mean that any exegetical argumentation you make should usually be grounded in that translation. It means this is the translation you are working from, and it means that if you cannot prove your point from this translation on its own merits then you might want to consider whether or not it is a point worth making.

He goes on to explain that there are many very good English translations. They’ve all got strengths, and they’ve all got flaws. And by “translations,” he’s referring to bona fide translations and not paraphrases.

Check out his reasoning for this conclusion.

Can You Trust Your Bible Study if You Don’t Know Hebrew and Greek?

By

Tommy Keene has a fabulous piece at his blog entitled “How do I do good exegesis if I don’t know Hebrew or Greek?” Perhaps you’ve been plagued by this question, wondering how far English translations can really take you.

This uncertainty causes some people to question any conclusion drawn from a Bible translation whatsoever. And it causes others to do foolish things when they use original language tools without knowledge of those original languages (for an example, see my post on how a little Greek can be a big distraction).

But it doesn’t have to be this way. Keene proposes an utterly sensible way forward. Here’s a taste:

Let’s say that you want to do some serious exegetical work on a passage of Scripture–perhaps you need to write an exegetical paper, or you’re running this week’s Bible Study, or counseling a client through a trauma, or answering your friend’s very specific and theological questions in a coffee shop–but you don’t know the original languages and therefore feel some lack of confidence when it comes to explaining what the biblical text really means.

Can you deeply and analytically study and reflect on a text of Scripture without making use of the original languages, and if so, how?

The question is particularly important if you’ve already been convinced, as I’ve argued previously, that you shouldn’t make definitive conclusions based on the original languages if you don’t possess a working knowledge of them. The present post began as a kind-of appendix to that argument, but on further reflection deserves a series itself.

“So I shouldn’t come to definitive exegetical conclusions from the Hebrew and Greek if I don’t know the original languages?” one might respond. “If that’s the case, is it still possible for me to mount an exegetical case for my position, and if so, how do I do that?”

The short answer: yes it’s very much possible, but it is vitally important that you account for the limitations of working with the text “in translation.” If you want to properly exegete a passage without the evidence provided by the Hebrew and Greek, you need to (1) trust a native language translation while simultaneously (2) being perpetually aware of its limitations.

The rest of this piece is well worth your time.

Check it out!

Behind the Scenes: My Bible Study Tools and Process

By

Xi Wang (2019), public domain

Studying the Bible is hard, holy work.

The tools we use for this work are not holy, but neither are they incidental. As we grow and mature we find different Bibles, different processes, and different translations that offer just the help we need at that time.

At the risk of navel gazing, my goal in this post is to let you into my Bible study workshop. I’ll describe the tools and process I use to prepare a small group Bible study.

This is one workshop among many. (My co-blogger Peter has written about this too.) My example is not meant for blind imitation, but I hope some readers may find some inspiration here. I should also note that my personal preferences are in flux. I have adopted some of my work flow within the past four months.

Tools

I use six main tools when studying the Bible and preparing for my small group.

  1. An audio Bible. In my early exposure to the passage I’m studying, I like to listen to the Bible. A lot.

  2. A markup Bible. My current markup Bible is a template of my own design. I copy the text from Bible Gateway into a Word document with fat margins (three inches on each side and two inches on the bottom). This gives me plenty of room for notes, arrows, and symbols.

  3. Colored pencils. I use cheap colored pencils to mark up the Bible text. Color coordination helps me locate repetition and connections.

  4. A Bible commentary. This one’s fairly self-explanatory.

  5. A journal and pen. I need to write in order to understand a Bible passage. I grab a nearby notebook or journal.

  6. Multiple Bible translations. I read the passage in multiple translations at Bible Gateway before my small group meets. (I make a point to consult the translations that my small group members prefer.)

My Process

With my tools in hand, these are the eight steps I take to prepare a small group Bible study lesson.

  1. Before I do anything, I pray. I am weak and full of sin, and I am approaching God’s holy word. I need his help!

  2. My first step is to print out my markup Bible. Simple enough.

  3. Next, I listen to and read the Bible passage a bunch. My goal is to discover and understand the structure of the passage. (I recently wrote about how helpful it was to read a passage 25 times.) I listen to or read the Bible passage at least ten times before I make a single mark on the page.

  4. Now it’s time for Bible study. Using the markup Bible, colored pencils, and a pen, I dive into the Observe-Interpret-Apply (OIA) Bible study method. I make a ton of observations on the paper, and these lead me to interpretive questions, which I also write next to the text. I use the right-hand margin of the paper for these notes.

  5. At this point I try to answer the interpretive questions from the text. I outline the passage according to the central ideas of each paragraph and land on an overall main point. I force myself to make notes about the passage before reading any commentaries. I also write down the primary questions I’d like to learn from the commentary.

  6. Next, I read the commentary. If I found the passage confusing, I’ll spend a lot of time interacting with the commentary. If it was an easier passage, I might skim the commentary or skip it altogether. I write notes from the commentary in the left-hand margin of my markup Bible.

  7. It’s time for more writing. I try to identify the main point of each section of the passage and then the overall main point. (This will use my work from step 5 as well as what I learned in step 6.) I list how my interpretation of the passage connects to Jesus and I think through application. Finally, I write a launching question for my small group.

  8. The last step is to create my leader’s notes for the small group meeting. This is a list of questions to help my friends discover the main point of the passage and discuss application. This is also when I read the passage in different translations, although I may do this earlier if the passage is especially thorny.

One Model Among Many

What I’ve outlined above is just one model among many. Some of it may work for you and some may not. And if what you’re doing already is working for you, you shouldn’t feel any need to change.

Don’t focus on the tools. Get and use the tools that will help you focus on the Bible.

Parts of the Bible are Not Inspired

By

Mike Leake makes a great point at his blog: Some parts of your Bible are not inspired by God.

Leake primarily has the punctuation in mind, as the original manuscripts had no punctuation.

…if we believe that the only original manuscripts are fully inspired, authoritative, and without error it means we do not believe the verse divisions or punctuation in your Bible falls under that category. Those were not present in either the original Hebrew or the Greek. Those were added much later.

Leake gives an example where shifting a comma might adjust the way we read a verse. Such discussions are not contrary to a belief in the inspiration or inerrancy of Scripture. Things such as comma placement are translators’ decisions. If you compare different translations, you’ll often see a variety of choices on such matter.

We also should keep in mind that verse divisions, red letters, paragraph breaks, footnotes, page formatting, and section headings are also translation or publication decisions, not components of the original manuscripts. If the context and train of thought of the text take you across some of these contrived boundaries, make sure you allow it to do so.

Check it out! 


Does the New Testament Misquote the Old Testament?

By

When you look up Old Testament passages quoted in the New Testament, you may notice that they don’t always line up exactly. For example, look at Isaiah 61:1-2, and then look at Luke’s quote of those verses in Luke 4:18-19:

The Spirit of the Lord GOD is upon me, because the LORD has anointed me to bring good news to the poor; he has sent me to bind up the brokenhearted, to proclaim liberty to the captives, and the opening of the prison to those who are bound; to proclaim the year of the LORD’s favor. (Is 61:1-2)

The Spirit of the Lord is upon me, because he has anointed me to proclaim good news to the poor. He has sent me to proclaim liberty to the captives and recovering of sight to the blind, to set at liberty those who are oppressed, to proclaim the year of the Lord’s favor. (Luke 4:18-19)

Michael S. Heiser explains the cause for discrepancy in this brief article. In short, the New Testament authors were typically working off a Greek translation of the Hebrew original. So our Old Testaments are translating the Hebrew directly into English. But when the NT quotes the OT, our English New Testaments are translating a Greek translation of the original Hebrew. The more languages involved in the conversion, the more adjustment gets made at each step.

For a helpful example, try the following experiment. Go to Google translate, and translate a normal English phrase (such as, “My shoulder hurts from throwing too much at baseball practice yesterday”) into any other language. Copy the result. Now paste that text and translate it back into English. After just those two steps, going into Danish and back, I got: “My shoulder hurts to throw too much of baseball practice yesterday.” The discrepancies from the original should not surprise us.

(I understand that going from English to Danish to English—two total languages—is not identical to going from Hebrew to Greek to English—three total languages. My point is just to show, to an audience that is likely unilingual, what happens when you have two steps in translation.)

This doesn’t mean we can’t trust translations. It just means we have to be reasonable and sensible about how language works. Remember: The original languages don’t function like a code to be cracked. They were real documents written by real people in ordinary languages. There’s no need for concern when languages function linguistically.

Heiser’s article helpfully explains this example. Check it out!

What the KJV Translators Can Teach Us About Bible Translation

By

At the LogosTalk blog, Mark Ward has posted some much-needed insights into Bible translation—directly from the quills of the KJV’s own translators. Would you believe they never expected the KJV to be very well-received? Or that they knew it wouldn’t be the ultimate English translation of the Bible? Or that they expected better and different translations to come along in future generations?

Ward first translates the original preface to the King James Version into modern English. Then he reflects on some lessons we can learn from it about Bible translation. In particular:

  1. People don’t like change.
  2. Watch out for petty objections.
  3. No translation is perfect.
  4. People must have the Bible.

I find especially helpful Ward’s comments on the way uninformed readers today love to make sweeping generalizations about what is the “best” Bible translation or “best” way to translate segments of the Bible:

The KJV translators anticipated waves of abuse from the great-great-great-great-great-great grandparents of today’s internet trolls. If there’s one line in the KJV preface that has come to mind over the years more than any other, it’s this from the second sentence: “Cavil, if it do not find a hole, will make one.” In other words, by sentence two the KJV translators are already complaining archly about the human propensity to let petty objections destroy something good.

Every Bible translation involves approximately 327 gazillion decisions about word choice, word order, textual criticism, assonance and consonance, meter, theology, tradition, typography, the current state of the target language, and numerous other factors. Someone, somewhere, is going to dislike just about every choice of any significance—particularly if it is an innovation overturning an established tradition. As the KJV translators say, “So hard a thing it is to please all, even when we please God best, and do seek to approve ourselves to every one’s conscience.”

I think (I hope) most Christian people have a sense that it is indiscrete to offer unsubstantiated opinions about pork futures in Australia (Market’s goin’ up ten points this year!) or the best fabric blend for patio table umbrellas (80% polyester, 10% elastane—that’s what I always say!). But somehow sweeping generalizations about the NIV (They’ve given in to gender politics!) or the ESV (They’ve given in to gender politics!) are permitted, even from people who’ve never read either side in significant translation debates.

It’s not wrong to have opinions about Bible translations: it’s wrong to speak opinions boldly about complex matters when you haven’t done the work to back them up. Internet commenters and cavil-hole makers of all sorts, be warned: the KJV translators are on to you.

If you can see any piece of yourself in Ward’s criticism, I highly commend his reflections to you.

Check it out!

Disclaimer: The Amazon link above is an affiliate link. If you click it and buy stuff, this blog will receive a small commission at no extra cost to yourself. If you choose not to click the link, we promise not to accuse you of giving in to gender politics.