À un certain point, l'équipe de traduction devra déterminer ce qu'elle doit traduire en premier ou, si elle a déjà fait une traduction, ce qu'elle doit traduire ensuite. Plusieurs facteurs doivent être pris en compte :
Parce que la traduction est une compétence qui se développe, il est prudent de commencer à traduire un contenu moins compliqué que les Écritures. De cette façon, les traducteurs peuvent acquérir de la compétence durant la traduction de documents moins difficiles.
Wycliffe Bible Translators a évalué la difficulté de la traduction des livres de la Bible. Dans leur indice de difficulté de traduction, les livres les plus compliqués à traduire reçoivent une cote de difficulté 5. Les livres les plus faciles à traduire reçoivent une cote de difficulté 1.
En général, les livres qui contiennent des termes et des idées plus abstraits, poétiques et théologiquement complexes sont plus difficiles à traduire alors que les livres qui sont plus narratifs et présentent des informations de manière simple sont plus faciles à traduire.
unfoldingWord has developed a set of 50 Bible stories assembled in a collection called Open Bible Stories. Though Open Bible Stories was not assessed according to this rating system, it should fall under Difficulty Level 1. We recommend that you begin by translating Open Bible Stories. There are many good reasons to start by translating Open Bible Stories:
* Open Bible Stories was designed to be easily translated.
* Most of it is simple narrative.
* Many difficult phrases and words have been simplified.
* It has many pictures to help the translator understand the text.
* Open Bible Stories is much shorter than the Bible or even the New Testament, so it can be quickly completed and distributed to the Church.
* Since it is not Scripture, Open Bible Stories removes the fear that many translators have of translating the Word of God.
* Translating Open Bible Stories before translating the Bible gives the translators experience and training in translation, so that when they translate the Bible, they will do it well. By translating Open Bible Stories, the translation team will gain:
> > * experience in creating a translation and checking team
> > * experience in doing the translation and checking process
> > * experience in using the Door43 translation tools
> > * experience in resolving translation conflicts
> > * experience in getting church and community participation
> > * experience in publishing and distributing content
* Open Bible Stories is a great tool to teach the church, evangelize the lost, and train the translators in what the Bible is all about.
You can work your way through the stories in whatever order that you want, but we have found that story number 31 is a good first story to translate since it is short and easy to understand.
Ultimately, the church needs to decide what they want to translate, and in what order. But we highly recommend starting your translation project with Open Bible Stories, for three reasons:
After translating Open Bible Stories, the church will need to decide if it would be more beneficial to start with how everything began (Genesis, Exodus) or with Jesus (New Testament gospels). In either case, we recommend starting Bible translation with some of the Difficulty Level 2 and 3 books (like Genesis, Ruth, and Mark). Finally, after the translation team has a lot of experience, then they can start translating Difficulty Level 4 and 5 books (like John, Hebrews, and Psalms). If the translation team follows this schedule, they will make better translations with far fewer mistakes.
See in Reader
