See in Reader
Setting up for Vietnamese translation work
This commit is contained in:
parent
a55aeac147
commit
f704d633f2
Binary file not shown.
|
|
@ -1,12 +0,0 @@
|
|||
|
||||
### Translation in an Acceptable Style
|
||||
|
||||
As you read the new translation, ask yourself these questions. These are questions that will help determine whether or not the translation has been done in a style that is acceptable to the language community:
|
||||
|
||||
1. Is the translation written in a way that can be understood easily by both young and old members of the language community? (Whenever someone speaks, they can change their choice of words for either a younger or an older audience. Is this translation done using words that communicate well to both young and old people?
|
||||
1. Is the style of this translation more formal or informal? (Is the manner of speaking the way that the local community prefers, or should it be more or less formal?)
|
||||
1. Does the translation use too many words that were borrowed from another language, or are these words acceptable to the language community?
|
||||
1. Did the writer use an appropriate form of the language acceptable to the wider language community? (Is the writer familiar with the dialects of your language found throughout the area? Did the writer use a form of the language that all of the language community understands well, or did he use a form that is used in only a small area?
|
||||
|
||||
If there is a place where the translation uses language in the wrong style, make a note of that so that you can discuss it with the translation team.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Did the translation team use an acceptable style?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Acceptable Style
|
||||
|
||||
|
|
@ -1,44 +0,0 @@
|
|||
|
||||
### Checking the Translation for Accuracy
|
||||
|
||||
The purpose of this section is to make sure that the new translation is accurate. In other words, when compared with the source translation, does the new translation communicate the same meaning (not necessarily with the same wording or the exact order)?
|
||||
|
||||
#### Level One
|
||||
|
||||
The people who do the Level One accuracy check can be members of the translation team, but they should <u>not</u> be the same people who translated the story or Bible passage that they are checking. They can also be members of the community who are not part of the translation team. They should be speakers of the language of the translation, be respected in the community, and, if possible, know the Bible well in the language of wider communication. The purpose of this step is to make sure that the translation accurately communicates the meaning of the original story or Bible passage. The checkers will be helping the translation team think about the best way to translate the meaning of the story or Bible passage in their own language. There can be one person who checks a story or Bible passage, or more than one. Having more than one person checking a story or passage can be helpful, because often different checkers will notice different things.
|
||||
|
||||
#### Levels Two and Three
|
||||
|
||||
The people who do the Level Two or Level Three accuracy check should not be members of the translation team. They should be church leaders who speak the language of the translation and who know the Bible well in the source language. It is true that the language community members who do the [Language Community Check](../language-community-check/01.md) *must not* look at the source text while they check the translation for naturalness and clarity. But for accuracy testing, the accuracy checkers *must* look at the source text so that they can compare it with the new translation.
|
||||
|
||||
#### All Levels
|
||||
|
||||
The people doing the checking should follow these steps:
|
||||
|
||||
1. Each of the checkers should read the translation (or listen to the recording) by himself, comparing it to the original Bible passage or story in the language of wider communication. It can be helpful for the translator to read the translation out loud to the checker while the checker follows along looking at the source Bible or Bibles. As the checker reads (or listens to) the translation and compares it to the source, he should keep in mind these general questions:
|
||||
|
||||
* Does the translation add anything to the original meaning? (The original meaning also includes [Implicit Information](../../jit/figs-explicit/01.md).)
|
||||
* Is there any part of the meaning that is left out of the translation?
|
||||
* Has the translation changed the meaning in any way?
|
||||
|
||||
1. The checker should make notes where he thinks there might be a problem or something to be improved. Each checker will discuss these notes with the translation team.
|
||||
|
||||
1. After the checkers have checked a Bible Story or chapter individually, they should all meet with the translator or translation team and review the story or Bible passage together. As they come to the places where each checker made note of a problem or question, the checkers can ask their questions or make suggestions for improvement. As the checkers and the translation team discuss the questions and suggestions, they might think of other questions or new ways of saying things. This is good. As the checkers and the translation team work together, God will help them discover the best way to communicate the meaning of the story or Bible passage.
|
||||
|
||||
1. After the checkers and the translation team have decided what they need to change, the translation team will revise the translation.
|
||||
|
||||
1. After the translation team revises the translation, they should read it out loud to each other or to other members of the language community to make sure that it still sounds natural in their language.
|
||||
|
||||
1. The translator (or team) makes a note of any Bible passages that are still difficult to understand, and where they would like additional help from other Bible checkers. These notes will be used by the church leaders and checkers in levels two and three, so that they can help the translators understand the meaning and communicate it more clearly.
|
||||
|
||||
##### Additional Questions
|
||||
|
||||
These questions can also be helpful for finding anything that might be inaccurate in the translation:
|
||||
|
||||
* Was everything that was mentioned in the source language translation also mentioned in the flow of the new (local) translation?
|
||||
* Did the meaning of the new translation follow the message (not necessarily the wording) of the source translation? (Sometimes if the arrangement of words or the order of ideas is different than in the source translation, it sounds better that way and is still accurate.)
|
||||
* Were the people introduced in each story doing the same things as those mentioned in the source language translation? (Was it easy to see who was doing the events of the new translation when it was compared to the source language?)
|
||||
* Are there translationWords used in the new translation that do not match your understanding of the words in the source version? Think about things like this: How do your people talk about a priest (one who sacrifices to God) or a temple (the sacrifice place of the Jews) without using a word borrowed from the source language?
|
||||
* Are the phrases used in the new translation helpful in understanding the more difficult phrases of the source translation? (Are the phrases of the new translation put together in a way that brings better understanding and still fit with the meaning of the source language translation?)
|
||||
* Another way to determine if the text is accurate is to ask comprehension questions about the translation, such as, "who did what, when, where, how, and why." There are questions that have already been prepared to help with this. (To view the translationQuestions go to https://door43.org/u/WycliffeAssociates/en_tq.) The answers to those questions should be the same as the answers to those questions about the source language translation. If they are not, there is a problem in the translation.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I do an accuracy check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Accuracy Check
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
Is the translation accurate?
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
Is the translation accurate?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Accurate Translation
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
Does the translation use an appropriate alphabet?
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
Does the translation use an appropriate alphabet?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Appropriate Alphabet
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
How can the church leaders help improve the translation?
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
How can the church leaders help improve the translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Church Leader Check
|
||||
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
|
||||
### A Clear Translation
|
||||
|
||||
Ask yourself questions like the following as you read the translation to see if the translated message is clear. For this section of testing, do not compare the new translation with the source language translation. If there is a problem at any place, make a note of it so that you can discuss the problem with the translation team at a later time.
|
||||
|
||||
1. Do the words and phrases of the translation make the message understandable? (Are the words confusing, or do they tell you plainly what the translator means?)
|
||||
1. Do your community members use the words and expressions found in the translation, or has the translator borrowed many words from the national language? (Is this the way your people talk when they want to say important things in your language?)
|
||||
1. Can you read the text easily and understand what the writer might say next? (Is the translator using a good style of telling the story? Is he telling things in a way that makes sense, so that each section fits with what came before and what comes after?)
|
||||
|
||||
Additional help:
|
||||
|
||||
* One way to determine if the text is clear is to read a few verses at a time out loud and ask someone listening to retell the story after each section. If the person can easily restate your message, then the writing is clear.
|
||||
* If there is a place where the translation is not clear, make a note of that so that you can discuss it with the translation team.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I tell if the translation is clear?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Clear Translation
|
||||
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
|
||||
We, the members of the translation team, affirm that we have checked the translation with members of the language community.
|
||||
|
||||
* We have checked the translation with old people and young people, and with men and women.
|
||||
* We used the translationQuestions when we checked the translation with the community.
|
||||
* We corrected the translation to make it clearer and easier to understand in the places where the community members did not understand it well.
|
||||
|
||||
Please also answer the following questions. The answers to these questions will help those in the wider Christian community know that the target language community finds the translation to be clear, accurate, and natural.
|
||||
|
||||
* List a few passages where the community feedback was helpful. How did you change these passages to make them clearer?
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
* Write an explanation for some of the Important Terms, explaining how they are equal to terms used in the source language. This will help the checkers understand why you chose these terms.
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
* Does the community verify that there is a good flow to the language when the passages are read out loud? (Does the language sound like the writer was a person from your own community?)
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
The community leaders might want to add their own information to this or make a summary statement about how acceptable this translation is to the local community. This can be included as part of the Level Two Community Check Evaluation information. The wider church leadership will have access to this information, and it will help them validate the translation as approved by the local Christian community when they do the Level Two Church Check and also Level Three Checking.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I show that the community approves the translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Language Community Evaluation Questions
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
|
||||
### A Complete Translation
|
||||
|
||||
The purpose of this section is to make sure that the translation is complete. In this section, the new translation must be compared to the source translation. As you compare the two translations, ask yourself these questions:
|
||||
|
||||
1. Is the translation missing any of its parts? In other words, does the translation include all the events of the book that was translated?
|
||||
1. Does the translation include all the verses of the book that was translated? (When you look at the verse numbering of the source language translation, are all of the verses included in the target language translation?) Sometimes there are differences in verse numbering between translations. For example, in some translations some verses are grouped together or sometimes certain verses are put in footnotes. Even though there may be these kinds of differences between the source translation and the target translation, the target translation is still considered to be complete.
|
||||
1. Are there places in the translation where something seems to be left out, or there seems to be a different message than is found in the source language translation? (The wording and the order can be different, but the language that the translator used should give the same message as the source language translation.)
|
||||
|
||||
If there is a place where the translation is not complete, make a note of that so that you can discuss it with the translation team.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Is the translation complete?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Complete Translation
|
||||
|
||||
|
|
@ -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,2 +0,0 @@
|
|||
What is the goal of Checking?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Goal of Checking
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can church leaders affirm that the translation is good?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level 2 Affirmation
|
||||
|
||||
|
|
@ -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,27 +0,0 @@
|
|||
|
||||
### Language Community Check
|
||||
|
||||
After you, the translation team, have performed the checks listed under Level One, you are ready to take the translation to the community so that you can check to see if it communicates the message clearly and naturally to them in the target language.
|
||||
|
||||
For this check you will read a section of the translation to members of the language community. Before you read the translation, tell the people listening that you want them to stop you if they hear something that is not natural in their language. (For more information on how to check a translation for naturalness, see [Natural Translation](../natural/01.md).)
|
||||
|
||||
There are a set of questions and answers for each *Open Bible Story* and for each chapter of the Bible that you can use to test the translation to make sure that it is communicating clearly. (See https://door43.org/u/WycliffeAssociates/en_tq for the questions.)
|
||||
|
||||
To use these questions, follow these steps:
|
||||
|
||||
1. Read the passage of the translation to one or more members of the language community who will answer the questions. These members of the language community must be people who have not been involved in the translation before. In other words, the community members who are asked the questions should not already know the answers to the questions from working on the translation or from previous knowledge of the Bible. We want them to be able to answer the questions only from hearing or reading the translation of the story or Bible passage. This is how we will know if the translation is communicating clearly or not. For this same reason, it is important that the community members not look at a Bible while they are answering these questions.
|
||||
|
||||
1. Ask the community members some of the questions for that passage, one question at a time. It is not necessary to use all of the questions for each story or chapter if it seems that the community members are understanding the translation well.
|
||||
|
||||
1. After each question, a member of the language community will answer the question. If the person only answers with a "yes" or a "no," then the questioner should ask a further question so that he can be sure that the translation is communicating well. A further question could be something like, "How do you know that?" or "What part of the translation tells you that?"
|
||||
|
||||
1. Write down the answer that the person gives. If the person's answer is similar to the suggested answer that has been provided for the question, then the translation of the story is clearly communicating the right information at that point. The answer does not have to be exactly the same as the suggested answer to be a right answer, but it should give basically the same information. Sometimes the suggested answer is very long. If the person answers with only part of the suggested answer, that is also a right answer.
|
||||
|
||||
1. If the answer is unexpected or very different than the suggested answer, or if the person cannot answer the question, then the translation team will need to revise the part of the translation that communicates that information so that it communicates the information more clearly.
|
||||
|
||||
1. After the translation team has revised the translation of the passage, then ask other members of the language community the same questions, that is, ask other speakers of the language who have not been involved in checking the same passage before. If they answer the questions correctly, then the translation is now communicating well.
|
||||
|
||||
1. Repeat this process with each story or Bible chapter until members of the language community can answer the questions well, showing that the translation is communicating the right information clearly. The translation is ready for the church check of level 2 when language community members who have not heard the translation before can answer the questions correctly.
|
||||
|
||||
1. Go to the Community Evaluation page and answer the questions there. (see [Language Community Evaluation Questions](../community-evaluation/01.md))
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can the language community help me check my work?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Language Community Check
|
||||
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
|
||||
### Proper Documentation for Level Two Affirmation
|
||||
|
||||
We, as church leaders in our language community, affirm the following:
|
||||
|
||||
1. The translation conforms to the Statement of Faith and Translation Guidelines.
|
||||
1. The translation is accurate and clear in the target language.
|
||||
1. The translation uses an acceptable style of the language.
|
||||
1. The translation uses an appropriate alphabet and system of spelling.
|
||||
1. The community validates the translation.
|
||||
1. The community evaluation form has been completed.
|
||||
|
||||
If there are any remaining problems, make a note of them here for the attention of the Level Three Checkers.
|
||||
|
||||
Names and positions of the level 2 checkers:
|
||||
|
||||
* Name:
|
||||
* Position:
|
||||
* Name:
|
||||
* Position:
|
||||
* Name:
|
||||
* Position:
|
||||
* Name:
|
||||
* Position:
|
||||
* Name:
|
||||
* Position:
|
||||
* Name:
|
||||
* Position:
|
||||
|
||||
|
|
@ -1,24 +0,0 @@
|
|||
|
||||
### Proper Documentation for Level 1 Affirmation
|
||||
|
||||
We, the members of the translation team, affirm that we have completed the steps below for level 1 checking:
|
||||
|
||||
* Initial study of the text, using:
|
||||
* The Translation Notes
|
||||
* The definitions of translationWords
|
||||
* Individual blind drafting
|
||||
* Individual self check
|
||||
* Peer check
|
||||
* Key word check as a team
|
||||
* Verse-by-verse accuracy check as a team
|
||||
* Final editing, including everything learned from the earlier editing sessions, the Translation Notes, and the definitions of translationWords
|
||||
|
||||
Names of translation team members:
|
||||
|
||||
* Name or pseudonym:
|
||||
* Name or pseudonym:
|
||||
* Name or pseudonym:
|
||||
* Name or pseudonym:
|
||||
* Name or pseudonym:
|
||||
* Name or pseudonym:
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How do I affirm that I have finished level 1 checking?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level 1 Affirmation
|
||||
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
|
||||
### Documentation for Level Three Affirmation
|
||||
|
||||
I, as a representative of the *<u>fill in name of church network or Bible translation organization</u>* Church Network or Bible translation organization serving the *<u>fill in the name of the language community</u>* language community, affirm the quality of the translation, and affirm the following:
|
||||
|
||||
1. The translation conforms to the Statement of Faith and Translation Guidelines.
|
||||
1. The translation is accurate and clear in the target language.
|
||||
1. The translation uses an acceptable style of the language.
|
||||
1. The community affirms the quality of the translation.
|
||||
|
||||
If any problems remain unresolved after meeting with the translation team a second time, please make note of them here.
|
||||
|
||||
Signed: *<u>sign here</u>*
|
||||
|
||||
Position: *<u>fill in your position here</u>*
|
||||
|
||||
For Gateway Languages, you will need to follow the [Source Text Process](../../process/source-text-process/01.md) so that your translation can become a source text.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I give Level 3 affirmation of the translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Level 3 Affirmation
|
||||
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
|
||||
### Questions for Level Three
|
||||
|
||||
These are the questions for the Level Three checkers to keep in mind as they read the new translation.
|
||||
|
||||
You can answer these questions after you read portions of the translation or as you come across problems in the text. If you answer "no" to any of these questions in the first group, please explain in more detail, include the specific passage that you feel is not right, and give your recommendation for how the translation team should correct it.
|
||||
|
||||
Keep in mind that the goal of the translation team is to express the meaning of the source text in a natural and clear way in the target language. This means that they may have needed to change the order of some clauses and that they had to represent many single words in the source language with multiple words in the target language. These things are not considered to be problems in Other Language (OL) translations. The only times that translators should avoid making these changes is for Gateway Language (GL) translations of the ULB and UDB. The purpose of the ULB is to show the OL translator how the original biblical languages expressed the meaning, and the purpose of the UDB is to express that same meaning in simple, clear forms, even though it might be more natural to use an idiom in the OL. GL translators need to remember those guidelines. But for OL translations, the goal is always to be natural and clear.
|
||||
|
||||
Also keep in mind that the translators may have included information that the original audience would have understood from the original message, but that the original author did not state explicitly. When this information is necessary for the target audience to understand the text, it is good to include it explicitly. For more about this, see [Implicit and Explicit Information](../../jit/figs-explicit/01.md).
|
||||
|
||||
1. Does the translation conform to the Statement of Faith and Translation Guidelines?
|
||||
1. Did the translation team show a good understanding of the source language as well as the target language and culture?
|
||||
1. Does the language community affirm that the translation speaks in a clear and natural way in their language?
|
||||
1. Which of the following translation styles did the translators appear to follow?
|
||||
|
||||
1. word-by-word translation, staying very close to the form of the source translation
|
||||
1. phrase by phrase translation, using natural language phrase structures
|
||||
1. meaning-focused translation, aiming for a freedom of local language expression
|
||||
|
||||
1. Do the community leaders feel that the style that the translators followed (as identified in question 4) is appropriate for the community?
|
||||
1. Do the community leaders feel that the dialect that the translators used is 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?
|
||||
1. 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?
|
||||
1. In these difficult passages, do the community leaders feel that the translator has used language that communicates the same message that is in the source text?
|
||||
1. In your judgment, does the translation communicate the same message as the source text? If any part of the translation causes you to answer "no," please answer the second group of questions below.
|
||||
|
||||
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, the original message also includes [Implicit Information](../../jit/figs-explicit/01.md).)
|
||||
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.
|
||||
|
||||
When you are ready to approve the translation, go here: [Level 3 Approval](../level3-approval/01.md).
|
||||
|
||||
|
|
@ -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,13 +0,0 @@
|
|||
|
||||
### A Natural Translation
|
||||
|
||||
To translate the Bible so that it is NATURAL means that:
|
||||
|
||||
The translation should sound like it was written by a member of the target language community—not by a foreigner.
|
||||
|
||||
To check a translation for naturalness, it is not helpful to compare it to the source language. During this check for naturalness, no one should look at the source language Bible. People will look at the source language Bible again for other checks, such as the check for accuracy, but not during this check.
|
||||
|
||||
To check a translation for naturalness, you or another member of the language community must read it out loud. You can read it to one other person who speaks the target language or to a group of people. Before you start reading, tell the people listening that you want them to stop you when they hear something that does not sound like the way someone from your language community would say it. When someone stops you, then you can discuss together how someone would say that same thing in a more natural way.
|
||||
|
||||
It is helpful to think about a situation in your village in which people would talk about the same kind of thing that the translation is talking about. Imagine people that you know talking about that thing, and then say it out loud in that way. If others agree that that is a good and natural way to say it, then write it that way in the translation.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Is the translation natural?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Natural Translation
|
||||
|
||||
|
|
@ -1,117 +0,0 @@
|
|||
|
||||
### Self-assessment of Translation Quality
|
||||
|
||||
The objective of this section is to describe a process by which the Church can reliably determine for themselves the quality of a translation. This following assessment is intended to suggest some of the most important techniques for checking a translation, rather than to describe every conceivable check that could be employed. Ultimately, the decision of what checks are used, when, and by whom should be made by the Church.
|
||||
|
||||
#### How to Use the Assessment
|
||||
|
||||
This assessment method employs two types of statements. Some are "yes/no" statements where a negative response indicates a problem that must be resolved. Other sections use an equally-weighted method that provides translation teams and checkers with statements about the translation. Each statement should be scored by the person doing the check (beginning with the translation team) on a scale of 0-2:
|
||||
|
||||
**0** - disagree
|
||||
|
||||
**1** - agree somewhat
|
||||
|
||||
**2** - strongly agree
|
||||
|
||||
At the end of the review, the total value of all responses in a section should be added up and, if the responses accurately reflect the state of the translation, this value will provide the reviewer with an approximation of the probability that the translated chapter is of excellent quality. The rubric is designed to be simple and provide the reviewer with an objective method to assess where the work needs improvement. *For example, if the translation scores relatively well in "Accuracy" but quite poorly in "Naturalness" and "Clarity," then the translation team needs to do more community checking.*
|
||||
|
||||
The rubric is intended to be used for each chapter of translated biblical content. The translation team should do an assessment of each chapter after they finish their other checks, and then the level 2 church checkers should do it again, and then the level 3 checkers should also assess the translation with this checklist. As more detailed and extensive checking of the chapter is performed by the Church at each level, the points for the chapter should be updated from each of the first four sections (overview, naturalness, clarity, accuracy), allowing the church and community to see how the translation is improving.
|
||||
|
||||
#### The Self-Assessment
|
||||
|
||||
The process is divided into five parts: the **overview** (information about the translation itself), **naturalness**, **clarity**, **accuracy**, and **Church approval**.
|
||||
|
||||
##### 1. Overview
|
||||
|
||||
*Circle either "no" or "yes" for each statement below.*
|
||||
|
||||
**no | yes** This translation is a meaning-based translation that attempts to communicate the meaning of the original text in ways that are natural, clear, and accurate in the target language.
|
||||
|
||||
**no | yes** Those involved in checking the translation are first-language speakers of the target language.
|
||||
|
||||
**no | yes** The translation of this chapter is in agreement with the Statement of Faith.
|
||||
|
||||
**no | yes** The translation of this chapter has been done in accordance with the Translation Guidelines.
|
||||
|
||||
##### 2. Naturalness: "this is *my* language"
|
||||
|
||||
*Circle either "0" or "1" or "2" for each statement below.*
|
||||
|
||||
This section can be strengthened through doing more community checking. (See [Language Community Check](../language-community-check/01.md))
|
||||
|
||||
**0 1 2** Those who speak this language and have heard this chapter agree that it is translated using the correct form of the language.
|
||||
|
||||
**0 1 2** Those who speak this language agree that the key words used in this chapter are acceptable and correct for this culture.
|
||||
|
||||
**0 1 2** The illustrations or stories in this chapter are easy for people who speak this language to understand.
|
||||
|
||||
**0 1 2** Those who speak this language agree that the sentence structure and order of the text in this chapter is natural and flows correctly.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for naturalness included community members who have not been directly involved in creating the translation of this chapter.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for naturalness included both believers and non-believers, or at least believers who are relatively unfamiliar with the Bible so that they do not know what the text is supposed to say before they hear it.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for naturalness included speakers of the language from many different age groups.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for naturalness included both men and women.
|
||||
|
||||
##### 3. Clarity: "the meaning is clear"
|
||||
|
||||
*Circle either "0" or "1" or "2" for each statement below.*
|
||||
|
||||
This section can be strengthened through doing more community checking. (See [Language Community Check](../language-community-check/01.md))
|
||||
|
||||
**0 1 2** This chapter is translated using language that native speakers of the language agree is easy to understand.
|
||||
|
||||
**0 1 2** Speakers of this language agree that the translations of names, places, and verb tenses are all correct in this chapter.
|
||||
|
||||
**0 1 2** Figures of speech in this chapter make sense for people in this culture.
|
||||
|
||||
**0 1 2** Speakers of this language agree that the way this chapter is structured does not distract from the meaning.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for clarity included community members who have not been directly involved in creating the translation of this chapter.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for clarity included both believers and non-believers, or at least believers who are relatively unfamiliar with the Bible so that they do not know what the text is supposed to say before they hear it.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for clarity included speakers of the language from many different age groups.
|
||||
|
||||
**0 1 2** The review of the translation of this chapter for clarity included both men and women.
|
||||
|
||||
##### 4. Accuracy: "the translation communicates what the original source text communicated"
|
||||
|
||||
*Circle either "0" or "1" or "2" for each statement below.*
|
||||
|
||||
This section can be strengthened through doing more accuracy checking. (See [Accuracy Check](../accuracy-check/01.md))
|
||||
|
||||
**0 1 2** A complete list of all important words in the source text for this chapter has been used to help ensure all terms are present in the translation.
|
||||
|
||||
**0 1 2** All important words are translated correctly in this chapter.
|
||||
|
||||
**0 1 2** All important words are translated consistently in this chapter, as well as in other places where the important words appear.
|
||||
|
||||
**0 1 2** Exegetical resources have been used for the entire chapter to identify and resolve potential translation challenges, including the Notes and translationWords.
|
||||
|
||||
**0 1 2** Historical details in the source text (like names, places, and events) have been preserved in the translation.
|
||||
|
||||
**0 1 2** The meaning of each figure of speech in the translated chapter has been compared and aligned to the intent of the original.
|
||||
|
||||
**0 1 2** The translation has been tested with native speakers who were not involved in creating the translation and they agree that the translation accurately communicates the intended meaning of the source text.
|
||||
|
||||
**0 1 2** The translation of this chapter has been compared against at least two source texts.
|
||||
|
||||
**0 1 2** All questions or disagreements about any of the meaning in this chapter have been resolved.
|
||||
|
||||
**0 1 2** The translation of this chapter has been compared against the original texts (Hebrew, Greek, Aramaic) to check for correct lexical definitions and intent of the original texts.
|
||||
|
||||
##### 5. Church approval: "the naturalness, clarity, and accuracy of the translation is approved by the Church that speaks that language"
|
||||
|
||||
*Circle either "0" or "1" or "2" for each statement below.*
|
||||
|
||||
**no | yes** Church leaders who have checked this translation are native speakers of the target language, and include someone who understands well one of the languages in which the source text is available.
|
||||
|
||||
**no | yes** People from the language community, both men and women, old and young, have reviewed the translation of this chapter and agree that it is natural and clear. *(Note: this addresses the first part of the community check for Level 2.)*
|
||||
|
||||
**no | yes** Church leaders from at least two different church networks have reviewed the translation of this chapter and agree that it is accurate. *(This addresses the final aspect of Level 2, the Church check).*
|
||||
|
||||
**no | yes** The leadership or their delegates of at least two different church networks have reviewed the translation of this chapter and endorse it as a faithful translation of this chapter of the Bible in this language. *(This addresses Level 3.)*
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I objectively assess the quality of the translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Self-Assessment Rubric
|
||||
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
|
||||
### 1. Show the Target Language Usage for Words and Clauses
|
||||
|
||||
#### a. Use the meaning of the word in context
|
||||
|
||||
If a word has only one basic meaning, then the back translator should use a word in the language of wider communication that represents that basic meaning throughout the back translation. If, however, a word in the target language has more than one meaning, so that the meaning changes depending on the context that it is in, then the back translator should use the word or phrase in the language of wider communication that best represents the way that the word was used in that context. In order to avoid confusion for the translation checker, the back translator can put the other meaning in parentheses the first time that he uses the word in a different way, so that the translation checker can see and understand that this word has more than one meaning. For example, he might write, "come (go)" if the target language word was translated as "go" earlier in the back translation but in the new context it is better translated as "come."
|
||||
|
||||
If the target language translation uses an idiom, it is most helpful to the translation checker if the back translator translates the idiom literally (according to the meaning of the words), but then also includes the meaning of the idiom in parentheses. In that way, the translation checker can see that the target language translation uses an idiom in that place, and also see what it means. For example, a back translator might translate an idiom such as, "he kicked the bucket (he died)." If the idiom occurs more than once or twice, the back translator does not need to continue to explain it each time, but can either just translate it literally or just translate the meaning.
|
||||
|
||||
#### b. Keep parts of speech the same
|
||||
|
||||
In the back translation, the back translator should represent the parts of speech of the target language with the same parts of speech in the language of wider communication. This means that the back translator should translate nouns with nouns, verbs with verbs, and modifiers with modifiers. This will help the translation checker to see how the target language works.
|
||||
|
||||
#### c. Keep clause types the same
|
||||
|
||||
In the back translation, the back translator should represent each clause of the target language with the same type of clause in the language of wider communication. For example, if the target language clause uses a command, then the back translation should also use a command, rather than a suggestion or request. Or if the target language clause uses a rhetorical question, then the back translation should also use a question, rather than a statement or other expression.
|
||||
|
||||
#### d. Keep punctuation the same
|
||||
|
||||
The back translator should use the same punctuation in the back translation as there is in the target language translation. For example, wherever there is a comma in the target language translation, the back translator should also put a comma in the back translation. Periods, exclamation points, quote marks, and all punctuation need to be at the same place in both translations. In that way, the translation checker can more easily see which parts of the back translation represent which parts of the target language translation. When making a back translation of the Bible, it is also very important to make sure that all chapter and verse numbers are in the right places in the back translation.
|
||||
|
||||
#### e. Express the full meaning of complex words
|
||||
|
||||
Sometimes words in the target language will be more complex than words in the language of wider communication. In this case, the back translator will need to represent the target language word with a longer phrase in the language of wider communication. This is necessary so that the translation checker can see as much of the meaning as possible. For example, to translate one word in the target language it might be necessary to use a phrase in the language of wider communication such as, "go up," or "be lying down." Also, many languages have words that contain more information than the equivalent words in the language of wider communication. In this case, it is most helpful if the back translator includes that additional information in parentheses, such as "we (inclusive)," or "you (feminine, plural)."
|
||||
|
||||
### 2. Use the Language of Wider Communication Style for Sentence and Logical Structure
|
||||
|
||||
The back translation should use the sentence structure that is natural for the language of wider communication, not the structure that is used in the target language. This means that the back translation should use the word order that is natural for the language of wider communication, not the word order that is used in the target language. The back translation should also use the way of relating phrases to each other and the way of indicating logical relations, such as cause or purpose, that are natural for the language of wider communication. This will make the back translation easier to read and understand for the translation checker. This will also speed up the process of checking the back translation.
|
||||
|
||||
|
|
@ -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,21 +0,0 @@
|
|||
|
||||
### What kinds of back translations are there?
|
||||
|
||||
#### Oral
|
||||
|
||||
An oral back translation is one that the back translator speaks to the translation checker in the language of wider communication as he reads or hears the translation in the target language. He will usually do this one sentence at a time, or two sentences at a time if they are short. When the translation checker hears something that may be a problem, he will stop the person doing the oral back translation so that he can ask a question about it. One or more members of the translation team should also be present so that they can answer questions about the translation.
|
||||
|
||||
An advantage of the oral back translation is that the back translator is immediately accessible to the translation checker and can answer the translation checker's questions about the back translation. A disadvantage of the oral back translation is that the back translator has very little time to think about the best way to back translate the translation and he may not express the meaning of the translation in the best way. This may make it necessary for the translation checker to ask more questions than if the back translation were expressed in a better way. Another disadvantage is that the checker also has very little time to evaluate the back translation. He only has a few seconds to think about one sentence before hearing another. Because of this, he may not catch all of the problems that he would catch if he had more time to think about each sentence.
|
||||
|
||||
#### Written
|
||||
|
||||
There are two types of written back translations. The differences between the two will be discussed in the next module. A written back translation has several advantages over an oral back translation. First, when a back translation is written, the translation team can read it to see if there are any places where the back translator has misunderstood their translation. If the back translator misunderstood the translation, then other readers or hearers of the translation certainly will misunderstand it also, and so the translation team will need to revise their translation at those points.
|
||||
|
||||
Second, when the back translation is written, the translation checker can read the back translation before meeting with the translation team and take time to research any question that arises from the back translation. Even when the translation checker does not need to research a problem, the written back translation allows him more time to think about the translation. He can identify and address more of the problems in the translation and sometimes come to better solutions to the problems because he has more time to think about each one than when he has only a few seconds to think about each sentence.
|
||||
|
||||
Third, when the back translation is written, the translation checker can also prepare his questions in written form before meeting with the translation team. If there is time before their meeting and if they have a way to communicate, the checker can send his written questions to the translation team so that they can read them and change the parts of the translation that the checker thought to be problems. This helps the translation team and the checker to be able to review much more of the biblical material when they meet together, because they were able to fix many of the problems in the translation before their meeting. During the meeting, they can concentrate on the problems that remain. These are usually places where the translation team has not understood the checker's question or where the checker has not understood something about the target language and so thinks that there is a problem where there is not. In that case, during the meeting time the translation team can explain to the checker what it is that he has not understood.
|
||||
|
||||
Even if there is not time for the checker to send his questions to the translation team before their meeting, they will still be able to review more material at the meeting than they would have been able to review otherwise because the checker has already read the back translation and has already prepared his questions. Because he has had this previous preparation time, he and the translation team can use their meeting time to discuss only the problem areas of the translation rather than reading through the entire translation at a slow pace, as is required when making an oral back translation.
|
||||
|
||||
Fourth, the written back translation relieves the strain on the translation checker from having to concentrate for many hours at a time on hearing and understanding an oral translation as it is spoken to him. If the checker and translation team are meeting in a noisy environment, the difficulty of making sure that he hears every word correctly can be quite exhausting for the checker. The mental strain of concentration increases the likelihood that the checker will miss some problems with the result that they remain uncorrected in the biblical text. For these reasons, we recommend the use of a written back translation whenever possible.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What kinds of back translations are there?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Kinds of Back Translations
|
||||
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
|
||||
### Why is a back translation necessary?
|
||||
|
||||
The purpose of a back translation is to allow a consultant or checker of biblical material who does not understand the target language to be able to see what is in the target language translation, even though he or she does not understand the target language. Therefore, the language of the back translation needs to be a language that both the person doing the back translation (the back translator) and the checker understand well. Often this means that the back translator will need to translate the target language text back into the same language of wider communication that was used for the source text.
|
||||
|
||||
Some people might consider this to be unnecessary, since the biblical text already exists in the source language. But remember the purpose of the back translation: it is to allow the checker to see what is in the target language translation. Just reading the original source language text does not allow the checker to see what is in the target language translation. Therefore, the back translator must make a new translation back into the language of wider communication that is based only on the target language translation. For this reason, the back translator *cannot* look at the source language text when doing his back translation, but *only* at the target language text. In this way, the checker can identify any problems that might exist in the target language translation and work with the translator to fix those problems.
|
||||
|
||||
The back translation can also be very useful in improving the target language translation even before the checker uses it to check the translation. When the translation team reads the back translation, they can see how the back translator has understood their translation. Sometimes, the back translator has understood their translation in a different way than they intended to communicate. In those cases, they can change their translation so that it communicates more clearly the meaning that they intended. When the translation team is able to use the back translation in this way before they give it to the checker, they can make many improvements to their translation. When they do this, the checker can do his checking much more rapidly, because the translation team was able to correct many of the problems in the translation before meeting with the checker.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Why is a back translation necessary?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Purpose of the Back Translation
|
||||
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
|
||||
### Who should do the back translation?
|
||||
|
||||
To do a good back translation, the person must have three qualifications.
|
||||
|
||||
1. The person who makes the back translation should be someone who is a mother-tongue speaker of the local target language and who also speaks the language of wider communication well.
|
||||
1. This person must also be someone who was not involved in making the local target language translation that he is back translating. The reason for this is that someone who made the local target language translation knows what he intended the translation to mean, and will put that meaning in the back translation with the result that it looks the same as the source translation. But it is possible that a speaker of the local target language who did not work on the local target language translation will understand the translation differently, or will not understand parts of it at all. The checker wants to know what these other meanings are that other speakers of the local target language will understand from the translation so that he can work with the translation team to make those places communicate the right meaning more clearly.
|
||||
1. The person who does the back translation should also be someone who does not know the Bible well. The reason for this is that the back translator must give only the meaning that he understands from looking at the target language translation, not from knowledge that he might have from reading the Bible in another language.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Who should do the back translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The Back Translator
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
|
||||
There are two kinds of written back translations.
|
||||
|
||||
### Interlinear Back Translation
|
||||
|
||||
An interlinear back translation is one in which the back translator puts a translation for each word of the target language translation underneath that word. This results in a text in which each line of the target language translation is followed by a line in the language of wider communication. The advantage of this kind of back translation is that the checker can easily see how the translation team is translating each word of the target language. He can more easily see the range of meaning of each target language word and can compare how it is used in different contexts. The disadvantage of this kind of back translation is that the line of text in the language of wider communication is made up of translations of individual words. This makes the text difficult to read and understand, and may create more questions and misunderstandings in the mind of the translation checker than the other method of back translation. This is the same reason we do not recommend the word-for-word method for translation of the Bible!
|
||||
|
||||
### Free Back Translation
|
||||
|
||||
A free back translation is one in which the back translator makes a translation in the language of wider communication in a separate space from the target language translation. The disadvantage of this method is that the back translation is not related as closely to the target language translation. The back translator can overcome this disadvantage when back translating the Bible, however, by including the verse numbers with the back translation. By referring to the verse numbers in both translations, the translation checker can keep track of which part of the back translation represents which part of the target language translation. The advantage of this method is that the back translation can use the grammar and word order of the language of wider communication, and so it is much easier for the translation checker to read and understand. Even while using the grammar and word order of the language of wider communication, however, the back translator should remember to translate the words in a literal way. We recommend that the back translator use the method of free back translation.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What kinds of written back translations are there?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Kinds of Written Back Translations
|
||||
|
||||
|
|
@ -1,7 +0,0 @@
|
|||
|
||||
### What is a back translation?
|
||||
|
||||
A back translation is a translation of the biblical text from the local target language back into the language of wider communication. It is called a "back translation" because it is a translation in the opposite direction than what was done to create the local target language translation.
|
||||
|
||||
A back translation is not done in a completely normal style, however, because it does not have naturalness as a goal in the language of the translation (in this case, the language of wider communication). Instead, its goal is to represent the words and expressions of the local language translation in a literal way, while also using the grammar and word order of the language of wider communication. In this way, the translation checker can most clearly see the meaning of the words in the target language text, and can also understand the back translation well and read it more quickly and easily.
|
||||
|
||||
|
|
@ -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,45 +0,0 @@
|
|||
|
||||
### Steps in Checking a Translation
|
||||
|
||||
#### Before Checking
|
||||
|
||||
1. Find out ahead of time which set of stories or which Bible passage you will be checking.
|
||||
1. Read the passage in several versions in any languages you understand, including the original languages, if possible.
|
||||
1. Read the passage in the ULB and UDB, and read the Notes and translationWords.
|
||||
1. Make note of any parts that you think might be difficult to translate.
|
||||
1. Research these passages in translation helps and commentaries, making notes about what you discover.
|
||||
|
||||
#### While Checking
|
||||
|
||||
1. **Ask Questions**. When you see something that you think might be a problem in the translation, do not make a statement to the translator that there is a problem in the translation. If you do not speak the target language, then you do not know if there is a problem or not. You only suspect that there could be a problem. Even if you do speak the target language, it is more polite to ask a question than to make a statement that something is wrong. You could ask something like, "What would you think about saying it this way?" and then suggest an alternative way to translate it. Then together you can discuss the different translation ideas, and you can give reasons why you think one translation alternative might be better than another. Then, after considering the alternatives, the translator or translation team must decide which way is best.
|
||||
1. **Explore the target language and culture**. The questions that you ask will be to discover what the phrase means in the target language. The best questions are the ones that help the translator to think about what the phrase means and how it is used. Useful questions are, "In what situations is this phrase used in your language?" or "Who usually says things like this, and why do they say it?" It is also useful to help the translator to think about what a person from his village would say if in the same situation as the person in the Bible.
|
||||
1. **Teach the translator**. After you explore the meaning of a phrase in the target language and culture, you can tell the translator what the phrase means in the source language and culture. Then together you can decide if the phrase in the translation or the phrase he has just thought of has that same meaning or not.
|
||||
|
||||
#### Checking the Translation Directly
|
||||
|
||||
If you speak the target language, then you can read or hear the translation and ask the translation team about it directly.
|
||||
|
||||
#### Using a Written Back Translation
|
||||
|
||||
If you do not speak the target language, you will need to work from a back translation in a language that you do understand. This can be written separately from the translation, or it can be written as an interlinear, that is, with a line of back translation written under each line of the translation. It is easier to compare the translation to the back translation when they are written as an interlinear, and it is easier to read a back translation that is written separately. Each method has its own strength. The person who makes the back translation should be someone who was not involved in making the translation.
|
||||
|
||||
1. If possible, review the back translation in written form before meeting with the translator or translation team face-to-face. This will give you time to think about the passage and to do further research on questions that arise because of what the back translation says. It will also save a lot of time when you meet with the translation team, because there will be a lot of text that you do not need to talk about because you read it in the back translation and it did not have problems. When you meet together, you will be much more productive because you can spend all of your time on the problem areas.
|
||||
1. As you work through the back translation, make notes of questions that you want to ask the translator, either for clarification or to help the translator think about possible problems with the translation.
|
||||
1. Ask the translator for a copy of the translation (if it is not interlinear), so that you can compare the translation with the back translation and make note of the connectors that the target language uses and other features that might not be visible in the back translation. Looking at the translation can also help to identify places where the back translation might not accurately represent the translation. For example, where the same words are used in the translation but they are different in the back translation. In this case, it is good to ask the translator why the back translation is different, and if it needs to be corrected.
|
||||
1. If you cannot review the back translation before meeting with the translator, then work through it with the translator, discussing questions and problems as you work together. Often, as the back translation is compared to the translation, the translator will also discover problems with the translation.
|
||||
|
||||
#### Using an Oral Back Translation
|
||||
|
||||
If there is no written back translation, then have someone who knows the target language and also a language that you understand make an oral back translation for you. This should be a person who was not involved in making the translation. As you listen to the oral back translation, make notes of words or phrases that seem to communicate the wrong meaning or that present other problems. The person should translate the passage in short segments, pausing in between each segment so that you can ask your questions after you hear each segment.
|
||||
|
||||
#### After Checking
|
||||
|
||||
Some questions will need to be set aside for later, after the checking session. Be sure to plan a time to meet again to discuss the answers to these questions. These will be:
|
||||
|
||||
1. Questions that you or someone else will need to research, usually something about the biblical text that you will need to find out, such as more exact meanings of biblical words or phrases, or the relationship between biblical people or the nature of biblical places.
|
||||
1. Questions to ask other speakers of the target language. These would be to make sure that certain phrases are communicating correctly, or to research the cultural background of certain terms in the target language. These are questions that the translation team may need to ask of people when they return to their community.
|
||||
|
||||
### Key Words
|
||||
|
||||
Make sure that the translation team is keeping a list of the translationWords (important terms) from the Bible passages that they are translating, along with the term in the target language that they have decided to use for each of these important terms. You and the translation team will probably need to add to this list and modify the terms from the target language as you progress through the translation of the Bible. Use the list of translationWords to alert you when there are Key Words in the passage that you are translating. Whenever there is a Key Word in the Bible, make sure that the translation uses the term or phrase that has been chosen for that Key Word, and also make sure that it makes sense each time. If it does not make sense, then you will need to discuss why it makes sense in some places but not in others. Then you may need to modify or change the chosen term, or decide to use more than one term in the target language to fit different ways that the Key Word is used. One useful way to do this is to keep track of each important term on a spreadsheet, with columns for the source language term, the target language term, alternative terms and the Bible passages where you are using each term. We hope that this feature will be in future versions of translationStudio.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What are the steps I should follow to check someone else's translation?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Steps in Checking a Translation
|
||||
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
|
||||
### Types of things to check
|
||||
|
||||
1. Ask about anything that does not seem right to you, so that the translation team can explain it. If it also does not seem right to them, they can adjust the translation. In general:
|
||||
|
||||
1. Check for anything that appears to be added, that was not a part of the meaning of the source text. (Remember, the original meaning also includes [Implicit Information](../../jit/figs-explicit/01.md).)
|
||||
1. Check for anything that appears to be missing, that was a part of the meaning of the source text but was not included in the translation.
|
||||
1. Check for any meaning that appears to be different than the meaning of the source text.
|
||||
|
||||
1. Check to make sure that the main point or the theme of the passage is clear. Ask the translation team to summarize what the passage is saying or teaching. If they choose a minor point as the primary one, they might need to adjust the way that they translated the passage.
|
||||
1. Check that the different parts of the passage are connected in the right way – that the reasons, additions, results, conclusions, etc. in the Bible passage are marked with the proper connectors in the target language.
|
||||
1. Check for the consistency of the translationWords, as explained in the last section of "Steps in Checking a Translation." Ask how each term is used in the culture – who uses the terms, and on what occasions. Also ask what other terms are similar and what the differences are between the similar terms. This helps the translator to see if some terms might have unwanted meanings, and to see which term might be better, or if they might need to use different terms in different contexts.
|
||||
1. Check figures of speech. Where there is a figure of speech in the Bible text, see how it has been translated and make sure it communicates the same meaning. Where there is a figure of speech in the translation, check to make sure it communicates the same meaning as in the Bible text.
|
||||
1. Check to see how abstract ideas were translated, such as love, forgiveness, joy, etc. Many of these are also Key Words.
|
||||
1. Check the translation of things or practices that might be unknown in the target culture. Showing the translation team pictures of these things and explaining to them what they are is very helpful.
|
||||
1. Discuss the words about the spirit world and how they are understood in the target culture. Make sure that the ones used in the translation communicate the right thing.
|
||||
1. Check anything that you think might be especially difficult to understand or translate in the passage.
|
||||
|
||||
After checking all of these things and making corrections, have the translation team read the passage out loud again to each other or to other members of their community to make sure that everything still flows in a natural way and uses the right connectors. If a correction made something sound unnatural, they will need to make additional adjustments to the translation. This process of testing and revision should repeat until the translation communicates clearly and naturally in the target language.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What types of things should I check?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Types of Things to Check
|
||||
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
|
||||
The unfoldingWord project exists because we want to see **unrestricted biblical content in every language**.
|
||||
|
||||
Jesus commanded his disciples to make disciples of EVERY people group:
|
||||
|
||||
>"Jesus came to them and spoke to them and said, 'All authority has been given to me in heaven and on earth. Go therefore and make disciples of all the nations. Baptize them into the name of the Father, of the Son, and of the Holy Spirit. Teach them to obey all the things that I have commanded you. And see, I am with you always, even to the end of the world.'" (Matthew 28:18-20 ULB)
|
||||
|
||||
We have the promise that people from EVERY language will be in heaven:
|
||||
|
||||
>After these things I saw, and behold, there was a great crowd, which no one was able to number, out of every nation, tribe, people, and language, standing before the throne and before the Lamb. (Revelation 7:9 ULB)
|
||||
|
||||
Understanding the Word of God in one's heart language is important:
|
||||
|
||||
>So faith comes from hearing, and hearing by the word of Christ. (Romans 10:17 ULB)
|
||||
|
||||
### How Do We Do This?
|
||||
|
||||
How do we accomplish the goal of **unrestricted biblical content in every language**?
|
||||
|
||||
* [unfoldingWord Network](https://unfoldingword.org/network/) - By partnering with other like-minded organizations
|
||||
* [Statement of Faith](../statement-of-faith/01.md) - By working with those who have the same beliefs
|
||||
* [Translation Guidelines](../translation-guidelines/01.md) - By using a common translation theory
|
||||
* [Open License](../open-license/01.md) - By releasing everything we create under an open license
|
||||
* [Gateway Languages Strategy](../gl-strategy/01.md) - By making Biblical content available to translate from a known language
|
||||
|
||||
### What Do We Do?
|
||||
|
||||
* **Content** - We create and make available for translation free and unrestricted biblical content. See http://ufw.io/content/ for a complete list of resources and translations. Here are a few samples:
|
||||
* **Open Bible Stories** - a chronological mini-Bible comprising 50 key stories of the Bible, from Creation to Revelation, for evangelism and discipleship, in print, audio, and video (see http://ufw.io/stories/).
|
||||
* **the Bible** - the only inspired, inerrant, sufficient, authoritative Word of God made available under an open license for unrestricted translation, use, and distribution (see http://ufw.io/bible/).
|
||||
* **Translation Notes** - linguistic, cultural, and exegetical helps for translators. They exist for Open Bible Stories and the Bible (see http://ufw.io/tn/).
|
||||
* **Translation Questions** - questions for each chunk of text that translators and checkers can ask to help ensure that their translation is understood correctly. Available for Open Bible Stories and the Bible (see http://ufw.io/tq/).
|
||||
* **Translation Words** - a list of important Biblical terms with a short explanation, cross references, and translation aids. Useful for Open Bible Stories and the Bible (see http://ufw.io/tw/).
|
||||
|
||||
* **Tools** - We create translation, checking, and distribution tools that are free and open-licensed. See http://ufw.io/tools/ for a complete list of tools. Here are a few samples:
|
||||
* **Door43** - an online translation platform where people can collaborate on translation and checking, also the content management system for unfoldingWord (see https://door43.org/).
|
||||
* **translationStudio** - a mobile app and a desktop app where translators can do offline translating (see http://ufw.io/ts/).
|
||||
* **translationKeyboard** - a web and mobile app to help users create and use custom keyboards for languages without them (see http://ufw.io/tk/).
|
||||
* **unfoldingWord app** - a mobile app where translations can be distributed (see http://ufw.io/uw/).
|
||||
* **translationCore** - a program that enables comprehensive checking of Bible translations (see http://ufw.io/tc/).
|
||||
|
||||
* **Training** - We create resources to train mother tongue translation teams. translationAcademy (this resource) is our primary training tool. We also have audio recording and training resources. See http://ufw.io/training/ for a complete list of training materials.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What is the unfoldingWord Project?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
The unfoldingWord Project
|
||||
|
||||
|
|
@ -1,65 +0,0 @@
|
|||
intro-publishing:
|
||||
recommended: []
|
||||
dependencies:
|
||||
- prechecking-training
|
||||
intro-share:
|
||||
recommended:
|
||||
- share-content
|
||||
dependencies:
|
||||
- intro-publishing
|
||||
platforms:
|
||||
recommended:
|
||||
- setup-ts
|
||||
- pretranslation-training
|
||||
dependencies:
|
||||
- process-manual
|
||||
- file-formats
|
||||
prechecking-training:
|
||||
recommended:
|
||||
- intro-check
|
||||
- goal-checking
|
||||
- required-checking
|
||||
dependencies:
|
||||
- pretranslation-training
|
||||
pretranslation-training:
|
||||
recommended:
|
||||
- choose-team
|
||||
- translate-source-text
|
||||
- translate-alphabet
|
||||
- writing-decisions
|
||||
- translation-difficulty
|
||||
dependencies:
|
||||
- translate-process
|
||||
- translate-why
|
||||
process-manual:
|
||||
recommended: []
|
||||
dependencies:
|
||||
- finding-answers
|
||||
required-checking:
|
||||
recommended:
|
||||
- intro-publishing
|
||||
dependencies:
|
||||
- prechecking-training
|
||||
setup-team:
|
||||
recommended:
|
||||
- choose-team
|
||||
- qualifications
|
||||
- translate-source-text
|
||||
- translate-alphabet
|
||||
- writing-decisions
|
||||
- translation-difficulty
|
||||
dependencies:
|
||||
- translate-process
|
||||
setup-ts:
|
||||
recommended: []
|
||||
dependencies:
|
||||
- platforms
|
||||
share-content:
|
||||
recommended: []
|
||||
dependencies:
|
||||
- intro-share
|
||||
source-text-process:
|
||||
recommended:
|
||||
- intro-share
|
||||
dependencies:
|
||||
- intro-publishing
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
|
||||
### Publishing Overview
|
||||
|
||||
Once a work has been uploaded to Door43, it is automatically available online under your user account. This is referred to as self-publishing. You will have access to a web version of your project at http://door43.org/u/user_name/project_name (where user_name is your username and project_name is your translation project). The translationStudio app will give you the correct link when you upload. You can also browse all works on http://door43.org.
|
||||
|
||||
From your Door43 project page you can:
|
||||
|
||||
* See the web version of your project with default formatting
|
||||
* Download documents of your project (like a PDF)
|
||||
* Get the links to the source files (USFM or Markdown) for your project
|
||||
* Interact with others about your project
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What is publishing?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Introduction to Publishing
|
||||
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
|
||||
### Distribution Overview
|
||||
|
||||
Content is worthless unless it is disseminated and used. One advantage of using the Door43 translation and publishing platform is that it provides multiple, simple ways of distributing content.
|
||||
|
||||
### Open License
|
||||
|
||||
The biggest factor that encourages distribution of content is the [Open License](../../intro/open-license/01.md) that is used for all content on Door43. This license gives everybody the freedom they need to:
|
||||
|
||||
* **Share** — copy and redistribute the material in any medium or format
|
||||
* **Adapt** — remix, transform, and build upon the material
|
||||
|
||||
for any purpose, even commercially.
|
||||
|
||||
Under the terms of the license.
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
How can I distribute content?
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Introduction to Distribution
|
||||
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
|
||||
### Recommended Platform
|
||||
|
||||
The recommended platform for doing translation in the Door43 ecosystem is translationStudio (http://ufw.io/ts/). This is where the translation and checking teams will do their work. You may set up translationStudio on Android, Windows, Mac, or Linux devices, (see [Setting up translationStudio](../setup-ts/01.md) for more information).
|
||||
|
||||
### Other Options
|
||||
|
||||
If using translationStudio is not an option for your team, then you may consider using other online or offline tools. Note that it will be your responsibility to get the content into USFM or Markdown format if you do not use translationStudio (see [File Formats](../../translate/file-formats/01.md) for more information).
|
||||
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
What tool can I use to translate?
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue