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.
There are those who say that this can all be sped up in some way, but this usually involves missing out one or more of the above stages, which I hope you can see are all important for good quality translations. How many translators are needed? Probably 2-3 is an ideal number. If you have more then the discussions during the team check stage can take for ever, and lead to a lot of arguments about key terms issues. One organisation I know of is experimenting with using 30 or so translators, which is great for buy in to the translation, but a nightmare in terms of consistency.
The pastors/believers involved in the reviewing process may or may not be members of the translation committee, which meets periodically to decide issues like which portions/passages of Scripture to work on next, how to raise funds to pay the translators, testers, and other team members, and discuss important key terms issues. The exegetical advisor and/or consultant will have input regarding key terms, as its important to know the various ideas communicated in Hebrew/Greek before translating them.
I mentioned discourse analysis above. This is a study of the phrase order used in the language, and of various particles and words that might communicate something at a high level in the language. An example in English is the word 'well' when it begins a sentence. e.g.
Well...
An example in Hebrew is the word hine, often translated 'behold' in older translations. It is a discourse marker, highlighting something important about to be said (or seen).
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 draft orally? Because a) many cultures are oral in their preference (and much of Scripture was oral too) b) it results in a much more natural translation than other methods, and means that discourse analysis of the receptor language isn't so necessary.
- Team Check: the other translators listen to (or read) the translation and make comments on it. This helps make sure that the translators are all using the same key terms, and are reasonable consistent in terms of style and level of their translation. They also need to be on the same page in terms of when to insert footnotes, what kind of glossary entries are needed, and so on. In fact at this stage it's a good time to work on all those para-textual helps. The other translators can also help with naturalness of the translation at this stage, of course.
- Exegetical check: if the translator doesn't work from the original languages, then someone needs to carefully read the translation and compare it with the Hebrew/Aramaic/Greek Scriptures to make sure the translation is accurate and communicates the correct meaning. The exegetical advisor may also comment on any key terms and consistency issues, as in stage 2.
- Test & Review: the 3rd draft is sent to reviewers, who may be experts in the language or pastors/believers, for them to comment on the draft. This makes the translation more acceptable, both in terms of its orthography, and its theological appropriateness, as well as usefulness for the purpose it was intended for, whether use in church or outreach. It is also taken out into the community for 'testing' - this is where the translation is checked for clarity and comprehensibility. The more testing that can be done the better, and this is great Scripture engagement as well as being an important checking stage. Some hearers may comment on parts of the translation that sound unnatural, or where the translation is woodenly literal, and such problems can be fixed at this stage. The 4th draft is the final draft that is consultant checked...
There are those who say that this can all be sped up in some way, but this usually involves missing out one or more of the above stages, which I hope you can see are all important for good quality translations. How many translators are needed? Probably 2-3 is an ideal number. If you have more then the discussions during the team check stage can take for ever, and lead to a lot of arguments about key terms issues. One organisation I know of is experimenting with using 30 or so translators, which is great for buy in to the translation, but a nightmare in terms of consistency.
The pastors/believers involved in the reviewing process may or may not be members of the translation committee, which meets periodically to decide issues like which portions/passages of Scripture to work on next, how to raise funds to pay the translators, testers, and other team members, and discuss important key terms issues. The exegetical advisor and/or consultant will have input regarding key terms, as its important to know the various ideas communicated in Hebrew/Greek before translating them.
I mentioned discourse analysis above. This is a study of the phrase order used in the language, and of various particles and words that might communicate something at a high level in the language. An example in English is the word 'well' when it begins a sentence. e.g.
What do you think we should do tomorrow?
Well...
Comments
Post a Comment