It’s been a while since I wrote anything about the Gworog project. That’s largely because the project has faced personnel management issues and then a funding crisis, and then technical problems and they just haven’t had much for me to work on. I’ve also been pretty busy. But yesterday I had a (nother) meeting with the Gworog translation coordinator and 3 other linguists and literacy people to help come up with a plan for a really necessary meeting.
Perhaps to you “Community Orthography Consensus Meeting” doesn’t necessarily sound like the world’s most exciting knees-up but it could really be a matter of life and death.
I spent the last week working with the Koro Ashe Translation team again. They are based 3 hours to the west but we worked this week in Jos. (If you receive news and prayer requests from Wycliffe.org.uk you might have heard mention of them as they are supported in particular by some British churches.)
Some more interesting features of Ashe language came out in Luke 12, where Jesus says he has come not to bring peace but division. ‘Peace’ is expressed as ‘lying heart’ (that is, ‘restful mind’) which had me rather puzzled until it was explained. And where I was expecting a mother-in-law to pop up divided against her daughter-in-law, we ended up with ‘grandmother’. Ashe uses ingkoko ‘grandmother’ and then wife-of-her-son in this situation. That is one of those situations where it sounds odd in English, but everything is OK as far as the Ashe translation is concerned; they had done their job well. Merely translating the 3 English words ‘mother-in-law’ piece-by-piece would have been perplexing and meaningless and also not faithful to the original Greek.
Last week I made a discovery that surprised both me and the translation team I was working with: that the ‘bean pods’ the young prodigal of Luke 15 wanted to ‘fill himself with’ neither the generic food scraps we might think, or the sloppy grain-husk-porridge people feed pigs with here but were the fruit of a tree very familiar to us in West Africa.
To be fair we are not the first people to have made this discovery since the information was sitting in dictionaries and translators’ helps waiting to be uncovered, but the fact is we were all so sure we understood what the boy fed the pigs that we didn’t even consider it might be wrong. Continue reading Unexpectedly familiar: ‘Bean pods’ of Luke 15→
For my work as a Bible translation consultant (in training) I am reliant on using languages of wider communication (mostly English, with little bits of Hausa) to discuss the meaning of parts of the Bible and help translators check and improve their work. I am very aware of the dangers and pitfalls that this entails.
(Why is this a reality for me? I’m rather slow and poor at learning to speak languages, and work with far too many languages to attempt it.)
There is a real push amongst some Americans who want to “accelerate Bible translation” to resource and partner directly with local churches around the world and to cut out the missionary middle man, as it were. This is possible because more and more non-Western partners are able to communicate in Western languages of wider communication(English, Spanish, French).
David Rowbory, Translation Consultant in Training, SIL Nigeria
A paper presented at the 2015 Bible Translation Conference hosted by GIAL Dallas, Texas, 16-20 October relating to the sub-themes Technology and other Tools, Theory & Practice and Translator Training.
John Roberts has lamented the tendency of Bible translators to ignore lexicography until after a New Testament has been completed and printed. The consequence is that while the translation process necessarily reveals much of the lexical richness of a language, few dictionaries are ever finished and little of the effort of creating such a dictionary ends up benefitting the translation itself. It does tend to be a peculiar minority of people who attack the task of lexicography with relish, but I want to outline the many ways that a working dictionary can and should support better writing. Recent developments have eroded many of the difficulties which have hindered the development and use of dictionaries. There is no need to typeset a full dictionary before it is used; software-based dictionaries can be useful even when incomplete. Rather than throwing knowledge away, every translator or pioneer writer should see the dictionary as a place to store the riches of their language and conserve the fruit of their wrestling with the language. Mother-tongue translators need dictionaries too. Where a diverse range of community members contribute their knowledge of the language to make a good, growing, living dictionary it can provide consultants, reviewers and translators alike with a wider evidence base for their decisions than mere individual opinion. I survey recent developments that make dictionary development more achievable than ever before, and propose procedures for Bible translators to use and maintain a dictionary with examples from projects that have done this.
Some time I may get round to writing a paper on some cross-disciplinary lessons that Bible translators can learn from Software Engineering. (This is essentially trying to integrate my former and current career paths.)
My attention was caught by a slightly overblown headline on favourite irreverent geeky news site The Register: Most developers have never seen a successful project. Let me intersperse some quotes with some comments on how I see this relating to difficulties we face in the Bible translation world:
Most software professionals have never seen a successful software development project, continuous delivery evangelist Dave Farley said, and have “built careers on doing the wrong thing”.