Subscribe: Apple Podcasts | Google Podcasts | Spotify | RSS
If the Bible is God’s word. . . which Bible should we read?
Welcome back to another Patterns of Truth podcast, and today we’re doing a “Catkiller,” a podcast where we dive into a topic related to the Bible to understand it as much as possible. (Don’t worry, no cats were harmed in making these podcasts; we like cats!)
Patricia and Peter are joined by Krista, Roy, and new guest Lars Kemmann—a software engineer who was instrumental in launching our site when we first started Patterns of Truth two years ago—in a discussion about Bible translations.
We know what you’re thinking. There are so many translations in the English language alone; how do I choose the right one? Aren’t they all saying the same thing in different ways?
Touching on everything from our guests’ go-to version for personal study (7:23) to chronological bibles (30:21), we attempt to bring a general overview on the topic. We could go in-depth with numerous details, but we’ll save those for another time!
As you listen along, you’ll hear Lars and Roy speak on a very general history of translations, what autographs and received texts are, the debate on how literal versus readable a translation should be (24:42), how culture and idioms affect our perceptions, and the bigger question:
Do most of the translations say the same thing? (28:52)
With so many translations out there and some that fall into a category of misappropriating God’s Word, what can we do? How does one go about understanding why there are different translations in the first place? Starting with simply reading our Bible’s preface (13:59) and prayerfully being aware of the deceptions and conspiracy theories that can cloud the waters, there are many ways to approach choosing a translation to read.
What did you think of our “Lost in Translation” podcast? Did you like Lars’ suggestion of doing follow-ups on more specific areas? Join the discussion! We would love to hear your thoughts, questions, and recommendations by either commenting below, contacting us, or submitting a question.