4 Weeks of Checking 2 Books
For the last 4 weeks, CABTAL invited a translation consultant to check the work of 2 translation teams, the Ngomba and the Ngombale. Two weeks time were devoted to each team, which proved sufficient time to do the work. The Ngomba had checked the Gospel of John, and then the Ngombale the Gospel of Mark.
While I was able to take part in the checking of the Ngomba's John, I was not able to for the Ngombale. Nevertheless, we had the opportunity to get to know each other and discuss translation during breaks and prayer times, etc.
A few observations, of these checking sessions of John:
1. Technology Congruency
Updated and congruent technology is important to configure from the outset, between the consultant and the language team. At the outset, two different versions of Paratext were being used at first (and there are significant upgrades made in the recent version!), and this could have caused mayhem! Computer problems can wreak havoc on any translation.
2. Complete Text
Work through the text - the entire biblical text - in order, as well as the chapter headings (if present), and then the book summary at the end (if present). I can see where spot checks simply do not cut it in this important ministry of checking the accuracy of the translation.
3. Know the Language
Request/find information on basic discourse, orthographic, grammatical and linguistic features of the language before meeting with the team. For example, how many and what kind of verb tenses are used for the future? And do they have inclusive/exclusive pronouns? How do they introduce new characters in a narrative? Etc.
4. Pace Varies
Remember that the pace of checking will vary. The first day of checking always goes slower, as the team and consultant become familiar with each other (if this is the first book/work they are checking together). Additionally in most books, important translation decisions must be made early (e.g. John's 18 verse prologue) and that requires extra time.
5. Consistent Key Words
There are several constraints on working with key words, but one of them is that they can be translated differently in every place they surface. This gets to be quite challenging, but with the search technology on computers, this task is made easier (though not necessarily automatic!).
6. Prayer and Dependence on God
Start sessions not just with token prayer, but with earnest pleading that the Lord show up. Some consultants like to start the session with biblical meditation, which serves to orient the hearts and minds of people on the reason we are doing this linguistic work: glorifying God by enjoying Him and communing with Him over His Word.
7. Good Back Translation
Having both a good, written back translation before the consultant as well as a skilled, non-translation language group member to give a back translation on-the-spot are preferable. This helps to keep the translation honest, while also afford the consultant the opportunity to ask comprehension questions by virtue of how the back translation was given.
For the last 4 weeks, CABTAL invited a translation consultant to check the work of 2 translation teams, the Ngomba and the Ngombale. Two weeks time were devoted to each team, which proved sufficient time to do the work. The Ngomba had checked the Gospel of John, and then the Ngombale the Gospel of Mark.
While I was able to take part in the checking of the Ngomba's John, I was not able to for the Ngombale. Nevertheless, we had the opportunity to get to know each other and discuss translation during breaks and prayer times, etc.
A few observations, of these checking sessions of John:
1. Technology Congruency
Updated and congruent technology is important to configure from the outset, between the consultant and the language team. At the outset, two different versions of Paratext were being used at first (and there are significant upgrades made in the recent version!), and this could have caused mayhem! Computer problems can wreak havoc on any translation.
2. Complete Text
Work through the text - the entire biblical text - in order, as well as the chapter headings (if present), and then the book summary at the end (if present). I can see where spot checks simply do not cut it in this important ministry of checking the accuracy of the translation.
3. Know the Language
Request/find information on basic discourse, orthographic, grammatical and linguistic features of the language before meeting with the team. For example, how many and what kind of verb tenses are used for the future? And do they have inclusive/exclusive pronouns? How do they introduce new characters in a narrative? Etc.
4. Pace Varies
Remember that the pace of checking will vary. The first day of checking always goes slower, as the team and consultant become familiar with each other (if this is the first book/work they are checking together). Additionally in most books, important translation decisions must be made early (e.g. John's 18 verse prologue) and that requires extra time.
5. Consistent Key Words
There are several constraints on working with key words, but one of them is that they can be translated differently in every place they surface. This gets to be quite challenging, but with the search technology on computers, this task is made easier (though not necessarily automatic!).
6. Prayer and Dependence on God
Start sessions not just with token prayer, but with earnest pleading that the Lord show up. Some consultants like to start the session with biblical meditation, which serves to orient the hearts and minds of people on the reason we are doing this linguistic work: glorifying God by enjoying Him and communing with Him over His Word.
7. Good Back Translation
Having both a good, written back translation before the consultant as well as a skilled, non-translation language group member to give a back translation on-the-spot are preferable. This helps to keep the translation honest, while also afford the consultant the opportunity to ask comprehension questions by virtue of how the back translation was given.
No comments:
Post a Comment