Scripture Engagement

Any translation goes through several stages before it is published: Drafting Team check Exegetical check Test & Review Lastly a consultant meets with the team and discusses any translation issues, making suggestion for changes before it is published. I'm now going to unpack why each stage is needed and what happens during each stage. Draft: the translator studies the passage, preferably in the original language, but if not, s/he compares several different versions in several different languages, and makes an oral draft (or sometimes they listen to several different audio versions instead). They do this by closing all their books, if they have any open, then speaking the passage into a recording device (like a smartphone). At least 2-3 verses are drafted at a time, then the translator listens to their recording, and checks they haven't left anything out. They might then keyboard it into their computer, using a program called ' Paratext '. Why do we dr

We are used to talking about Bible translation in terms of communication. Missiologists talk often talk about 'bridges' used for sharing the good news, which is also a communication metaphor - we have something we want to communicate, but we need a bridge, a way of expressing it, some kind of packaging for it, so that it communicates correctly (or hides whats inside the package, if we interpret the metaphor literally). This is a misunderstanding for two reasons: It is a false assumption that we have 'correctly' understood the good news. Unfortunately we have only understood a representation of the good news for our own culture . It doesn't matter how we package it, this will be misunderstood or irrelevant to the receptor culture (the primary audience in question). For instance, those in the minority world often explain the good news in terms of our guilt before a just God who has to punish sin, and that He, in Christ, took that punishment on our behalf to make us