Skip to main content

Why We Don't Start with Bible Translation

When a new programme starts it's often tempting to set it up as a Bible translation programme. Sometimes that's appropriate. In many cases, for a variety of reasons, it's not. This is because:
  • It's a minority language
  • People tend to be bi- or multi-lingual (at least if they live in towns, or have been educated)
  • They're oral preference
  • They're illiterate or semi-literate, or literate only in the language of wider communication
  • They aren't yet Christian believers
  • etc.
If any or all of the above are true, then it's good to start with language development and Scripture engagement rather than full-blown Bible translation, where you translate whole books of the Bible, and aim for a full Bible or New Testament + Psalms or Panoramic Bible. Sometimes the only reason for doing the latter is the kudos of the team, which is not a good reason. We're aiming for transformed communities, not team kudos!



The above flowchart shows the various stages. Note that the process does include translation ('phew' they all say!), but only as it is needed by Scripture engagement activity (stories, individual psalms, selections of both local and biblical proverbs, or whatever is needed). Sometimes there will be two teams, working in close cooperation, one team on SE, the other on LD and translation. In other cases there will be one team working on everything!

One good thing about having translation take place as and when needed is that the translation is going to be appropriate, used, and timely. Why spend years translating books that no one will read or engage with? Obviously we don't know the future, and it might be that the Lord works miracles so that many people come to know Him and start wanting to engage with Bible books in print format, but if that happens we can still work according to the above chart - it's just that the SE activities will use whole books instead of short portions.

This means that when we work on project briefs (there is a new form out at the moment), it's good to work on the LD and SE aspects of it before planning translation. Sometimes we plan translation first, so that there will be something for the local churches and SE workers to use, but this is back-to-front. If you haven't got any SE workers in your team (yet), then bring in a SE consultant, and local church leaders, when you're filling in the project brief form. This consultant can explain some of the audience issues, help you assess the felt needs, use participatory approaches with key partners (like church leaders, mission workers) and other key members of the audience, and so on.

When Paul preached to the Athenians (Acts 17) he didn't quote huge amounts of the Bible at them. In fact he rephrased biblical teaching in terms they understood, having started where they are with a great hook, and then finished his introduction by quoting one of their poets (v18)! Of course we probably have a summary of his actual sermon (we know he spoke at length on occasion), nevertheless, his actual meaty content is this:

“Therefore since we are God’s offspring, we should not think that the divine being is like gold or silver or stone—an image made by human design and skill. In the past God overlooked such ignorance, but now he commands all people everywhere to repent. For he has set a day when he will judge the world with justice by the man he has appointed. He has given proof of this to everyone by raising him from the dead.” Acts 17:29-31

This rephrasing of Scriptural truth is what local churches and SE workers do. The translation team can help by providing some portions of the Bible, ready for the SE workers and others to work with. The SE workers and so on will be aiming for transformation:

Some of the people became followers of Paul and believed. Acts 17:34

May that be true in parts of the world where you work!


LD: Language development
SE: Scripture engagement


Note added May 2024: In one local organisation in West Asia they decided to have the following steps in each of their projects:
  1. Relationship building
  2. Language & culture development
  3. Scripture engagement - including some limited Bible translation
  4. Full-blown Bible translation programme (if needed)
Step 4 was only implemented if there had been reception to step 3 resulting in believers beginning to desire the Scriptures in their own language (instead of in the national language or LWC, which were separate languages, in this case).

Comments

Popular posts from this blog

Asset Based Bible Translation (ABBT)

Many of you will have heard of asset-based community development (ABCD). How can Bible translation programmes be asset based, rather than deficit based? The best way to look at this is a comparison table: Deficit based Asset based Driven by outsiders Driven by the community Outside funding Community funded Done to meet a need Done to help the community grow Quality control done by a consultant Community checked and approved Control from outside-in Lead by stepping back Products not accepted? Products are accepted Little engagement Engagement with products Scientific Organic Not sustainable Sustainable Of course many translation programmes these days are neither one nor t'other, they are somewhere between these two extremes. Nevertheless, this illustrates a point, and shows that the current

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 it is the idea that seed was scatted by throwing it from a bag carried round the farmer's shoulder. This could be explained in the para-

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