From bf7deec78873b2b869a7261cadca281a37bde245 Mon Sep 17 00:00:00 2001 From: Perry J Oakes Date: Mon, 8 Jul 2019 14:26:04 +0000 Subject: [PATCH] Perry'sEdits3Q2019 (#186) --- checking/important-term-check/01.md | 34 ++++++++++++++++++++++++----- checking/intro-check/01.md | 9 ++++---- checking/intro-checking/01.md | 20 +++++++---------- checking/peer-check/01.md | 12 ++++++---- checking/peer-check/title.md | 2 +- checking/vol2-intro/01.md | 16 +++++++++++--- checking/vol2-intro/sub-title.md | 2 +- checking/vol2-intro/title.md | 2 +- 8 files changed, 66 insertions(+), 31 deletions(-) diff --git a/checking/important-term-check/01.md b/checking/important-term-check/01.md index 974f0081..0a473eec 100644 --- a/checking/important-term-check/01.md +++ b/checking/important-term-check/01.md @@ -1,8 +1,32 @@ -### How to do a translationWord Check +### How to Do a translationWord Check in translationCore + +* Sign in to translationCore +* Select the project (book of the Bible) that you want to check +* Select the category or categories of words that you want to check +* Select your Gateway Language +* Click "Launch" +* Work through the list of words on the left by following the instructions that appear to the right of the Bible verse. +* To understand the source word better, you can read the short definition in the blue bar, or the longer one in the panel on the right side. +* After selecting (highlighting) the translation for the word or phrase in the list, click "Save." +* Consider whether or not the term that was chosen for the translationWord makes sense in this context. +* If you think that the translation for the translationWord is a good translation, then click "Save and Continue." +* If you think that there is a problem with the verse or that the translation for the word or phrase is not good, then either edit the verse to make it better, or make a comment telling someone who will review your work what you think might be wrong with the translation here. +* If you have made an edit, you may need to make your selection again. +* When you are finished making your edit or comment, click "Save and Continue." If you prefer to only make a comment about a translationWord and not make a selection for it, then click on the next verse in the list on the left to go on to the next word. + +After a selection has been made for all of the verses where a translationWord occurs, the list for that word can be reviewed. The instructions that follow are for the reviewer or for the translation team. + +* You will now be able to see a list of the translations that were made for each translationWord under each translationWord on the left. If you see that the translationWord was translated in different ways in different verses, you will want to review the places that have differences to see if the target term used was the correct one for each context. +* You will also want to review any comments that were made by others. To do that, click the funnel symbol to the right of "Menu" at the upper left. A list will open, including the word "Comments." +* Click the box next to "Comments." This will make all verses that do not have comments in them disappear. +* To read the comments, click on the first verse in the list. +* Click on "Comment." +* Read the comment, and decide what you will do about it. +* If you decide to make an edit to the verse, then click "Cancel" and then "Edit Verse." This will open a small screen where you can edit the verse. +* When you are finished making the edit, select the reason for the change, and then click "Save." +* Continue this process until you have acted on all of the comments that were left for you. + +If you are unsure if a translation for a certain translationWord is correct in a certain context, it might be helpful to consult the translationWord spreadsheet that the translation team made as they were creating the translation. You may also want to discuss a difficult term with others on the translation team and try to find a solution together. You may need to use a different term in some contexts, or find another way to communicate the translationWord, such as using a longer phrase. -* Make a list of the translationWords in the story or Bible passage that you translate, along with the term that you choose for it in the target language. It is best if you can do this on a chart so that you can list the source word or phrase in one column and the target word or phrase in another column. Further columns could list equivalent terms in other languages and the references where these terms occur in the Bible. Make sure that everyone translating Bible books that use these terms has access to the chart so that you can all use the same words or phrases in your translation. -* Use the list of words and definitions in the translationWords section of Door43 or translationStudio to help you to make a list of these words and to understand what they mean. -* Each time the translationWord occurs in the source text, make sure that the term you have chosen for the translation still makes sense in that context. If it does not, discuss the problem with others on the translation team and try to find a solution together. You may need to use a different term, or you may need to use more than one term for the different contexts, or you may need to find another way to communicate the translationWord that includes all of the meanings, such as using a longer phrase. -* When you have decided that you need to use different target language words or phrases to translate one source language translationWord in different contexts, then make a new line on the chart for each different way that you are translating the source translationWord. Repeat the source term in the source column, and put the new translation in the next column, under the first translation. Share this chart with everyone on the translation team so that they can choose the right translation for the source translationWord in the context that they are translating. diff --git a/checking/intro-check/01.md b/checking/intro-check/01.md index 43646665..34b6e38a 100644 --- a/checking/intro-check/01.md +++ b/checking/intro-check/01.md @@ -1,10 +1,11 @@ ### Translation Checking Manual -This manual describes how to check translated biblical content for accuracy, clarity, and naturalness. +This manual describes how to check Bible translations in Other Languages (OLs) for accuracy, clarity, and naturalness. The Manual also discusses the importance of obtaining approval for the translation and the translation process from the church leaders of the language area. +The manual begins with instructions for checking the translation that the translation team will use to check each other’s work. These checks include the oral partner check and the team oral chunk check. Then there are instructions for the translation team to use for checking the translation with the Translation Core software. These include the Translation Words and Translation Notes checks. -The manual begins with instructions for checking the translation that the translation team will use to check each other’s work. If they follow these instructions, they will complete checking level one. Then there are instructions for the translation team to use for checking the translation with the language community for clarity and naturalness, and for church leaders to use when they check the translation for accuracy. If they follow these instructions, they will complete checking level two. This manual also contains instructions for the leaders of church networks to use for checking the translation for accuracy at level three. +After this, the translation team will need to check the translation with the language community for clarity and naturalness. This is necessary because other speakers of the language can often 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. +Another check that the translation team can do at this point is the OL pastor’s check. Since the OL pastors are familiar with the Bible in the Gateway Language (GL), they can check the translation for accuracy to the GL Bible. They can also catch mistakes that the translation team did not see because the translation team is so close to and involved in their work. Also, the translation team may lack some of the expertise or knowledge of the Bible that other OL pastors might have who are not part of the translation team. In this way, the whole language community can work together to make sure that the Bible translation is accurate, clear, and natural in the target language. - -The manual also includes further instructions for checking the translation that the leaders of church networks can use to check the translation. Because many leaders of church networks do not speak the language of the translation, there are also instructions for creating a back translation, which allows people to check a translation in a language that they do not speak. \ No newline at end of file +A further check for the accuracy of the Bible translation is to align it to the original languages of the Bible using the Word Alignment tool in Translation Core. After all of these checks have been performed and the translation has been aligned, the leaders of the OL church networks will want to review the translation and give their endorsement. Because many leaders of church networks do not speak the language of the translation, there are also instructions for creating a back translation, which allows people to check a translation in a language that they do not speak. \ No newline at end of file diff --git a/checking/intro-checking/01.md b/checking/intro-checking/01.md index 181bef37..d884a055 100644 --- a/checking/intro-checking/01.md +++ b/checking/intro-checking/01.md @@ -3,28 +3,24 @@ #### Introduction +##### Why do we do Translation Checking? + As part of the translation process, it is necessary that several people check the translation to make sure that it is clearly communicating the message that it should communicate. A beginning translator who was told to check his translation once said, “But I speak my native language perfectly. The translation is for that language. What more is needed?” What he said was true, but there are two more things to keep in mind. One thing is that he may not have understood the source text correctly, and so someone who knows what it should say might be able to correct the translation. This could be because he did not correctly understand a phrase or expression in the source language. In this case, someone else who understands the source language well can correct the translation. Or it could be that he did not understand something about what the Bible meant to communicate at a certain place. In this case, someone who knows the Bible well, such as a Bible teacher or a Bible translation checker, can correct the translation. -The other thing is that, although the translator may know very well what the text should say, the way he translated it might mean something else to a different person. That is, another person might think that the translation is talking about something other than what the translator intended, or the person hearing or reading the translation might not understand what the translator was trying to say. That is why it is always necessary to check what someone else understands from the translation so that we can make it more accurate and more clear. +The other thing is that, although the translator may know very well what the text should say, the way he translated it might mean something else to a different person. That is, another person might think that the translation is talking about something other than what the translator intended, or the person hearing or reading the translation might not understand what the translator was trying to say. -This is a guide to the process of checking, in the form of a scale with three levels. +It often happens when one person writes a sentence and then another person reads it (or sometimes even if the first person reads it again later), that they understand it to say something different from what the writer meant. Take the following sentence as an example. -This checking scale helps to show the extent to which the accuracy and clarity of a translation have been verified. These checking levels have been developed by the unfoldingWord project (see https://unfoldingword.bible ), the same group that manages Door43 with the help of many volunteers, and they are used to indicate the checking level of all biblical content on Door43. +John took Peter to the temple and then he went home. -#### The Checking Levels +In his mind when he wrote it, the writer meant that Peter went home, but the reader thought that the writer probably meant that it was John who went home. The sentence needs to be changed so that it is more clear. -There are three checking levels: +Also, the translation team is very close to and involved in their work, and so they sometimes do not see mistakes that others can see more easily. For these reasons, it is always necessary to check what someone else understands from the translation so that we can make it more accurate and more clear. -* [Checking Level One - Affirmation by Translation Team](../level1/01.md) -* [Checking Level Two - Affirmation by Community](../level2/01.md) -* [Checking Level Three - Affirmation by Church Leadership](../level3/01.md). - -Any translation that has not yet been checked to Level One is considered to have not been checked and is assigned no checking status. - -The purpose of having several Checking Levels is to make translated materials quickly available to the church, while also allowing the content to continue to be checked and corroborated in an open environment. At all times, the degree to which its accuracy has been checked will be clearly indicated. We believe this will result in a faster checking process, allow broad church participation and ownership, and produce better translations. +This Checking Manual is a guide to the process of checking. It will guide you through several kinds of checks that will allow you to fix these problems. We believe that having many people doing a variety of different checks will result in a faster checking process, allow broad church participation and ownership, and produce better translations. *Credits: Quotation used by permission, © 2013, SIL International, Sharing Our Native Culture, p. 69.* diff --git a/checking/peer-check/01.md b/checking/peer-check/01.md index 8224ccdc..1b618aee 100644 --- a/checking/peer-check/01.md +++ b/checking/peer-check/01.md @@ -1,7 +1,11 @@ -### How to do a Peer Check +### How to do an Oral Partner Check -* Give your translation to a member of the translation team who did not work on this passage. Have that person go through all of the same steps of the Self Check, making note of any places that need fixing. -* Review the translation together and fix those places. -* Read the revised translation out loud to this person and fix anything that does not sound like it is the way that someone from your community would say it. +At this point, you have already gone through the steps of drafting your translation. Now you are ready for others to help you to check it, find any errors or problems, and make it better. To do so, follow these steps. +* Read your translation to a partner (a member of the translation team) who did not work on this passage. +* The partner can listen first for naturalness and tell you which parts do not sound natural in your language. Together, you can think of how someone would say that meaning in your language. +* Use those ideas to change the unnatural parts of your translation to be more natural. +* Then read the passage to your partner again. This time, the partner can listen to the translation while following along in the source text. +* Your partner can tell you if there is any part where something was added, missing, or changed when compared to the source text. +* Correct those parts of the translation. diff --git a/checking/peer-check/title.md b/checking/peer-check/title.md index e179a3c8..a55e09bc 100644 --- a/checking/peer-check/title.md +++ b/checking/peer-check/title.md @@ -1 +1 @@ -Peer Check \ No newline at end of file +Oral Partner Check \ No newline at end of file diff --git a/checking/vol2-intro/01.md b/checking/vol2-intro/01.md index 0adeafe1..daa2c1c3 100644 --- a/checking/vol2-intro/01.md +++ b/checking/vol2-intro/01.md @@ -1,6 +1,16 @@ -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. +To do a Team Oral Chunk Check, each translator will read his translation out loud to the rest of the team. At the end of each chunk, the translator will stop so that the team can discuss that chunk. Ideally, each written translation is projected where all can see it while the translator reads the text orally. -For Level Two and Level Three, the translation team needs to bring 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, and so they sometimes do not see 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. +The duties of the team members are divided - it is important that each team member only plays one of the following roles at a time. +* One or more team members listen for naturalness. If something is unnatural, at the end of reading the chunk, they recommend a more natural way to say it. +* One or more team members follow along in the source text, noting anything that is added, missing, or changed. At the end of reading the chunk, they alert the team that something is added, missing, or changed. +* Another team member follows along in the report mode of translationCore, noting all of the highlighted key terms in the source text. The team then discusses any key terms in the translation that seem inconsistent or inappropriate, along with any other problems that surface in the reading. If this mode is not available, this team member can look up the key terms on the team's key term spreadsheet. + +These steps can be repeated as necessary until the team is satisfied with their translation. + +At this point, the translation is considered a first draft, and the team needs to also do the following. + +* Someone on the translation team needs to enter the text into translationStudio. If the team has been using translationStudio from the beginning of drafting, then all that needs to be entered at this point are the changes that the team has made. +* A new audio recording should be made of the translation, incorporating all of the changes and improvements that the team has made. +* The translationStudio files and the audio recording should be uploaded to the team repository on Door43. -The rest of this manual will go over the guidelines that the church leaders can use to guide them in checking the translation for both Level Two and Level Three. \ No newline at end of file diff --git a/checking/vol2-intro/sub-title.md b/checking/vol2-intro/sub-title.md index 9f4507b0..b922c58a 100644 --- a/checking/vol2-intro/sub-title.md +++ b/checking/vol2-intro/sub-title.md @@ -1 +1 @@ -Why should I check someone else’s translation? \ No newline at end of file +#### How do I do a Team Oral Chunk Check? \ No newline at end of file diff --git a/checking/vol2-intro/title.md b/checking/vol2-intro/title.md index 19a7b4d8..c7880dd4 100644 --- a/checking/vol2-intro/title.md +++ b/checking/vol2-intro/title.md @@ -1 +1 @@ -Introduction to Translation Checking - Part 2 \ No newline at end of file +### Team Oral Chunk Check \ No newline at end of file