See in Reader
Compare commits
1 Commits
master
...
FixIntroTo
| Author | SHA1 | Date |
|---|---|---|
Perry J Oakes
|
4f1405dcaf |
|
|
@ -0,0 +1 @@
|
|||
.idea
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
# Appendix to the Translation Topics
|
||||
|
||||
## Decisions concerning the Translation Topics
|
||||
|
||||
Many of the Translation Topics have links to other parts of the Wycliffe Associates Translation Manual. However only the topics that are addressed in either the Translation Notes or the Translation Words in this Translation Helps volume are included in this volume. Because of that, some of the links to other parts of the Translation Manual do not work. If you want to read those other parts of the Translation Manual, you can see them on Bible in Every Language (https://read.bibletranslationtools.org/u/WycliffeAssociates/en_tm/). The links that do not work are black, and those that work are some other color.
|
||||
|
||||
## How to use the Translation Topics
|
||||
|
||||
You can find topics in the Table of Contents at the beginning of this Translation Helps manual, or you can click on the links to topics in the Translation Notes or Translation Words.
|
||||
|
||||
Many of the topics have the following format.
|
||||
* Description - Use this to learn about the topic.
|
||||
* Reasons This is a Translation Issue - Use this to understand the translation issue.
|
||||
* Examples from the Bible - Use this to understand the topic better.
|
||||
* Translation Strategies - Use this to get ideas for how to translate a passage if the way it is communicated in the Unlocked Literal Bible would not be helpful in your language.
|
||||
* Examples of Translation Strategies Applied - Use this to see ways each of the strategies might be applied to a passage in the Bible. The bold text is the ULB and the text below it is an exmple of the strategy applied. Sometimes there is also some explanation with an example.
|
||||
|
||||
A box next to the description tells what question the page answers. It may also have links to other pages to read in order to understand the topic better. These links will not work if their pages are not also in this Translation Helps manual.
|
||||
|
||||
## Contributors to the Translation Topics
|
||||
- Christine Jarka, MSEd in Instructional Design
|
||||
- Henry Whitney, BA in Education
|
||||
- James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
|
||||
- Susan Quigley, MA in Linguistics
|
||||
- Tabitha Price, BA in Education
|
||||
- Bev Staley
|
||||
- Carol Brinneman
|
||||
- Jody Garcia
|
||||
- Kara Anderson
|
||||
- Kim Puterbaugh
|
||||
- Lizz Carlton
|
||||
|
||||
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
# About the Translation Manual
|
||||
|
||||
The Translation Manual is an open licensed manual on Bible translation. It teaches the basics of translation theory and a process for doing Bible translation, it provides practical helps for dealing with various translation issues, and it provides instruction and processes for checking translations.
|
||||
|
||||
The Translation Manual is intended to empower anyone, anywhere to equip themselves for creating high-quality translations of biblical content into their own language. The manual is designed to be highly flexible. It can be used in a systematic, in-advance approach, or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
|
||||
|
||||
The Translation Manual is written primarily for mother-tongue Bible translators who have had little or no prior training in translation. The English version of the manual is primarily for people who speak English as a second language. Because of this, we have tried to keep the writing style easy to understand.
|
||||
|
||||
**You can learn more about the Translation Manual** in the Appendix to the Translation Manual, rc://en_tm/00-tM_front&back/tM-3-Appendix.md. It has the following sections:
|
||||
* Decisions Concerning the Translation Manual
|
||||
* How to use the Translation Manual
|
||||
* Contributors to the Translation Manual (Fuller list)
|
||||
|
||||
## Viewing
|
||||
|
||||
To read or print the complete Translation Manual, see "Wycliffe Associates Translation Manual" on the "Translations" page of [Bible in Every Language](https://bibleineverylanguage.org/translations/) (https://bibleineverylanguage.org/translations/).
|
||||
|
||||
The Translation Manual is also integrated into BTT Writer and VMAST so that translators can have immediate access to it while translating. BTT Writer and VMAST are available on the Tools page of [Bible in Every Language](https://bibleineverylanguage.org/tools/) (https://bibleineverylanguage.org/tools/).
|
||||
|
||||
## Questions, comments, and suggestions
|
||||
We welcome questions, comments, and suggestions. You may send them to helpdesk@techadvancement.com or training_wa@wycliffeassociates.org.
|
||||
|
||||
## Contributors to the Translation Manual
|
||||
- Christine Jarka, MSEd in Instructional Design
|
||||
- Henry Whitney, BA in Education
|
||||
- James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
|
||||
- Perry Oakes, PhD in Old Testament, MA in Linguistics
|
||||
- Susan Quigley, MA in Linguistics
|
||||
- Tabitha Price, BA in Education
|
||||
- Door43 World Missions Community
|
||||
- Wycliffe Associates Staff
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
# Appendix to the Translation Manual
|
||||
|
||||
## Decisions concerning the Translation Manual
|
||||
|
||||
The Translation Manual is written primarily for mother-tongue Bible translators who have had little or no prior training in translation. The English version of the manual is primarily for people who speak English as a second language. Because of this we have tried to keep the writing style easy to understand.
|
||||
|
||||
## How to use the Translation Manual
|
||||
|
||||
The Translation Manual is intended to empower anyone, anywhere to equip themselves for creating high-quality translations of biblical content into their own language. The manual is designed to be highly flexible. It can be used in a systematic, in-advance approach, or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
|
||||
|
||||
A systematic, in-advance approach might involve reading sequentially through the sections of the manual: the Introduction, Translation Theory and Practice, Translation Topics, and Checking. A just-in-time learning approach might involve reading particular Translation Topics when directed to them by particular Translation Notes.
|
||||
|
||||
The Translation Topics section of the Translation Manual deals with grammar, figures of speech, writing styles, translating unknown ideas, and issues specific to Bible translation. Some of the pages describe a topic, tell why it is a translation issue, explain some examples from the Bible, and present translation strategies with examples of how the strategies might be applied. When translating a particular passage, translators will need to decide if any of the strategies would be appropriate for them to use. The examples of how strategies might be applied are meant to help translators learn how to apply the strategies. Translators are not expected to use any particular strategy.
|
||||
|
||||
|
||||
## Contributors to the Translation Manual
|
||||
{{manifest}}
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
# Introduction to the Translation Topics
|
||||
|
||||
"Translation Topics" is a part of the the Wycliffe Associates Translation Manual. It deals with translation issues that arise because of grammar, discourse, figures of speech, and ideas that maybe unknown to speakers of the target language. It also deals with issues that are particularly relevant to Bible translation. Many of the topics include examples from the Bible, strategies for dealing with the issues, and examples of how those strategies might be applied.
|
||||
|
||||
The topics that are included in this set of Translation Resources are ones that are addressed in either the Translation Notes or the Translation Words for this book of the Bible.
|
||||
|
||||
**You can learn more about the Translation Manual** in the Appendix to the Translation Manual, rc://en_tm/00-tM_front&back/tM-3-Appendix.md. It has the following sections:
|
||||
* Decisions Concerning the Translation Manual
|
||||
* How to use the Translation Manual
|
||||
* Contributors to the Translation Manual (Fuller list)
|
||||
|
||||
## Viewing
|
||||
|
||||
To read or print the complete Translation Manual, see "Wycliffe Associates Translation Manual" on the "Translations" page of [Bible in Every Language](https://bibleineverylanguage.org/translations/) (https://bibleineverylanguage.org/translations/).
|
||||
|
||||
The Translation Manual is also integrated into BTT Writer and VMAST so that translators can have immediate access to it while translating. BTT Writer and VMAST are available on the Tools page of [Bible in Every Language](https://bibleineverylanguage.org/tools/) (https://bibleineverylanguage.org/tools/).
|
||||
|
||||
## Questions, comments, and suggestions
|
||||
We welcome questions, comments, and suggestions. You may send them to helpdesk@techadvancement.com or training_wa@wycliffeassociates.org.
|
||||
|
||||
## Contributors to the Translation Topics
|
||||
- Christine Jarka, MSEd in Instructional Design
|
||||
- Henry Whitney, BA in Education
|
||||
- James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
|
||||
- Perry Oakes, PhD in Old Testament, MA in Linguistics
|
||||
- Susan Quigley, MA in Linguistics
|
||||
- Tabitha Price, BA in Education
|
||||
- Door43 World Missions Community
|
||||
- Wycliffe Associates Staff
|
||||
|
|
@ -24,4 +24,3 @@ The licensor cannot revoke these freedoms as long as you follow the license term
|
|||
You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
|
||||
|
||||
No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
|
||||
|
||||
|
|
|
|||
22
README.md
22
README.md
|
|
@ -1,30 +1,31 @@
|
|||
# English Translation Manual
|
||||
# English translationAcademy
|
||||
|
||||
## Overview
|
||||
|
||||
Translation Manual is intended to enable anyone, anywhere to equip themselves so that they will be able to make high-quality translations of biblical content into their own language. Translation Manual is designed to be highly flexible. It can be used in a systematic, in-advance approach or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
|
||||
translationAcademy is intended to enable anyone, anywhere to equip themselves so that they will be able to make high-quality translations of biblical content into their own language. translationAcademy is designed to be highly flexible. It can be used in a systematic, in-advance approach or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
|
||||
|
||||
Translation Manual was developed by the [Door43 World Missions Community](https://door43.org) in conjunction with [Wycliffe Associates](http://www.wycliffeassociates.org/). The entire project is made
|
||||
translationAcademy was developed by the [Door43 World Missions Community](https://door43.org) in conjunction with [Wycliffe Associates](http://www.wycliffeassociates.org/). The entire project is made
|
||||
available under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0), see the [LICENSE](https://git.door43.org/Door43/en_ta/src/master/LICENSE.md) file for more information.
|
||||
|
||||
Please use the [issue queue](https://git.door43.org/Door43/en_ta/issues) to provide feedback or suggestions for improvement.
|
||||
|
||||
## Resources
|
||||
|
||||
If you want to download English Translation Manual to use, go here: https://unfoldingword.org/academy/. It is also included in [tS](http://ufw.io/ts) and [tC](http://ufw.io/tc).
|
||||
If you want to download English translationAcademy to use, go here: https://unfoldingword.org/academy/. tA is also included in [tS](http://ufw.io/ts) and [tC](http://ufw.io/tc).
|
||||
|
||||
## Contributing or Translating
|
||||
|
||||
### Contributions are always welcomed.
|
||||
The Translation Manual is a collaborative work between several organzations. We seek those that would like to contribute to the work. Presently there is an Oversight Team that is responsible for the maintenance of the content. The members of this team represent various organizations and are experienced Biblical Scholars, Linguists and Bible Translators.
|
||||
The translationAcademy is a collaborative work between several organzations. We seek those that would like to contribute to the work. Presently there is an Oversight Team that is responsible for the maintenance of the content. The members of this team represent various organizations and are experienced Biblical Scholars, Linguists and Bible Translators.
|
||||
All contributions will be reviewed by the Oversight Team.
|
||||
|
||||
#### Submit an Issue
|
||||
Submitting an issue is the preferred way to let the Oversight Team know of errors in the content. When you find an error, please note where the error is, if possible copy the error, open an [Issue](https://git.door43.org/Door43/en_ta/issues), paste in the error, then offer a correction, and then submit the Issue.
|
||||
|
||||
#### Pull Request
|
||||
To contribute to the content of the Translation Manual please fork a copy of the repository, make your changes and then submit a Pull Request to the repository.
|
||||
The Oversight Team will then review the pull request and then decide on the merging of the content into the master repository.
|
||||
To contribute to the content of the translationAcademy please fork a copy of the repository, make your changes and then submit a Pull Request to the repository.
|
||||
The Oversight Team will then review the PR and then decide on the merging of the content into the master repository.
|
||||
|
||||
|
||||
### Explanation of the content file layout
|
||||
|
||||
|
|
@ -54,7 +55,7 @@ Following the YAML header is the body of the article, which uses a format called
|
|||
|
||||
Images that are included in tA should be no more than 600px wide.
|
||||
|
||||
### Instructions for translating Translation Manual
|
||||
### Instructions for translating translationAcademy
|
||||
|
||||
__The instructions for translating `meta.yaml` (metadata) and `toc.yaml` (table of contents) are included in the header of those files.__
|
||||
|
||||
|
|
@ -76,7 +77,7 @@ You can translate the "text to display" inside the square brackets but not the w
|
|||
|
||||
You are free to add additional pages. In order for the new page to be included when tA is published, all of the following conditions need to be satisfied:
|
||||
|
||||
1. You must create a directory in one of the manual directories (like the translate directory) that has the short name of the module you want to write. For example, to create a new module on "testing" in the Translation Manual, you will want to put the file in "translate/testing/01.md".
|
||||
1. You must create a directory in one of the manual directories (like the translate directory) that has the short name of the module you want to write. For example, to create a new module on "testing" in the Translation Manual, you will want to put the file in "translate/testing/01.md".
|
||||
|
||||
1. The file must be included in the table of contents, `toc.yaml` for the appropriate manual.
|
||||
|
||||
|
|
@ -86,5 +87,4 @@ You are free to add additional pages. In order for the new page to be included w
|
|||
|
||||
## Historical
|
||||
|
||||
If you would like to see the deprecated tranlsationAcademy pages in DokuWiki, go to https://dw.door43.org/en/ta. You can still see the workbench pages at https://dw.door43.org/en/ta/workbench.
|
||||
|
||||
If you would like to see the deprecated tranlsationAcademy pages in DokuWiki, go to https://dw.door43.org/en/ta. You can still see the workbench pages at https://dw.door43.org/en/ta/workbench.
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -1,2 +0,0 @@
|
|||
Acceptable Style
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Accuracy Check
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Accurate Translation
|
||||
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
|
||||
### An Accurate Translation
|
||||
|
||||
It is very important to make sure that the new translation is accurate. Those who have been chosen to check the translation for accuracy have the responsibility to make sure that it communicates the same meaning as the original writer intended and expected to communicate.
|
||||
|
||||
For instructions on how to do this, go to [Accuracy Check](../accuracy-check/01.md), and follow the steps in the section under the heading "All Levels."
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
Is the translation accurate?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Accurate Translation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Appropriate Alphabet
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
|
||||
### The Alphabet for the Translation
|
||||
|
||||
As you read the translation, ask yourself these questions about the way words are spelled. These questions will help to determine if an appropriate alphabet has been chosen to represent the sounds of the language and if words have been written in a consistent way so that the translation will be easy to read.
|
||||
|
||||
1. Is the alphabet suitable to represent the sounds of the language of the new translation? (Are there any sounds that make a difference in meaning but have to use the same symbol as another sound? Does this make the words hard to read? Can additional marks be used to adjust these letters and show the differences?)
|
||||
1. Is the spelling used in the book consistent? (Are there rules that the writer should follow to show how words change in different situations? Can they be described so others will know how to read and write the language easily?)
|
||||
1. Has the translator used expressions, phrases, connectors, and spellings that will be recognized by most of the language community?
|
||||
|
||||
If there is something about the alphabet or spelling that is not right, make a note of that so that you can discuss it with the translation team.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
Does the translation use an appropriate alphabet?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Appropriate Alphabet
|
||||
|
||||
|
|
@ -1,134 +0,0 @@
|
|||
|
||||
During the first few days of a MAST workshop, translation teams are guided through the process of developing an authentic assessment rubric for their translation project. Below are the instructions for creating this rubric, which then guides the checking process throughout the project.
|
||||
|
||||
1. Ask the translation team to choose a leader/representative of their language group to manage the rubric building process. Also look for an individual who is able to translate this rubric into English (it is possible to need double translation, first into the national language and then into English).
|
||||
2. Ask the individuals on the team the following (each one should work on this on their own first.)
|
||||
* What is a good translation?
|
||||
* List at least ten qualities. Even twenty if you want to stretch.
|
||||
* Work together as a team to make one list that includes all the items from each individual’s list. Combine qualities that are the same and develop one master list of at least 10 qualities that everyone agrees on. The chosen leader will guide this process.
|
||||
3. If everyone is new to this process, the team can refer to v-raft.com to review a sample rubric. Compare your rubric with the sample. Are elements missing from yours that need to be added? Are there extra elements you may not need to keep? After discussing these you are ready to move to step four.
|
||||
If a leader who has participated in this process before is available, he will review the team's rubric, determine if anything is missing, and ask questions to lead the group toward discovering and adding those traits. Some sample questions are:
|
||||
* If no one says that key words need to be translated accurately, ask "When you look at the language of scripture, what are some of the things that give scripture a strong sense of accuracy?" Keep asking until they express the "important words" (in some form) and then ask "should those be checked?"
|
||||
* If no one says that names need to be translated in a consistent way (ie—Jesus, Son of God, Jesus Christ, Christ Jesus), ask "what do you think about the different names of Jesus—are those important to be translated consistently with a good source text?"
|
||||
4. Take the one group rubric and do the rest of the following steps as a team.
|
||||
5. Define each of those items (verbally, and then record them). Each definition should be clear enough that anyone from that language group could utilize the rubric and understand the traits of quality.
|
||||
6. Next, you are going to have a discussion of each of the traits on the list and ask:
|
||||
* How can you measure those items?
|
||||
* Express that each of these items needs to be put into a "yes or no" type of measure—how can you phrase each quality item into a "yes/no" result?
|
||||
7. Next ask the group: How can you test those items? In other words, if a person who speaks the language were to later check a translated chapter, could they pick up that chapter, take the rubric and score each of the assessment elements listed?
|
||||
8. Finally, ask the group the following:
|
||||
* How can you testify to those items if anyone at any time asked you the question "is this of good quality?"
|
||||
* If all of these traits in your translation were assessed and proved out as a "yes" within each chapter, would you have a good quality translation?
|
||||
10. When possible, translate the rubric into English and share it at [v-raft.com](https://v-raft.com).
|
||||
|
||||
Below you will see a sample rubric created by following the steps above:
|
||||
|
||||
### Sample Rubric
|
||||
|
||||
####List Ten or More Characteristics (up to 20 if you can).
|
||||
Accurate
|
||||
Community Oriented
|
||||
Clear
|
||||
Grammatically consistent
|
||||
Natural
|
||||
Faithful to Original Languages
|
||||
Authoritative
|
||||
Historical
|
||||
Equal
|
||||
Acceptable
|
||||
Trustworthy
|
||||
Has Appropriate Familial Terms
|
||||
Culturally Relevant
|
||||
|
||||
#### Combine or Condense the Characteristics. Then define them well.
|
||||
|
||||
**Accurate**
|
||||
1. All key words are present (names, places, transitional statements, time identifiers
|
||||
2. Key words are translated accurately
|
||||
3. Nothing is added or missing from the text
|
||||
4. The text reflects the author's intended meaning
|
||||
|
||||
**Clear**
|
||||
1. The text is understood by a wide range of audiences.
|
||||
2. The text uses common language.
|
||||
3. Uses proper language structures (word placement, tenses, sentence structure)
|
||||
4. Proper punctuation is used.
|
||||
|
||||
**Natural**
|
||||
1. The text sounds like how we speak. It uses common language
|
||||
2. Sounds beautiful and academic
|
||||
3. The text is efficient and effective in its communication
|
||||
|
||||
**Faithful**
|
||||
1. We're not trying to add in theological, denominational or political meaning
|
||||
2. True to the source text
|
||||
3. Uses proper familial terms
|
||||
|
||||
**Authoritative**
|
||||
1. The text reflects original meaning of the source texts
|
||||
2. The text is confirmed by proper intermediary biblical source texts
|
||||
3. The supporting texts are acceptable
|
||||
|
||||
**Historical**
|
||||
1. Lines up with archeology
|
||||
2. The text is supported by secular documents
|
||||
3. Depicts historical facts accurately
|
||||
|
||||
**Equal**
|
||||
1. The text reflects the author's original intent
|
||||
2. Genres are the same (poetry, commands, encouragement, story telling)
|
||||
3. The text uses equal political terminology
|
||||
4. The tone and purpose are clear and identifiable
|
||||
|
||||
Notice that in condensing the qualities, some of the items on the list are combined so there are no longer 10 seperate qualities.
|
||||
|
||||
#### Turn each definition into a “yes/no” Measurement.
|
||||
|
||||
**Accurate**
|
||||
1. Are all key words present? (names, places, transitional statements, time identifiers)
|
||||
2. Are all key words translated accurately?
|
||||
3. Was anything added or subtracted from the meaning of the text?
|
||||
4. To the best of your ability to determine, does the text communicate the author's intended meaning?
|
||||
|
||||
**Clear**
|
||||
1. Are you able to understand and comprehend what you are reading/hearing?
|
||||
2. Are there too many or two few words that make it confusing?
|
||||
3. Is the grammatical structure (word placement, tense and sentence structure) appropriate?
|
||||
4. Is proper punctuation used?
|
||||
5. Can the young and the old understand it?
|
||||
|
||||
**Natural**
|
||||
1. Does the translation read/sound like someone would speak?
|
||||
2. Does the translation sound beautiful to you when it is read?
|
||||
3. Are there too many or two few words that make it confusing?
|
||||
4. Are all words and phrases common?
|
||||
|
||||
**Faithful**
|
||||
1. We're not trying to add in theological, denominational or political meaning Does this translation avoid political bias?
|
||||
2. Does this translation avoid theological bias?
|
||||
3. Does this translation avoid social and cultural bias?
|
||||
4. Is this translation true to the source text, not denominational inclination?
|
||||
5. Are literal familial terms used for Son of God and God the Father?
|
||||
|
||||
**Authoritative**
|
||||
1. Does the meaning of the translated content reflect what is understood of the original language texts?
|
||||
2. Is the text confirmed by intermediary source texts and biblical content?
|
||||
3. Were the supplementary materials used to guide translation respectable and accepted?
|
||||
|
||||
**Historical**
|
||||
1. Is the text supported by known facts of history, archeology, etc?
|
||||
2. Are historical events and facts communicated accurately?
|
||||
3. Are people and places accurately identified, transliterated, or defined?
|
||||
4. Are steps taken to create clarity for unknown biblical terms (weights, units, financials, etc)?
|
||||
|
||||
**Equal**
|
||||
1. Is the meaning the same and are the same implications drawn in this translation as they are in the source text?
|
||||
2. Is what type of genre each chapter/book is able to be determined? (poetry, commands, encouragement)
|
||||
3. Are political terms/expressions of authority/positions clearly articulated?
|
||||
4. Are the tone and purpose clear and identifiable?
|
||||
|
||||
|
||||
The questions are designed as yes/no. If the answer is yes 70% of the time, but no the other 30%, then the answer is "No". The question has to be answered yes 100% of the time to be "Yes". In this way areas that need attention (even down to the minute details) will get reviewed and edited.
|
||||
|
||||
View additional sample rubrics at v-raft.com.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
How do we design a rubric for the quality of our translation?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Designing a Rubric for Bible Translation Quality
|
||||
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
### Affirmation by Translation Team
|
||||
|
||||
The intent of this level is to affirm that the translators have taken steps to ensure the accuracy of their translation and that the translation is in agreement with standard Christian doctrine. Publishing content at this level makes it available to members of the language community and provides an open invitation (implied or direct) to them to suggest improvements to the translation.
|
||||
|
||||
To achieve this level, the translation team asserts that the [Statement of Faith](../../intro/statement-of-faith/01.md) is an accurate reflection of their own beliefs and that the translated content is also in harmony with it.
|
||||
|
||||
The translation team asserts that the translation has been done in accordance with the MAST process and that they have made use of available exegetical and translation checking resources in the translation process, including the Translation Notes and Translation Words.
|
||||
|
||||
An explanation of the steps followed during level one checking is available at [Level One Check](../level1/01.md).
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
What is affirmation level one?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Affirmation Level One
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
What is affirmation level two?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Affirmation Level Two
|
||||
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
|
||||
### Affirmation by Church Leadership
|
||||
|
||||
The intent of this level is to affirm that the translation agrees with the intent of the original texts and with the sound doctrine of the Church historic and universal.
|
||||
|
||||
To achieve this level, the translation team will work with the highest leadership of the church that speaks the language to review the Scripture. It is best if these leaders represent as many of the major groups of churches (networks and denominations) that exist in the language community as possible. Level 3 is thus achieved by the mutual agreement of the leadership of multiple church networks.
|
||||
|
||||
The translation team will edit the translation so that the leadership of these church networks affirm that it is an accurate translation and will be accepted by their church fellowships.
|
||||
|
||||
The authentic assessment rubric will be used to guide this process. Specific steps for level 3 checking are available at [Level Three Check](../level3/01.md).
|
||||
|
||||
Level 3 is completed when the translation has been thoroughly checked and affirmed by the leadership (or their delegates) of at least two church networks.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
What is affirmation level three?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Affirmation Level Three
|
||||
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
|
||||
### Explanation
|
||||
|
||||
The church in each people group has the authority to decide for themselves what is and what is not a good quality translation of the Bible in their language. Authority to check and validate a Bible translation (which is constant) is separate from capacity, or the ability to carry out the process of checking a Bible translation (which can be increased). The authority for determining quality belongs to the church, independent of their current ability, experience, or access to resources that facilitate the checking of Bible translations. So while the church in a language group has the authority to check and validate their own Bible translation, tools and resources available on bibleineverylanguage.org are designed to ensure that the church also has the capacity to check the quality of their Bible translation using an excellent process.
|
||||
|
||||
This model proposes a layered approach to affirming the quality of a translation, designed to reflect three general levels of church authority within a people group:
|
||||
|
||||
* [Authority Level 1](../authority-level1/01.md): the church-based translation team
|
||||
* [Authority Level 2](../authority-level2/01.md): the leaders of the local church along with other members of the language community
|
||||
* [Authority Level 3](../authority-level3/01.md): the leaders of multiple local churches, a network of churches, or multiple evangelical denominations
|
||||
|
||||
Every check on the translation will be guided by the authentic assessment rubric that is created by the translation team to express the essential qualities of a good translation.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Checking Authority and Process
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Church Leader Check
|
||||
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
|
||||
### How to do a Church Leader Check
|
||||
|
||||
After the translation has been checked by community members for clarity, it will be checked by a group of church leaders for accuracy. This group must consist of at least three church leaders who are native speakers of the target language, and who understand well one of the languages in which the source text is available. They should not be related to, or otherwise closely connected with, the translation team. Usually these reviewers will be pastors. These church leaders should represent the different church networks in the language community. We recommend that the group includes church leaders from three different church networks, if the community has that many.
|
||||
|
||||
These reviewers should follow these steps:
|
||||
|
||||
1. Read the [Translation Guidelines](../../intro/translation-guidelines/01.md) to make sure that the translation is in agreement with both of those as they review the translation.
|
||||
1. Answer the questions about the translator or translation team that are located at [Translator Qualifications](../../translate/qualifications/01.md).
|
||||
1. Verify that the translation has been done in a style that is acceptable to the intended audience by asking the questions at [Acceptable Style](../acceptable/01.md).
|
||||
1. Verify that the translation accurately communicates the meaning of the source text by following the guidelines at [Accuracy Check](../accuracy-check/01.md).
|
||||
1. Verify that the translation is complete by following the guidelines at [Complete Translation](../complete/01.md).
|
||||
1. After you have reviewed several chapters or one book of the Bible, meet with the translation team and ask about each problem. Discuss with the translation team how they might adjust the translation in order to fix the problems. Make plans to meet again with the translation team at a later time, after they have had time to adjust the translation and test it with the community.
|
||||
1. Meet again with the translation team to verify that they have fixed the problems.
|
||||
1. Affirm that the translation is good. See [Level 2 Affirmation](../good/01.md) to do that on the Level Two Affirmation page.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
How can the church leaders help improve the translation?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Church Leader Check
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Clear Translation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Language Community Evaluation Questions
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Complete Translation
|
||||
|
||||
|
|
@ -1,232 +0,0 @@
|
|||
acceptable:
|
||||
recommended:
|
||||
- alphabet
|
||||
- complete
|
||||
dependencies:
|
||||
- clear
|
||||
- natural
|
||||
- church-leader-check
|
||||
accuracy-check:
|
||||
recommended:
|
||||
- level2
|
||||
- language-community-check
|
||||
- church-leader-check
|
||||
- other-methods
|
||||
- guidelines-accurate
|
||||
dependencies:
|
||||
- level1
|
||||
- guidelines-accurate
|
||||
- important-term-check
|
||||
accurate:
|
||||
recommended:
|
||||
- complete
|
||||
- accuracy-check
|
||||
- guidelines-accurate
|
||||
dependencies:
|
||||
- alphabet
|
||||
- church-leader-check
|
||||
alphabet:
|
||||
recommended: []
|
||||
dependencies:
|
||||
- acceptable
|
||||
- translate-alphabet
|
||||
authority-level1:
|
||||
recommended:
|
||||
- authority-level2
|
||||
- level1
|
||||
dependencies:
|
||||
- authority-process
|
||||
authority-level2:
|
||||
recommended:
|
||||
- authority-level3
|
||||
dependencies:
|
||||
- authority-level1
|
||||
authority-level3:
|
||||
recommended:
|
||||
- level3
|
||||
- level1
|
||||
dependencies:
|
||||
- authority-level2
|
||||
authority-process:
|
||||
recommended:
|
||||
- authority-level1
|
||||
- level1
|
||||
dependencies:
|
||||
- goal-checking
|
||||
church-leader-check:
|
||||
recommended:
|
||||
- accuracy-check
|
||||
- accurate
|
||||
- good
|
||||
dependencies:
|
||||
- level2
|
||||
clear:
|
||||
recommended:
|
||||
- acceptable
|
||||
- natural
|
||||
- guidelines-clear
|
||||
- language-community-check
|
||||
dependencies:
|
||||
- level2
|
||||
community-evaluation:
|
||||
recommended:
|
||||
- church-leader-check
|
||||
- self-assessment
|
||||
dependencies:
|
||||
- language-community-check
|
||||
- other-methods
|
||||
- writing-decisions
|
||||
complete:
|
||||
recommended:
|
||||
- self-assessment
|
||||
- good
|
||||
dependencies:
|
||||
- accurate
|
||||
formatting:
|
||||
recommended:
|
||||
- alphabet
|
||||
- spelling
|
||||
- punctuation
|
||||
dependencies:
|
||||
- vol2-things-to-check
|
||||
goal-checking:
|
||||
recommended:
|
||||
- intro-checking
|
||||
- authority-process
|
||||
dependencies:
|
||||
- intro-levels
|
||||
good:
|
||||
recommended:
|
||||
- self-assessment
|
||||
- level3
|
||||
dependencies:
|
||||
- complete
|
||||
headings:
|
||||
recommended:
|
||||
- community-evaluation
|
||||
dependencies:
|
||||
- acceptable
|
||||
- punctuation
|
||||
- verses
|
||||
important-term-check:
|
||||
recommended:
|
||||
- accuracy-check
|
||||
dependencies:
|
||||
- level1
|
||||
- peer-check
|
||||
intro-check:
|
||||
recommended:
|
||||
- intro-checking
|
||||
dependencies:
|
||||
- translate-manual
|
||||
intro-checking:
|
||||
recommended:
|
||||
- intro-levels
|
||||
dependencies:
|
||||
- intro-check
|
||||
intro-levels:
|
||||
recommended:
|
||||
- intro-levels
|
||||
- level1
|
||||
dependencies:
|
||||
- intro-checking
|
||||
language-community-check:
|
||||
recommended:
|
||||
- natural
|
||||
- other-methods
|
||||
- writing-decisions
|
||||
- community-evaluation
|
||||
dependencies:
|
||||
- level2
|
||||
level1:
|
||||
recommended:
|
||||
- statement-of-faith
|
||||
- translation-guidelines
|
||||
- accuracy-check
|
||||
dependencies:
|
||||
- intro-levels
|
||||
level1-affirm:
|
||||
recommended:
|
||||
- level2
|
||||
dependencies:
|
||||
- statement-of-faith
|
||||
- translation-guidelines
|
||||
- level1
|
||||
- accuracy-check
|
||||
level2:
|
||||
recommended:
|
||||
- language-community-check
|
||||
- church-leader-check
|
||||
- self-assessment
|
||||
- good
|
||||
dependencies:
|
||||
- intro-levels
|
||||
- accuracy-check
|
||||
level3:
|
||||
recommended:
|
||||
- level3-questions
|
||||
- self-assessment
|
||||
dependencies:
|
||||
- intro-levels
|
||||
- level2
|
||||
- accuracy-check
|
||||
level3-approval:
|
||||
recommended: []
|
||||
dependencies:
|
||||
- level3
|
||||
- level3-questions
|
||||
- self-assessment
|
||||
level3-questions:
|
||||
recommended:
|
||||
- accuracy-check
|
||||
- level3-approval
|
||||
- self-assessment
|
||||
dependencies:
|
||||
- level3
|
||||
natural:
|
||||
recommended:
|
||||
- acceptable
|
||||
- guidelines-natural
|
||||
- language-community-check
|
||||
dependencies:
|
||||
- alphabet
|
||||
- level2
|
||||
- clear
|
||||
other-methods:
|
||||
recommended:
|
||||
- writing-decisions
|
||||
- community-evaluation
|
||||
dependencies:
|
||||
- language-community-check
|
||||
peer-check:
|
||||
recommended:
|
||||
- important-term-check
|
||||
dependencies:
|
||||
- level1
|
||||
- self-check
|
||||
self-assessment:
|
||||
recommended:
|
||||
- good
|
||||
- accuracy-check
|
||||
- language-community-check
|
||||
- accurate
|
||||
- clear
|
||||
- natural
|
||||
- level3-questions
|
||||
- level3-approval
|
||||
dependencies:
|
||||
- complete
|
||||
- church-leader-check
|
||||
- level3
|
||||
self-check:
|
||||
recommended:
|
||||
- peer-check
|
||||
dependencies:
|
||||
- level1
|
||||
verses:
|
||||
recommended:
|
||||
- headings
|
||||
dependencies:
|
||||
- spelling
|
||||
- punctuation
|
||||
- alphabet
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
|
||||
### Why Check?
|
||||
|
||||
The translation team's goal is to produce a translation that is accurate, natural, clear, and accepted by the church. This goal will likely require the partnership of different people, resources, and tools to accomplish. For this reason, the checkers play a very important role in helping the translation team accomplish their goal.
|
||||
|
||||
#### Accurate
|
||||
|
||||
The checkers who are pastors, church leaders, and leaders of church networks will help the translation team produce a translation that is accurate. They will do this by comparing the translation with the source language and, when possible, also with the original languages of the Bible. They are also encouraged to use the translation tools created specifically for checking and available at bibleineverylanguage.org.
|
||||
|
||||
#### Clear
|
||||
|
||||
The checkers who are members of the language community will help the translation team produce a translation that is clear. They will do this by listening to (or reading) the translation and pointing out (to the translators) the places where the translation is confusing or does not make sense to them. The translation team will work with these checkers to edit the work for clarity during checking level 2.
|
||||
|
||||
#### Natural
|
||||
|
||||
In the same way, checkers who are members of the language community will help the translation team produce a translation that is natural. The translataion team will work with them to edit for naturalness during checkign level two. (Translation notes, available at bibleineverylanguage.org is a tool that provides suggestions for handling meaning naturally in difficult passages.)
|
||||
|
||||
#### Church-approved
|
||||
|
||||
The checkers who are members of a church in the language community will help the translation team produce a translation that is approved and accepted by the church in that community. They will do this by working together with members and leaders of other churches from the language community, using the tools available at bibleineverylanguage.org as well as their own resources and other translations to carefully check the content of the newly translated scripture. When members and leaders that represent the churches of a language community work together and agree that the translation is good, then it will be accepted and used by the churches in that community.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
What is the goal of Checking?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Goal of Checking
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level 2 Affirmation
|
||||
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
Authentic Assessment is a process for evaluating the quality of a work. It is done by setting a standard for the quality and then relying on that standard as a measurement throughout the process of producing the work. This standard is called a rubric.
|
||||
|
||||
Translation teams work together to design a rubric of objective criteria that must be present for their scripture translation to be considered good. They use that rubric as they produce their translation and as they assess its quality. If they find that any part of the translation lacks a particular characteristic, they adjust the translation so that it will have that characteristic.
|
||||
|
||||
After the team has affirmed the quality of their translation, the community and church leadership also use the rubric to assess its quality. If they find that any part of the translation lacks a particular characteristic, they they tell the translation team who then compares the issue with the standard in the rubric to decide if changes need to be made.
|
||||
|
||||
Developing a rubric and using it from start to finish helps ensure that the translation is assessed by the same objective criteria from the very start of the project.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
What is Authentic Assessment and how does it apply to quality assurance?
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Authentic Assessment in Checking Scripture
|
||||
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
|
||||
|
||||
As part of the translation process, it is necessary that several people check the translation to make sure that it is clearly communicating the message that it should communicate. Several important factors are addressed in checking the translation.
|
||||
|
||||
One important reason for checking the translation is to affirm accuracy. The translator may not have understood fully the passage in the source text, and therefore not have communicated it clearly in his translation. Using tools such as commentaries and other translations can be helpful in confirming that the meaning is accurately understood and conveyed.
|
||||
|
||||
Another reason for checking is to affirm naturalness and flow. The person translating may not have used the most common venacular. Having others in the language community read it to check for flow will provide insight for correcting awkward wording.
|
||||
|
||||
Checking is also important to affirm consistant and correct grammar, punctuation and spelling. Often the translation is into a previously unwritten language, so translators and other team members may have to work together to agree on spelling and punctuation.
|
||||
|
||||
As soon as the translator has created a draft, he will begin to check it himself. Several layers of checking by others on the translation team will follow. Finally two other levels of checking outside the translation team are recommended. One will help others in the community to test the translation for naturalness and flow. The other will give theologians and scholars of various denominations the opportunity to provide recommendations.
|
||||
|
||||
Checking the Scripture may seem tedious, but it is well worth the time and effort. The translation improves with each new set of eyes that can provide feedback and recommendations.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Why do we do translation checking?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Need for Translation Checking
|
||||
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
Checking levels are designed to expand the sphere of people who have the opportunity to check and affirm the quality of the translation. There are three levels of checking that lead to three levels of affirmation.
|
||||
|
||||
The three checking levels are as follows:
|
||||
|
||||
* Level One Check: done by the translation team.
|
||||
* Level Two Check: done by the leaders of a local church and the Christian community.
|
||||
* Level Three Check: done by the leaders of multiple local churches, a network of churches, or multiple evangelical denominations.
|
||||
|
||||
### What the Checks Achieve
|
||||
|
||||
Each of the checking levels results in an affirmation level. The checking levels as explained in this manual are a guide for affirming quality and expanding the exposure of a new translation.
|
||||
|
||||
During a MAST workshop the translators do the Level One Check by engaging in the checking steps (steps 5-8) as a team. This platform assures that the individual's work is edited by other members. Additionally, these steps give team members the responsibility of working together to agree on and affirm the final product. Once this is done, the translation has reached Affirmation Level One.
|
||||
|
||||
At this point, the team is encourageed to print or otherwise publish their translation so that it can be immediately useful.They are also invited to upload their translation to the Wycliffe Associates content server.
|
||||
|
||||
Also at this point, the translation team and church leaders will determine what further checking and subsequent affirmation levels should be reached.
|
||||
|
||||
Level Two Check is done by the church leaders and other Christian members of the community. When any needed changes have been made and the leaders and members have affirmed the quality of the translation, the translation has reached Affirmation Level Two.
|
||||
|
||||
Finally, some translation teams may wish to have their work reviewed and affirmed by a network of denominational leaders and scholars. When any needed changes have been made and the network of leaders and scholars has affirmed the quality of the translation, the translation has reached Affirmation Level Three.
|
||||
|
||||
### How Affirmation Levels Are Used
|
||||
|
||||
* Translations that reach Level One Affirmation can be made available to others on the Bible in Every Language website.
|
||||
* Translations that reach Level Three Affirmation can be used as source texts for other translation projects.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What are the checking levels, and what are they used for?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Checking Levels
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
|
||||
### Level two Checking
|
||||
|
||||
The level two check focuses on pastors and the Christian community within the target language. Once the translation team has reached level one with its translation, the translation is ready to be shared outside the team for further review. Ideally, a leader on the translation team will work with local pastors and Christians to check the scripture's clarity and naturalness.
|
||||
|
||||
The translator or leader will read (if it is a written translation) a portion of the translation to the gathered listeners. Before reading, he should tell the people listening to stop him if they hear something that does not sound natural. Alternatively, if the people are literate, each one in the group can be asked to read a passage of the newly translated material. It is best, even if everyone in the group is literate, to have the portions read out loud to the whole group. Portions should not be too long (this is subjective to the abilities of the group, and type of passage). It's also very important for listeners to understand that they are now a part of the team helping to improve and affirm the quality of the scripture. They, themselves are not being tested. Rather the questions are designed to help them provide feedback on the meaningfulness of the new translation.
|
||||
|
||||
These tools have been created to assist teams in checking and are recommending for use during this level--translation questions, translation notes, and the reviewer's guide. They are available on bibleineverylanguage.org. Additionally, the translation questions and translation notes are embedded in tStudio. During the MAST workshop, the translation team was asked to develop a rubric for testing and affirming the quality of their work. More information on this strategy is available at v-raft.org. This rubric will help the team determine which tools and methods to apply to the level two check within their community.
|
||||
|
||||
Key elements of this level of checking are: pastors AND Christians in the community have read (or listened to) the translated scriptures and contributed to their improvement, the above listed tools have been employed for ensuring accuracy and completeness, the translation team has been responsible to respond to feedback and implement changes in the translation where needed. When this has been done, the translation is considered to be at level two.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How pastors and other believers can be involved in checking the translation.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level Two--Pastoral and Christian Community Check
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can the language community help me check my work?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Language Community Check
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How do I affirm that I have finished level 1 checking?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level 1 Affirmation
|
||||
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
|
||||
Level One checking will be done primarily by the translation team; it can also include help from others in the language community. The translator or translation team should check their translation often (usually as soon as a whole chapter is drafted) so that they can correct mistakes as early as possible in the translation process. Sometimes a step will have to be repeated before moving on to the next step.
|
||||
|
||||
Translation teams are invited to upload Bible texts and biblical content to the online server after they reach Checking Level One. This enables the broadest reach of the content as an active project, with an open invitation to others in the language community (implied or direct) to help improve the translation.
|
||||
|
||||
### Steps for level one checking:
|
||||
|
||||
These are the steps that the translation team must follow in order to achieve Checking Level One:
|
||||
|
||||
1. Once a portion has been drafted, the translator of that section will perform a self-edit, using the source text and other available tools to check the draft. For more information about how to do this see [Self-Edit](../self-edit/01.md).
|
||||
2. When the translator has completed the self-edit, another translator on the team will perform a peer-edit, carefuly comparing the translated text to the source text and using any other available tools to confirm the accuracy and meaningfulness of the translation. He may also provide feedback and comments on spelling, naturalness and flow. The person conducting the peer-edit does not have authority to make changes; his role is to provide feedback and suggestions to the translator of the draft who then makes changes as he deems necessary. For more information on how to conduct a peer-edit, see [Peer-Edit](../peer-edit/01.md).
|
||||
3. The keywords of the passage are systematically checked against the list of key words in the available tool designed specifically to support this checking step. Alternatively, the translation team can create their own list of key words--abstract spiritual terms, historical and geographical terms and names--and carefully compare their drafted text to that list. This step is typically done by the translator and at least one other member of the translation team. For more information, see [Key Word Check](../key-word-check/01.md).
|
||||
4. Each verse is carefully checked comparing the drafted text to the original source text, looking for any missing portions or added material. This check is typically done with the translator of the passage and at least one other member of the translation team--preferably a different member than assisted in the keyword check. For more information, see [Verse-by-verse Check](../verse-by-verse/01.md)
|
||||
|
||||
When these steps have been completed, edits have been incorporated into the translated portion, and the translation team is collectively satisifed with the product, it is considered level one checked. At this point, if the translation team desires to do so, they are invited to upload the translation to the Wycliffe Associates content server where the work can be seen on [bibleineverylanguage.org](https://bibleineverylanguage.org) to reach a broader community.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How do we do a level one check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Translation Team Check
|
||||
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
The purpose of Level Two checking is to engage representative groups from the local language community to assess the quality of the translating and contribute to its improvement where needed.
|
||||
|
||||
The level two check focuses on pastors and the Christian community within the target language. Once the translation team has reached level one with its translation, the translation is ready to be shared outside the team for further review. Ideally, a leader on the translation team will work with local pastors and Christians to check the scripture's clarity and naturalness.
|
||||
|
||||
The translator or leader will read (if it is a written translation) a portion of the translation to the gathered listeners. Before reading, he should tell the people listening to stop him if they hear something that does not sound natural. Alternatively, if the people are literate, each one in the group can be asked to read a passage of the newly translated material. It is best, even if everyone in the group is literate, to have the portions read out loud to the whole group. Portions should not be too long (this is subjective to the abilities of the group and the type of passage). It is also very important for listeners to understand that they are now a part of the team helping to improve and affirm the quality of the scripture. They themselves are not being tested. Rather the questions are designed to help them provide feedback on the meaningfulness of the new translation.
|
||||
|
||||
The following tools have been created to assist teams in checking and are recommended for use during this level: Translation Questions, Translation Notes, and the Reviewer's Guide. Translation Questions and Translation Notes are embedded in tStudio, and all of these tools are available on bibleineverylanguage.org.
|
||||
|
||||
In addition, the translation team will have developed a rubric for testing and affirming the quality of their work. This rubric lists the characeristics that the translation needs to have in order to be of good quality. This rubric will help the team determine which tools and methods to apply to the level two check within their community. More information on this strategy is available at v-raft.com.
|
||||
|
||||
Key elements of this level of checking are:
|
||||
1. Pastors AND other Christians in the community read (or listen to) the translated scriptures and contribute to their improvement
|
||||
2. The above listed tools are employed for ensuring accuracy and completeness
|
||||
3. The translation team is responsible to respond to feedback and implement changes in the translation where needed.
|
||||
|
||||
When this has been done, the translation is considered to be at level two.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How do we do a level two check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Community Review
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I give Level 3 affirmation of the translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level 3 Affirmation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What do I look for in a level 3 check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Questions for Checking on Level Three
|
||||
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
Level Three checking will be done by groups or organizations that are recognized by the churches in a language community. The leaders from these groups will verify that they affirm the quality the translation. This affirmation is not required for distribution of the translation, but rather serves to build the community's confidence in the quality of the translation.
|
||||
|
||||
Participants in this level of checking need to be different from the ones who participated in level two. Each level is an expansion of exposure, and this is most significant in affirming the quality as well as noting any needed improvements.
|
||||
|
||||
The purpose of this level is to affirm the alignment of the translation with the intent of the original texts and the sound doctrine of the Church historic and universal, through the review and affirmation by the leadership of the church that speaks the language. Level Three is thus achieved by the mutual agreement of the leadership of multiple church networks.
|
||||
|
||||
Level Three is completed when the translation has been thoroughly checked and validated by the leadership (or their delegates) of at least two church networks or denominations. When possible these should be leaders who have been trained/ordained through the church network, and they should use every aspect of their own knowledge and training to check the scriptures.
|
||||
|
||||
Here are some specific steps that can be followed for this check. However, the most important aspect of this check is to consider the authentic assessment rubric created by the translation team as the guide.
|
||||
|
||||
1. Does the translation conform to the [Statement of Faith](../../intro/statement-of-faith/01.md) and the [Qualities of a Good Translation](../../translate/guidelines-intro/01.md)?
|
||||
2. Did the translation team show a good understanding of the source language as well as the target language and culture?
|
||||
3. Does the language community affirm that the translation speaks in a clear and natural way in their language?
|
||||
4. Is the style that the translators followed appropriate for the community?
|
||||
5. Is the dialect that the translators used the best one to communicate to the wider language community? For example, have the translators used expressions, phrase connectors, and spellings that will be recognized by most people in the language community?
|
||||
6. As you read the translation, think about cultural issues in the local community that might make some passages in the book difficult to translate. Has the translation team translated these passages in a way that makes the message of the source text clear, and avoids any misunderstanding that people might have because of the cultural issue?
|
||||
7. In these difficult passages, do you feel that the translator has used language that communicates the same message that is in the source text?
|
||||
8. In your judgment, does the translation communicate the same message as the source text?
|
||||
|
||||
If the answer is no to any of the above questions, please note the area in the text that is a concern and communicate with the translation team and explanation of your concerns.
|
||||
|
||||
If you answer "yes" to any of the questions in this second group, please explain in more detail so that the translation team can know what the specific problem is, what part of the text needs correction, and how you would like them to correct it.
|
||||
|
||||
1. Are there any doctrinal errors in the translation?
|
||||
1. Did you find any areas of the translation that seem to contradict the national language translation or the important matters of faith found in your Christian community?
|
||||
1. Did the translation team add extra information or ideas that were not part of the message in the source text? (Remember that some implied information may have been expressed explicity for the meaning to be clear. This is a desirable part of meaningful translation.)
|
||||
1. Did the translation team leave out information or ideas that were part of the message in the source text?
|
||||
|
||||
If there were problems with the translation, make plans to meet with the translation team and resolve these problems. After you meet with them, the translation team may need to check their revised translation with the community leaders to make sure that it still communicates well, and then meet with you again.
|
||||
|
||||
Once the translation team has addressed suggestions to the satisfaction of the checking team, the scripture is considered to be checked to level three.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How do we do a level three check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Church Leadership Review
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Is the translation natural?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Natural Translation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I objectively assess the quality of the translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Self-Assessment Rubric
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What are the guidelines for creating a good back translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Guidelines for Creating a Good Back Translation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What kinds of back translations are there?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Kinds of Back Translations
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Why is a back translation necessary?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Purpose of the Back Translation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Who should do the back translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Back Translator
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What kinds of written back translations are there?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Kinds of Written Back Translations
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What is a back translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Back Translation
|
||||
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
|
||||
We have seen where the translation team will do a lot of checking of their own translation. Those checks bring their work up to checking Level One.
|
||||
|
||||
For Level Two and Level Three, the translation team needs to take their work to members of the language community and to the church leaders. This is necessary because the translation team is very close to and involved in their work; thus they occasionally miss mistakes that others can see more easily. Other speakers of the language can suggest better ways of saying things that the translation team may not have thought of. Sometimes the translation team makes the translation sound strange because they are following the words of the source language too closely. Other speakers of the language can help them fix that. Also, the translation team may lack some of the expertise or knowledge of the Bible that others have, and so there may be some mistakes that others can correct for them. For these reasons, people that are not part of the translation team need to check the translation.
|
||||
|
||||
In this manual, you will find guidelines for level two and level three checks, which each take the translated portions out into the wider community for further review.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Why should I check someone else's translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Introduction to Translation Checking - Part 2
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Steps in Checking a Translation
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What types of things should I check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Types of Things to Check
|
||||
|
||||
|
|
@ -1,54 +0,0 @@
|
|||
finding-answers:
|
||||
recommended:
|
||||
- process-manual
|
||||
dependencies:
|
||||
- ta-intro
|
||||
gl-strategy:
|
||||
recommended:
|
||||
- finding-answers
|
||||
dependencies:
|
||||
- uw-intro
|
||||
- open-license
|
||||
- translate/translate-terms
|
||||
open-license:
|
||||
recommended:
|
||||
- gl-strategy
|
||||
- translate-source-licensing
|
||||
dependencies:
|
||||
- uw-intro
|
||||
- statement-of-faith
|
||||
- translation-guidelines
|
||||
- translate/translate-terms
|
||||
statement-of-faith:
|
||||
recommended:
|
||||
- translation-guidelines
|
||||
- open-license
|
||||
- translate-source-licensing
|
||||
dependencies:
|
||||
- uw-intro
|
||||
ta-intro:
|
||||
recommended: []
|
||||
dependencies: []
|
||||
translate-why:
|
||||
recommended:
|
||||
- guidelines-intro
|
||||
- translate-process
|
||||
dependencies:
|
||||
- uw-intro
|
||||
- translate-manual
|
||||
- translate-whatis
|
||||
translation-guidelines:
|
||||
recommended:
|
||||
- open-license
|
||||
- translate-manual
|
||||
- intro-checking
|
||||
dependencies:
|
||||
- uw-intro
|
||||
- statement-of-faith
|
||||
- translate/translate-terms
|
||||
uw-intro:
|
||||
recommended:
|
||||
- statement-of-faith
|
||||
- gl-strategy
|
||||
dependencies:
|
||||
- ta-intro
|
||||
|
|
@ -1,51 +0,0 @@
|
|||
cobt-defined:
|
||||
recommended:
|
||||
- translate-why
|
||||
dependencies: []
|
||||
finding-answers:
|
||||
recommended:
|
||||
dependencies:
|
||||
- ta-intro
|
||||
gl-strategy:
|
||||
recommended:
|
||||
- finding-answers
|
||||
dependencies:
|
||||
- open-license
|
||||
- translate/translate-terms
|
||||
guidelines-church-approved:
|
||||
recommended:
|
||||
dependencies:
|
||||
guidelines-collaborative:
|
||||
recommended:
|
||||
dependencies:
|
||||
guidelines-ongoing:
|
||||
recommended:
|
||||
dependencies:
|
||||
mast-intro:
|
||||
recommended:
|
||||
dependencies:
|
||||
open-license:
|
||||
recommended:
|
||||
- gl-strategy
|
||||
- translate-source-licensing
|
||||
dependencies:
|
||||
- statement-of-faith
|
||||
- translate/translate-terms
|
||||
statement-of-faith:
|
||||
recommended:
|
||||
- open-license
|
||||
- translate-source-licensing
|
||||
dependencies:
|
||||
ta-intro:
|
||||
recommended: []
|
||||
dependencies: []
|
||||
translate-why:
|
||||
recommended:
|
||||
- guidelines-intro
|
||||
- translate-process
|
||||
dependencies:
|
||||
- translate-manual
|
||||
- translate-whatis
|
||||
wa:
|
||||
recommended: []
|
||||
dependencies: []
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
|
||||
The following statement on the principles and procedures used in translation is subscribed to by all contributors to the Bible In Every Language website (see https://bibleineverylanguage.org).
|
||||
|
||||
**All translation activities are carried out according to these common guidelines:**
|
||||
|
||||
1. **Accurate** (see [Accurate Translations](../../translate/guidelines-accurate/01.md))
|
||||
|
||||
1. **Clear** — (see [Clear Translations](../../translate/guidelines-clear/01.md))
|
||||
|
||||
1. **Natural** — (see [Natural Translations](../../translate/guidelines-natural/01.md))
|
||||
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
By what principles do we translate?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Translation Guidelines
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What is the unfoldingWord Project?
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue