Skip to main content

A History of Bible Translation: Introduction

People sometimes ask me when the work of Bible translation will be finished. I know why they’re asking. They want Jesus to come back. They want to know if they’ll still be alive when he does. The problem is that there always has been and always will be Bible translation going on. It isn’t the kind of task you start today, finish sometime next month, and then tick the box and move on. As cultures develop and communities change there is often a need for a new translation. Not only that, previous translations may seem to be out-of-date and irrelevant, or simply not very good.[1] Another question I get asked is why Bible translation takes so long? Why can’t we, in the age of advanced computers and globalisation, speed the process up? The problem is that computers aren’t human, and can’t produce a translation good enough for use by humans. Having said that humans are, after all, only human, and tend to make mistakes, albeit smaller ones than computers. When thinking about Bible translation most people compare it with translations like the New International Version, which had a ‘small’ committee of sixteen famous theologians working on it. Despite that, they took seventeen years to complete version one, and they’ve been producing new versions (of the New International Version) ever since. Comparing that with, at the other extreme, a couple of relatively untrained translators with only primary education working in a village, seems to be taking things too far. Those working with and advising such translators don’t know the language fluently, and the translators often don’t know Hebrew and Greek at all, nor do they know the background of the Bible well enough for the task in hand, therefore there isn’t one person on the project who knows everything they need to know in order to get the job done. The expression, ‘It takes two to tango’ comes to mind. It takes a team to translate. These days there is much more emphasis on training mother-tongue translators at workshops, and providing consultant help at both these and during visits to the team. Nevertheless, work often progresses slowly, and for good reasons.[2]

Few people know how complex the work of Bible translation is. One of the reasons I have written this book is to show how difficult it has been to put the Bible into local, spoken languages, and how much opposition to this process there has been. Many translators have died in the saddle, as it were, and not just from old age. Opposition has come from many quarters, including traditionally-minded church leaders who were quite happy with the status quo of having the priests in the know and the laity ignorant of Scripture. Putting the Scriptures into the modern spoken language of the day seemed sacrilege to them. Today opposition is more likely to come from other quarters – governments who are afraid to promote minority languages, or religious leaders who see Bible translation as a missionary activity, designed to cause the growth of local churches amongst communities all over the country. And so it is, as we shall hopefully see.



[1] Not good for the purpose they were intended for, that is. This is often because the translators have a hidden agenda, such as promoting the literary language, or competing with a neighbouring tribe. This is all very well, but we need translations that meet a felt need, not ones the boost someone’s ego.
[2] The NIV committee spent a lot of time deciding the parameters of the translation they were working on, key terms, and so on. Translations carried out in other parts of the world are often advised to leave decisions on key terms until later in the project, and keep such decisions as flexible as possible, as more data is needed to be able to make such hard choices.
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