A few weeks ago, I wrote a series of meandering posts looking at the relationship between the Gospel and culture. However, since then, I’ve come up with a metaphor which I find helpful (and which almost certainly is not original) in thinking about how the Gospel, culture and language inter-relate.
When software developers produce new computer programs they have to localise them. That is they do stuff to the program so that it functions effectively in a new locality. At its most simple, localisation simply involves translating the menus and dialogue boxes into a new language. However, it can sometimes be more complex than when certain localities call alphabets that use complex characters or which may be written from right to left. But, and this is the key, localisation does not change the core of the computer program. Microsoft Windows looks pretty much the same in English, French or German and if you are familiar with one version you can find you way around another with a bit of guess work and a dose of trial and error. Localisation involves a change in how we relate to the program, but it doesn’t change the program itself. Translation is a much more drastic concept than localisation. A translated text looks very different to the original and if you don’t know both languages you will not be able to follow the translation. The Windows dialogues are translated and the words bear very little resemblance from one language to another: it is the fact that they are placed in familiar places that allows us to guess their meaning – not the words themselves.
When the Gospel moves into a new culture it is localised. The words: the Scriptures, songs and prayers may be translated and become almost unrecognisable, but the core of the Gospel remains unchanged. Andrew Walls in his wonderful paper, “The Gospel as prisoner and liberator of culture” suggests that there are five elements which are common to every Christian community across time and space, I’d suggest that these could be seen as the unchanging core of the Gospel (though others might argue).
- the ultimate significance of Jesus of Nazareth
- worship of the triune God, who is the same as the God of Israel
- the special use of the same Scriptures
- the special use of water, bread and wine
- an awareness on the part of each local group of believers that it is in some way continuous with ancient Israel as well as related to the new people of God that transcends time and space.
The way in which these realities are expressed can change drastically from one culture to another, but the realities themselves do not change. The task of the Bible translator then, is analogous to that of translating the menus in Windows (though far, far more complex, I hasten to add). We translate the text from one language to another, but the deeper reality, the experience of the Gospel in the life of the community and individual, mediated by the Spirit, remains unchanged.
It is possible, with a bit of guesswork, to find your way around a copy of Word or Windows in another language as long as you are prepared to make a few mistakes. In the same way, Christian communities in different languages and cultures have familiar elements which allow us to navigate through them. Bread and wine is bread and wine; whether served in small glasses and neat cubes or from a common cup and in huge hunks. It is even recognisably bread and wine when it isn’t actually bread and wine as such (grape juice, orange juice, coke… I’ve seen lots of variations). Because of the familiarity of the underlying core, it is possible for a Christian to experience Wall’s last point – the continuity of believers across time and space – even when it’s more or less impossible to understand a word the other believers are saying.
It could be said that the metaphor of localisation doesn’t add anything to our understanding of how the Gospel crosses cultures. After all, in Translation, the language changes, but the core message does not change. However, I think that the localisation concept is more helpful in that it highlights the difference between the unchanging core code and the translated interface, capturing some of the complexity of what happens when the Gospel moves into a new home.

4 replies on “A localised Gospel”
[…] has a go at exploring the metaphor of software localization as a way of exploring what happens in cross-cultural mission, and where it might differ from […]
[…] Eddie has a thought-provoking post on localization of the Gospel which Doug has responded to. Eddie is suggesting that the Gospel is localized in ways similar to the way software is localized in different languages and regions. It’s a great metaphor showing how on the surface what seems like a straight-forward transfer of function is actually a bit tricky in practice. Last year, I attended a localization conference in South Africa and one of the project managers of http://translators.co.za made a comment that really interested me. He said that many people assume they can just translate the various commands (File, Save, Edit) and they’ll be ready to go. But actually it is a lot more than that. There is a lot to do to get the program to run properly and then the far trickier task is finding the right words to use and also teaching users what they mean. You and I know what the word “Preview” means but how would you express that concept without using the word “preview?” And how would you explain to users of a piece of software what “preview” is and why they would want to do it? […]
Eddie, I’m not a bible translator like yourself but I can imagine the difficulties in trying to recognize the text in another language. Sometimes, if I had to use Windows in another language due to unavailability of the English version, I don’t know if I could navigate through a windows task because I still can’t read the language, but I can recognize the symbols/pictures.
I think Walls is right to the extent that the unchanging core of the Gospel are the symbols of bread and wine, the worship of God, scriptures, Jesus. Fortunately, these are symbols in the act of worship. But in the work of bible translation, there are absolutely no symbols or pictures to refer to, just difficult-to-recognize linguistic characters so I think bible translation is much more difficult than localization of software.