Skip to main content

A History of Bible Translation: Chapter 1 - The Greek Translation of the Old Testament

In the fourth century BC a king called Ptolemy the 2nd decided it would be a good idea to get the Hebrew Bible translated into Greek. He, as the story goes, appointed seventy translators who were told to sit in separate booths and work alone, and at the end of the process all seventy miraculously produced identical translations of the Hebrew Bible. What a way to check for accuracy![1] This translation became known as the Septuagint, and is one of the most reliable texts of the Old Testament we have, along with the Masoretic Text (10th century AD), and the Dead Sea Scrolls (1st century BC). Sometimes the Dead Sea Scrolls line up with the Septuagint rather than the Masoretic text, showing that the Septuagint represents an earlier and more reliable Hebrew text than the Masoretic text, despite the latter’s authority in the Judeo-Christian world.

The main reason to be thankful for this translation, is that it is the main text alluded to by the writers of the New Testament. By then Greek had established itself as the language of education in the Mediterranean region, despite Roman[2] military dominance, and the use of Aramaic by Jews in the home and on the street, and the use of Hebrew in the synagogues.[3] Why do I say ‘alluded to’ not ‘quoted’? Because the New Testament writers, like Winnie the Pooh,  often ‘used’ the Septuagint to mean what they wanted it to, not what it originally communicated in the Hebrew. They felt they had a divine calling to write, and in doing so were writing not just ordinary words, but Scripture. The world had changed after both the resurrection of Jesus from the dead, and destruction of the temple, and they had a message to share.

This means that the Bible we read is itself dependent on a translation of the older, Hebrew Bible, what we as Christians call the Old Testament. It uses that translation as a stepping stone to move into new territory. Therefore, some missiologists such as Lamin Sanneh have talked about the ‘translatability of Scripture’ – the Bible is inherently a translation, contains translated material, and focusses on a person, Jesus the Messiah, who himself became incarnate, involving a ‘translation’ from heavenly to human.


[1] The Soviet Union apparently used to use a word count to check translations were accurate. Perhaps they were from the same stable.
[2] The Romans spoke Latin, but were themselves educated in Greek.
[3] Most of the New Testament was written after the destruction of the temple in AD 70, so synagogues were the only meeting places for Jewish believers.
Labels:

Comments

Post a Comment

Popular posts from this blog

10 Reasons to Make Scripture Impact a Priority

This is a response to some recent posts about the importance of Bible translation in fulfilling the Great Commission. Yes, there is much truth in that, but more is needed. It really helps to have Scripture impact (or 'engagement') the top priority, the 'car' as it were, with translation the engine that sits beneath the bonnet. Not all drivers need to know all the details of the engine, but they need to be able to control the vehicle. The most important thing is to be able to get from A to B (see point 2), rather than knowing how the engine works. These are the ten reasons to make Scripture impact a priority: To help people flourish in their communities. There are all kinds of needs that need to be met for people to flourish. One is clean water. Another is good sanitation. Peace (lack of war), and freedom of religion. Access to education etc. etc. For a community to truly flourish they also need access to the Scriptures in a language (or languages) that they understand a...
Post a Comment
Read more

A Flow Chart for Bible Translation (a Relevance Theory Approach)

One of the current theories behind modern translation work is Relevance Theory. [1] Here is a flow chart that explains the process often used to produce a draft when using such an approach: *Make sure your translation committee makes the decision as to what kind of translation they want. A domesticated translation is one that submits to dominant values in the target language [2] whereas a foreignized translation is one that is happy to import foreign terms and ideas from Hebrew, Greek, or the language of wider communication such as the Greek term baptizo . The chart looks something like this: Text                                   Communicated Ideas                  Context A sower went out to sow  A farmer went out to sow grain   People scattered/threw seed etc. The text has very little information, but behind i...
Post a Comment
Read more

Asking the Right Questions in Bible Translation and Scripture Engagement Planning

If you want to get useful answers you have to ask the right questions. Do you agree? Yes, of course you do. In the Bible translation world we often ask a very narrow question when planning for the next stage of work: 'What would you like to see translated next?' Now, if you simply want to translate, and that's it, that question is fine, but what if you want to see some kind of result from your translation work? What if, for instance, you want to see transformation occur? Then a more powerful question to ask the community and positive stakeholders in the project would be: 'What kingdom goals would you like to see reached?' These kingdom goals should meet felt needs of the community - they should solve problems that are apparent to most or all in the community. See below on how those can be met. If that's too abstract, then try, 'What kinds of things, in your extended family, do you tend to worry about?' This will help establish some felt needs, from which...
7 comments
Read more