DCS-Mirror
/
unfoldingWord_en_glm
mirror of https://git.door43.org/unfoldingWord/en_glm
2
0
Fork 0
Files Issues Releases Wiki Activity See in Reader

Initial conversion to rst and readthedocs

This commit is contained in:
Jesse Griffin 2018-02-15 12:40:59 -05:00
parent c3fc80ac98
commit d23b69cbc2
23 changed files with 1396 additions and 651 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored Normal file
View File

@ -0,0 +1 @@
docs/_build/

8
CONTRIBUTORS.md
View File

@ -1,8 +0,0 @@
# Overview
This file lists everyone who has contributed to the creation of this translationAcademy manual
If you have contributed, please add your name below. Please put one name (or pseudonym) per line in bullet style. You may also include your credentials after your name.
# Contributors

27
content/check_notes.md
View File

@ -1,27 +0,0 @@
---
title: Checking translationNotes
question: What are the guidelines for checking translationNotes?
manual: gateway
volume: 3
slug: check_notes
dependencies: ["vol2_steps", "vol2_things_to_check", "gl_notes"]
status: drafted
tags:
recommended: ["check_udb", "check_ulb"]
original_url:
credits:
---
When checking translationNotes, remember that tN are very closely tied to the text of the ULB. The purpose of tN is to explain any phrases or sentences in the ULB that are hard to understand or hard to translate.
### What Should Be Checked?
In addition to the things mentioned in [Types of Things to Check](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md), tN need to be checked in these areas.
1. Although the GL tN are a translation of the English tN, it is important that the phrase in each Note that reproduces the phrase from the ULB is exactly the same as it is in the GL ULB. So you must check the meaning of the Note in the English tN and make sure that the GL tN has the same meaning. Then you must also check the wording of the phrase that comes from the GL ULB and make sure that the words are exactly the same.
1. In the same way, make sure that any quotations of the UDB have the exact wording of the GL UDB.
1. Check that the GL tN makes sense with the GL ULB. It is possible that the GL translator made a good translation of the English tN, but when the Note is read with the new GL ULB, it might not explain the GL ULB in the right way, or it might not make sense with the GL ULB. In that case, you will need to discuss the problem with the translator. Then you will need to decide how to change the Note so that it explains the GL ULB in a way that will be helpful to the OL translator.
1. Check that all references to the UDB make sense with the GL UDB.
1. If the GL translator has decided that a Note does not apply to the GL ULB and has deleted the note from the GL tN, check to make sure that the Note was not needed.
1. If the GL translator has written a new Note, check to make sure that it was needed, and that it makes sense with the GL ULB.
In order to check the tN for naturalness and clarity, you will need to have people read them together with the GL ULB and UDB. Then ask them to mark anything that is not clear to them, or that they would say in a different way. Then give this feedback to the translator so that he can make those places clearer and more natural.

32
content/check_udb.md
View File

@ -1,32 +0,0 @@
---
title: Checking the UDB
question: What are the guidelines for checking the UDB?
manual: gateway
volume: 3
slug: check_udb
dependencies: ["vol2_steps", "vol2_things_to_check", "gl_udb"]
status: drafted
tags:
recommended: ["gl_notes", "check_udb", "check_notes"]
original_url:
credits:
---
When checking the UDB, remember that the UDB does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the UDB is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible. When you are checking the GL translation of the UDB, you must only compare it to the English UDB. Do not refer to any other version of the Bible when checking the UDB. The GL translation of the UDB will not be as smooth and natural as the Gateway Language Bible that you are used to, because it does not use many of the forms of expression that make a language sound natural. These forms of expression are different for every language. So please do not try to make the UDB sound like your favorite translation of the Bible in your language.
### What Should Be Checked in the UDB?
In addition to the things mentioned in [Types of Things to Check](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md), the UDB needs to be checked in these areas. For definitions and examples of these things, see [Translating the UDB](https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_udb.md):
1. **Sentence length** - If you see any long or complex sentences in the Gateway Language UDB, see how you might break them up into shorter sentences.
1. **Passive voice** - If you see this construction in the Gateway Language UDB, check to see what it was in the English source UDB and change it so that it is active.
1. **Abstract Nouns** - If you see one of these in the Gateway Language UDB, check to see what it was in the English source UDB and change it back to an action or description word.
1. **Events out of order** - Make sure that the events in the Gateway UDB are in the order that they occurred. Also make sure that the logical flow of arguments, such as occur in many of the New Testament letters, is in a natural order that makes sense in the GL.
1. **Figures of speech and idioms** - Make sure that the GL UDB does not contain any figures of speech or idioms. Instead, it should use only plain, clear language.
If you see any of these forms in the English UDB, email <help@door43.org> to let them know of the error.
It is also useful to check the UDB for clarity with speakers of the Gateway Language, but do not confuse clarity with naturalness (see below). You can read a passage from the UDB to a speaker of the Gateway Language, and ask if the meaning is clear. If they say, "Yes," that is enough. If they also say, "But I would say it differently," that is fine. We expect that they would say it differently. But the UDB needs to say it in a plain way. As long as the meaning of the GL UDB is clear, it is a successful translation.
### What Should Not Be Checked in the UDB?
It is not necessary to check the UDB for naturalness with speakers of the Gateway Language. The UDB will very often not be completely natural, because it avoids some forms that languages naturally use, such as idioms and figures of speech. The UDB avoids these because they are specific to individual languages, and do not translate well from one language to another.

26
content/check_ulb.md
View File

@ -1,26 +0,0 @@
---
title: Checking the ULB
question: What are the guidelines for checking the ULB?
manual: gateway
volume: 3
slug: check_ulb
dependencies: ["vol2_steps", "vol2_things_to_check", "gl_adaptulb", "gl_ulb"]
status: drafted
tags:
recommended: ["gl_notes", "check_udb", "check_notes"]
original_url:
credits:
---
When checking the ULB, remember that the ULB needs to retain the original grammatical forms (as far as possible), the idioms, and the figures of speech of the original so that the OL translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a Gateway Language (GL) translation of the ULB, then the OL translator will never see them and the Notes about them will not make sense. When you are checking the GL translation of the ULB, you must only compare it to the English ULB. Do not refer to any other version of the Bible when checking the ULB. The GL translation of the ULB will not be as smooth and clear as the Gateway Language Bible that you are used to, because it is showing the OL translator the forms of the original biblical languages. Please do not try to make the ULB sound like your favorite translation of the Bible in your language.
### What Should Be Checked in the ULB?
In addition to the things mentioned in [Types of Things to Check](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md), the ULB needs to be checked in these areas:
1. **Idioms** - If there is an idiom in the source ULB, then that same idiom should be in the target ULB. If the idiom does not make sense in the target language, make sure that there is a Note that explains its meaning. If there is not a note for it, then write one in the Gateway Language translationNotes that explains its meaning.
1. **Figures of Speech** - If there is a figure of speech in the source ULB, then that same figure of speech should be in the target ULB. If the figure of speech does not make sense in the target language, make sure that there is a Note that explains its meaning. If there is not a note for it, then write one in the Gateway Language translationNotes that explains its meaning.
1. **Grammatical Forms** - Check to see if the grammatical forms, that is, the order of words in the sentence or the way that the words are arranged, is the same in the target Gateway Language ULB as they are in the English source ULB. If the words are arranged differently, ask yourself if they could be arranged the same as the words in the English ULB and still make good sense, or if it is necessary for them to be arranged in a different way in the Gateway Language ULB. If they would still make good sense in a way that an Other Language translator would understand, then put them in the same arrangement as in the English. If they are in a different arrangement because that is what makes sense in the target Gateway Language, then leave them in the different arrangement.
### What Should Not Be Checked in the ULB?
It is not necessary to check the ULB for naturalness with speakers of the Gateway Language. The ULB will not be natural in some cases, because it is designed to retain the forms of the biblical languages, as far as the Gateway Language allows.

22
content/gl_academy.md
View File

@ -1,22 +0,0 @@
---
title: Translating translationAcademy
question: What are the guidelines for translating translationAcademy?
manual: gateway
volume: 3
slug: gl_academy
dependencies: ["ta_intro", "gl_strategy", "gl_notes", "gl_ulb"]
status: drafted
tags:
recommended: ["check_ulb", "check_notes"]
original_url:
credits:
---
### Recommended Training and Experience
translationAcademy contains many lessons on specialized topics, such as language, translation issues, biblical studies, software, and audio equipment. Some of the vocabulary is also specialized. We recommend that the people who translate tA into a Gateway Language have a **college-level education or some training and experience in the particular area that they are translating**. For example, if you are translating the Translation Manual, it would be good if you have training and experience in linguistics and translation. If you are translating the Audio Manual, it would be good if you have training and experience using audio equipment. You will be able to translate more accurately and clearly if you have experience in the topic.
This means that you will want to have **several specialists** on your translation team, with each specialist translating the parts that they are most familiar with. If you find that some lessons are unclear, discuss the problem with other members of the team until you understand what the lesson is trying to teach. You cannot translate something that you do not understand. If you try to do that, the Other Language translator will not be able to understand or use it.
### Recommended Reference Materials
We recommend that you use specialized dictionaries as you translate to hep you understand the concepts that you are translating. Do not use unusual or technical words in your translation if there is a simpler way to communicate the same thing. Remember that the OL translators speaks the Gateway Language as a second language, they will not know unusual or technical words. Try to keep the lessons uncomplicated and clear, using simple language as much as you can. We have tried to write the lessons of tA using simple language, so please follow this same style.

46
content/gl_adaptulb.md
View File

@ -1,46 +0,0 @@
---
title: Adapt the ULB
question: What are the guidelines for adapting an existing translation as the ULB?
manual: gateway
volume: 3
slug: gl_adaptulb
dependencies: ["gl_ulb", "gl_udb", "gl_translate"]
status: drafted
tags:
recommended: ["gl_notes", "open_license"]
original_url:
credits:
---
### Prerequisites for Adapting an Existing Translation for the ULB
**What is needed to adapt an existing translation and use it as the ULB for a Gateway Language (GL)?**
In order to adapt an existing translation and use it as the ULB for a Gateway Language (GL), it is necessary that the existing translation be a literal translation. That is, it should follow the same order of clauses as the original biblical languages and reproduce the original biblical idioms and figures of speech. Most Bibles that were translated into Gateway Languages in the first half of the twentieth century or earlier are literal translations.
It is also necessary that the Bible that you adapt as the ULB not be encumbered by copyright. That means that it must be in the public domain or have a license that permits us to reproduce and translate it. (For more information on copyrights and licensing, see [Open License](https://git.door43.org/Door43/en-ta-intro/src/master/content/open_license.md).)
If the Bible is very old, you will need to update the language and the style so that it uses words that people use now and "talks" in the way that people talk now. Even though the ULB has a literal style, it must use words that people know so that they can understand it.
### Methodology for Adapting an Existing Translation for the ULB
**What are the steps for adapting an existing translation for the ULB?**
Because adapting an existing translation is a process of editing rather than of translating, the first four steps of the MAST process cannot be used for this. Especially do not use the step of blind drafting. Instead, you should follow these steps:
1. Read the chapter in the English ULB and the Notes for that chapter. If you are beginning to translate a book, also read the overview of the book.
1. Read the chapter in the Bible that you are adapting as the ULB.
1. Go through the chapter and change old words to words that people use now.
1. Using the list of translationWords for that chapter, check to make sure that a good translation for each of those words is used in the Gateway Language ULB.
1. If some sentences are put together in a strange way, check to see if they are also that way in the English ULB.
1. If the sentences are also put together in that same strange way in the English ULB, it is because the original Bible has that structure. Leave them as they are. There will be a Note that will explain that structure.
1. If the sentences are not put together in that same strange way in the English ULB, then change the sentence so that it is clearer for modern readers.
1. If you see that any verse or phrase in the Bible that you are adapting is very different than the English ULB, then change it so that it is more like the English ULB.
1. If you see that any verse is missing in the Bible that you are adapting but it is there in the English ULB, then translate that verse from the English ULB.
After you do these things so that the text is ready to use as the Gateway Language ULB, you will need to translate the translationNotes. As you translate the translationNotes, you may see that there are parts of your adapted ULB that should be different so that the translationNote can make sense. Also, you may see that some translationNotes need to be changed so that they can refer to the right parts of the adapted ULB. In this way, you will need to make changes to both the Gateway Language ULB and the Notes as you adapt them to each other so that they make sense and are truly helpful for the OL translator. (For more information about this process, see [Translate the translationNotes](https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_notes.md).)
#### Does Adapting a Translation of the ULB Require a Back Translation?
**How does the church ensure the translation conforms to these guidelines?**
We expect that the translation that has been adapted as the ULB already went through a series of checks to ensure that it accurately reflects the original meaning of the biblical text. This would have been done by the entity that originally translated and published the Bible translation. We also expect that the people adapting this translation for use as the ULB in the Gateway Language will be well-educated and have good theological training. They will also be connected into church networks that will have adequate resources for checking the adapted translation. For this reason, back translations of the adapted ULB will usually not be necessary. The exception to this will be if the adaptation of the translation is done by a secular translation company, and there is no church network that speaks the Gateway Language that is available to check the adaptation. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.

49
content/gl_done_checking.md
View File

@ -1,49 +0,0 @@
---
title: Finishing Checking
question: How do I know when I have finished the checking for each level?
manual: gateway
volume: 3
slug: gl_done_checking
dependencies: ["gl_translate", "vol2_steps", "vol2_things_to_check"]
status: drafted
tags:
recommended: ["self_assessment", "intro_publishing", "source_text_process"]
original_url:
credits:
---
It can be difficult to know when you have sufficiently checked a text for errors or for ways that it could be improved. In a sense, this process is never completely finished, and people continually find ways to improve texts that have been checked already by many people. For example, there are many Bible translations in English that have been checked by many biblical scholars and are considered to be excellent translations. Yet it is possible to find places where they could be made better, and over time, they are continually revised and new versions are published. This is the process that you should expect to happen with these Bible translations, as well.
### Checking Evaluation Lists
The following lists can help you to consider whether or not you have checked a GL resource sufficiently.
#### Level One
Level one checking includes:
* Initial study of the related materials, including:
* The guidelines for translation of the specific materials in the Gateway Languages Manual
* The translationNotes
* The definitions of translationWords
* Reading each chapter connected to the translated materials in both ULB and UDB
* Careful comparison with the source text, including:
* Individual self edit
* Peer edit
* Key word check as a team
* Accuracy check as a team
* Final editing, including everything learned from the earlier editing sessions, the translationNotes, and the definitions of translationWords
#### Level Two
In addition to the steps listed above for level one, all parts of the resource have been checked by at least 2 respected church leaders, preferably pastors, who are mother-tongue speakers of the target language and bilingual in English. Also, these people are from different denominations and must not have been involved in translating the resource. These people can attest:
* The Translation conforms to the Statement of Faith (see https://ufw.io/faith ) and Translation Guidelines (see http://ufw.io/guidelines ).
* The Translation accurately communicates the content of the source document in the target language.
* The style of the Translation conforms to the guidelines set forth for translation of this resource in the Gateway Languages Manual.
* The translation team has edited the Translation to their satisfaction.
#### Level Three
For level three, at least 2 more people need to have checked every part of the resource. These people must meet the following criteria: people who were not involved in the translation, were not part of the checking process of level two for that resource, and are bilingual in English. In addition, these people are leaders of different church networks or denominations who are either Bible scholars themselves or who can delegate the level 3 checking to trusted associates who are Bible scholars, able to compare the GL translations with the original biblical languages. They also need to affirm the same statements as in level two.
Additional questions that can help you to evaluate if the translation has been sufficiently checked are in [Self-Assessment Rubric](https://git.door43.org/Door43/en-ta-checking-vol1/src/master/content/self_assessment.md). Just be aware that the ULB and the UDB are not intended to be completely natural in the Gateway Language.

54
content/gl_notes.md
View File

@ -1,54 +0,0 @@
---
title: Translate the translationNotes
question: What are the guidelines for translating or adapting the translationNotes?
manual: gateway
volume: 3
slug: gl_notes
dependencies: ["gl_adaptulb", "gl_ulb"]
status: drafted
tags:
recommended: ["resources_types", "gl_words", "check_notes"]
original_url:
credits:
---
### Why
translationNotes offer alternative ways to translate a phrase from the ULB. It is important that the phrase that you use to translate this kind of translationNote be a direct substitute for the phrase that it replaces in the ULB. In other words, the phrase has to have the same grammatical construction as the phrase in the ULB. That is, it needs to fit into the sentence in the ULB just like the original phrase did. In order to make sure that the phrase in the GL Note fits the sentence in the GL ULB, you must be able to always look at both the English translationNote and the GL ULB as you translate. Translating the translationNotes while having the source visible, therefore, is the most efficient way to translate them and this will also reduce the number of errors in translation. (For more information on the types of translationNotes, see [Using the translationNotes](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/resources_types.md).)
### Guidelines
#### Does the entire Bible need translated first?
It is not necessary to have the **entire** ULB and UDB Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
#### When I am translating the notes, do I need the ULB and UDB available and translated?
When you translate the translationNotes for the Bible, you must also have both the ULB and the UDB in front of you, already translated into the target Gateway Language. You must have the ULB available so that you can copy the part of the ULB text that the translationNote is talking about directly into the translationNote. You must also have the UDB text already translated and available, because the translationNotes often copy part of the UDB text in order to show another way to translate the same part of the verse. Other times, the translationNote does not quote the UDB but it does refer to it. In that case, you need to be able to see what the UDB says in order to translate the translationNote in the best way.
In addition, the translationNotes directly comment on parts of the ULB text, so you must read the part of the ULB text that the translationNote comments on in order to properly translate the translationNote. After you read and understand the ULB text, then you can translate the translationNote so that it makes sense together with the ULB text that it refers to.
#### May I use blind drafting?
Do not use the method of blind drafting to translate the translationNotes. Always translate the translationNotes with the Gateway Language ULB and UDB in front of you, and the English translationNotes also visible. This is because you must copy the ULB phrase into the translationNote exactly as it is in the ULB, and you must also copy the UDB phrase if the translationNote also quotes the UDB.
#### How does the church ensure the translation conforms to these guidelines?
We expect that the people translating the translationNotes into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the translationNotes will usually not be necessary. The exception to this will be if the translation of the translationNotes is done by a secular translation company. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
### Adapting the translationNotes
#### May I change a note so that it makes sense in my language?
Often, the ULB in the target Gateway Language will say things in a different way than the ULB said them in English. In order for the translationNote to be useful in the target Gateway Language, you will need to adapt the translationNote so that it talks about the text of the ULB as it is in the Gateway Language translation. This means that you will need to copy the phrase of the Gateway ULB that is the translation of the same phrase from the English ULB into the translationNote, and then sometimes change the translationNote so that it makes sense and is helpful for the Other Language translator who will use these translationNotes as translation tools.
#### May I delete a note that does not apply to my language?
Because languages can be very different from each other, sometimes there will be translationNotes that are important and necessary for some languages, but that are not needed for other languages. If there is a translationNote that does not make sense when applied to the ULB text in the target Gateway Language, then you as the translator will need to modify the translationNote so that it does make sense in relation to the ULB in your target Gateway Language. If the translationNote does not apply at all to the target GL text of the ULB, then you may delete that note from your translation of the translationNotes. But be sure to think about it very carefully before you delete a translationNote, to be sure that it is not necessary for the GL translation.
#### May I add a note that would help with translation in my language?
For the same reason, sometimes you will realize that the Other Language translator will need a translationNote in order to understand a phrase in the target Gateway Language ULB, but there might not be a translationNote already written for that phrase, because it was not necessary for the English ULB. In that case, you will need to write a new translationNote and include it in your translation. Usually these translationNotes will be to explain a phrase or way of saying something that is normal in the Gateway Language but that is not normal in the Other Languages that you know of. When writing your translationNote, follow the same style and format of the existing translationNotes.
Remember that speakers of many different languages will be using these Gateway Language translationNotes to help them translate the Bible. There will be many things that you will understand about the Bible in the Gateway Language that the OL translator may not understand. For that reason, if you think that there is something difficult to understand in the GL ULB, write a translationNote that can help the OL translator to understand it. There will probably be many Other Language translators who will benefit from reading the translationNote and who will make a better translation because of it.
Because the translationNotes need to be adapted in these ways and not simply translated, it is best if the people adapting the translationNotes be people who are well educated in biblical studies so that they can understand the various problems that the translationNotes explain.

44
content/gl_questions.md
View File

@ -1,44 +0,0 @@
---
title: Translating translationQuestions
question: What are the guidelines for translating translationQuestions?
manual: gateway
volume: 3
slug: gl_questions
dependencies: ["mast", "gl_words", "gl_notes", "gl_ulb"]
status: drafted
tags:
recommended: ["check_ulb", "check_notes"]
original_url:
credits:
---
### Why
We want all translations of the Bible to communicate clearly the message that God wants them to communicate. One tool that we are providing so that the OL translators can make sure that their translations are communicating correctly is translationQuestions (tQ). The OL translators will use tQ to conduct community checks of each chapter of the Bible that they translate.
### Guidelines
#### Does the entire Bible need to be translated first?
It is not necessary to have the **entire** ULB and UDB Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
#### MAST Method
1. Read the chapter of the ULB that the Questions are about, so that you understand it.
1. Draft each Question with its answer as one chunk. Work through the Questions for that chapter of the ULB, translating each pair of questions and answers.
1. When you finish translating each question-answer pair for that chapter, go back and do the checking steps, comparing your translation with the English source questions and answers.
1. Now compare your translation of each answer with the Gateway Language ULB of that verse. It is important that your answer to each Question match very closely to the words of the ULB. At this step, you may need to adjust the words of your answers so that they are the same as the words of the ULB. This is so the OL translators and checkers of the OL translation can use your questions and answers and easily see if the their translation is communicating the right message. When the words of your answer are the same as the words of the ULB, the OL checker can see where that answer is in the translation and know what part of their translation they need to make more clear if the person answering the question gives a different answer.
#### Modified MAST Method
This is an alternative method for translating tQ.
1. Read the chapter of the ULB that the Questions are about, so that you understand it.
1. Translate only the question part of each question-answer pair using the MAST method of blind drafting. Each Question will be one chunk. Draft all of Questions for one chapter.
1. In the self-edit stage of checking, edit each Question to correct any mistakes or to add things that you left out.
1. Now copy the answer to each question from the words of the Gateway Language ULB of that verse that match the answer to that question in the English source. In this way, the words of each answer will always match the words of the Gateway Language ULB.
You may want to try both methods and see which one works best for you.
#### If the ULB Has Not Been Translated
If the ULB has not been translated already, an alternative method would be to translate the ULB together with the other resources, chunk by chunk. In this case, for each chunk of text, you would translate the ULB and the UDB of those verses, then tN, tW, and tQ for those same verses. Then you would move to the next chunk and translate each of the resources for that chunk, as well. After you finish drafting all of the resources for one chunk, then go back and do the checking steps for all of the resources for that chunk.

34
content/gl_translate.md
View File

@ -1,34 +0,0 @@
---
title: Translating in the Gateways
question: What must be translated in the Gateway Languages?
manual: gateway
volume: 3
slug: gl_translate
dependencies: ["gl_strategy", "open_license"]
status: drafted
tags:
recommended: ["gl_ulb", "gl_udb", "translation_difficulty"]
original_url:
credits:
---
### What Needs To Be Translated
The following materials must be translated into the gateway languages and checked to the levels stated.
* translationAcademy vol 1 & vol 2 - Level 2
* Open Bible Stories text - Level 3
* OBS translationNotes - Level 3
* OBS translationQuestions - Level 2
* ULB Text - Level 3
* UDB Text - Level 3
* Bible translationNotes - Level 3
* Bible translationQuestions - Level 2
* translationWords - Level 2
It is important that you translate the text of the ULB and the UDB before you translate tN and tQ. However, another good method would be to translate all of the translation resources for each chunk of the Bible together. In this case, for each chunk of text, you would translate the ULB and the UDB of those verses, then tN, tW, and tQ for those same verses. Then you would move to the next chunk and translate each of the resources for that chunk, as well, in that order. (For information about which books of the Bible to translate first, see [Choosing What to Translate](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/translation_difficulty.md).)
### Why Translate Two Bibles into the Gateway Languages?
Some people might ask this question, because adequate Bibles already exist in most of the Gateway languages. However, these are end-user Bibles, designed to be read and studied by people who speak those languages in their homes and churches. The Bibles that we are translating are not end-user Bibles. They are Bibles designed to be used in conjunction with each other and with the other translation helps as a set of tools that will allow speakers of other languages to use them to translate a Bible into their own languages. What they produce from these tools will be an end-user Bible.
To make an end-user Bible, it is always best to translate from more than one version, so that the translator does not fall into the habit of following the form of any one version too closely. Also, it is always possible to translate something in more than one way in a target language, and often the biblical language has more than one possible meaning. Looking at multiple versions that between them reveal these differences gives the translator a window into those things that a single version would not give. This benefit is maximized when the two (or more) source Bibles use very different styles, such as literal and dynamic. Having a literal version and a dynamic version side by side give the translator a "three-dimensional" view into the original text, allowing him to see both the form and the meaning at the same time. It is for this purpose that we are providing the ULB and the UDB.

100
content/gl_udb.md
View File

@ -1,100 +0,0 @@
---
title: Translating the UDB
question: What are the guidelines for translating the UDB?
manual: gateway
volume: 3
slug: gl_udb
dependencies: ["gl_strategy", "gl_translate", "gl_ulb"]
status: drafted
tags:
recommended: ["gl_notes", "check_udb"]
original_url:
credits:
---
### Translation Theory for Translating the UDB
The *Unlocked Dynamic Bible* (UDB) is designed to be used in conjunction with the *Unlocked Literal Bible* (ULB) and the translationNotes as a tool for Bible translation. Unlike the ULB and unlike an end-user Bible, the UDB does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the UDB is to show the plain meaning of all of those things wherever they occur in the ULB. Because the UDB lacks these things, it is not a beautiful end-user Bible. An end-user Bible will use the figures of speech and idioms that speak naturally and beautifully in the target language, but the UDB does not use them. As the Other Language translator uses both the UDB and the ULB together as his translation source, he will be able to see the figures of speech, idioms, and other forms of the original Bible in the ULB and also see what their meaning is in the UDB. Then he can use the figures of speech or other forms from the ULB that are clear and natural in his language. When the forms in the ULB are not clear or natural in his language, then he can choose other forms in his language that have the same meaning as the UDB translation or the Notes. When translating the UDB, please do not use idioms, figures of speech, or difficult grammatical forms in the Gateway Language translation. The purpose of the UDB is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible.
The UDB avoids using long or complex sentences. In many languages, long or complex sentences are unnatural and unclear. When translating the UDB, keep the sentences short and simple.
The UDB often fills in the participants when these are lacking in the original Bible and the ULB. In the original biblical languages, these participants could be left out and still understood by the reader. But in many languages these must be included for the translation to be clear and natural. When translating the UDB, therefore, be sure to include all of the participants that are there in the UDB.
### What method should be used to translate the UDB?
When translating the UDB, keep the English source open in front of you. This means that if you are translating using MAST methodology, do not use the step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the UDB is a tool that carefully avoids certain structures that can be difficult to translate in some languages, as explained above. If the translator is using blind drafting, he might accidentally replace the simple structures of the UDB with structures that are natural in the target Gateway Language but unwanted in the UDB, such as idioms and figures of speech from the target GL. In order to guard against replacing these structures, it is best to translate the UDB with the English source text open to look at.
### Does Translation of the UDB Require a Back Translation?
We expect that the people translating the UDB into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the UDB will usually not be necessary. The exception to this will be if the translation of the UDB is done by a secular translation company. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
### Examples
The following are examples of ways that the text of the Bible can be unclear for some languages and what the UDB does to overcome those problems. When you translate the UDB, make sure that your translation of the UDB also avoids these problems.
#### Passive Voice
Passive voice is a grammatical construction that is common in Greek and English but it is not used in many other languages, so it can be very confusing. For that reason, it is not used in the UDB. In passive voice, the receiver of the action changes places with the actor. In English, the actor normally comes first in the sentence. But in passive voice, the receiver of the action comes first. Often, the actor is left unstated. In that case, the UDB will fill in the actor. See "Missing Participants" below.
For example, the ULB of Romans 2:24 says, "... the name of God is dishonored among the Gentiles because of you."
The action is "dishonor," the actors are "the Gentiles" (non-Jews), and the receiver of the action is "the name of God." The reason for the action is "because of you."
The UDB rearranges the verse to put the actor and the receiver of the action in a more normal order. It says, "The non-Jews speak evil about God because of the evil actions of you Jews." This is more clear for many languages. When you translate the UDB, make sure that you do not use any passive voice constructions.
#### Abstract Nouns
The ULB of Romans 2:10 says, "But praise, honor, and peace will come to everyone who practices good..."
In this verse, the words "praise," "honor," "peace," and "good" are abstract nouns. That is, they are words that refer to things that we cannot see or touch. They are ideas. The ideas that these nouns express are closer to actions or descriptions than they are to things. In many languages, therefore, these ideas must be expressed by verbs or description words, not by nouns.
For this reason, the UDB expresses these nouns as actions or descriptions. It says, "But God will praise, honor, and give a peaceful spirit to every person who habitually does good deeds."
When translating the UDB, avoid using abstract nouns. For more information on abstract nouns, see [Abstract Nouns](https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_abstractnouns.md).
#### Long, Complex Sentences
The ULB translates the first three verses of Romans as one complex sentence. It says, "<sup>1</sup> Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God, <sup>2</sup> which he promised beforehand by his prophets in the holy scriptures, <sup>3</sup> concerning his Son, who was born from the descendants of David according to the flesh."
The UDB breaks that into five sentences that are more simple in form. It says, "<sup>1</sup> I, Paul, who serve Christ Jesus, am writing this letter to all of you believers in the city of Rome. God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him. <sup>2</sup> Long before Jesus came to earth, God promised that he would reveal this good news by means of what his prophets wrote in the sacred scriptures. <sup>3</sup> This good news is about his Son. As to his Son's physical nature, he was born a descendant of King David."
When translating the UDB, keep the sentences short and simple.
#### Missing Participants
In the ULB, Romans 1:1 says, "Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God..."
In this verse, there is a participant that is left unstated, but still understood. This participant is God. It is God who called Paul to be an apostle and who set him apart for the Gospel. In some languages, this participant must be stated.
Therefore the UDB of Romans 1:1 says, "God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him."
When translating the UDB, be sure to include all of the participants that are there in the UDB.
#### Events out of Order
The ULB of Luke 2:6-7 says, "<sup>6</sup> Now it came about that while they were there, the time came for her to deliver her baby. <sup>7</sup> She gave birth to a son, her firstborn child, and she wrapped him snugly in strips of cloth. Then she put him in an animal feeding trough, because there was no room for them in a guest room."
In some languages, events need to be told in the order in which they happened, or else the story will be confusing and hard to understand. People might understand from these verses that Mary delivered her baby outside in the street, and then looked for somewhere to stay and, after a long search, ended up putting him in an animal feeding trough.
The UDB tells these events in the order in which they happened, so that it is clear that Mary was already in the shelter for animals when she gave birth. It says, "<sup>6-7</sup> When they arrived in Bethlehem, there was no place for them to stay in a place where visitors usually stayed. So they had to stay in a place where animals slept overnight. While they were there the time came for Mary to give birth and she gave birth to her first child, a son. She wrapped him in wide strips of cloth and placed him in the feeding place for the animals."
#### Figures of Speech
The ULB of Romans 2:21 says, "You who preach not to steal, do you steal?"
This is a figure of speech called a rhetorical question. It is not a real question that is used to seek an answer. It is used to make a point. In this case, Paul is using it to scold his audience and to condemn their hypocrisy. Many languages do not use rhetorical questions, or they do not use them in this way.
To show how to translate this meaning without a rhetorical question, the UDB says, "You who preach that people should not steal things, it is disgusting that you yourself steal things!"
When you translate the UDB, be sure to not use rhetorical questions or other figures of speech. (For more examples of figures of speech, see [Figures of Speech](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_intro.md) and the modules linked there.)
#### Idioms
The ULB of Deuteronomy 32:10 says, "he guarded him as the apple of his eye."
The word "apple" here does not refer to a kind of fruit, but instead refers to the pupil, the dark center of a person's eye. The phrase "the apple of his eye" is an idiom that refers to anything that is extremely precious to a person, or the one thing that is the most precious to a person. In many languages this idiom makes no sense, but they have other idioms that have this meaning. The Other Language translator should use one of these idioms from the target language in the OL translation, but there should be no idiom in the translation of the UDB.
To show the meaning of this verse, the UDB expresses this in plain language, without an idiom. It says, "He protected them and took care of them, as every person takes good care of his own eyes."
The Notes add another way to translate this that makes the meaning clear. It says, "He protected the people of Israel as something most valuable and precious." When you translate the UDB, be sure that you do not use any idioms. Only use plain language that makes the meaning clear. (For more information on idioms, see [Idiom](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_idiom.md).)
(For more examples of how the UDB avoids difficult grammatical constructions, idioms, and figures of speech, see the section of examples in [Translating the ULB](https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_ulb.md).)

56
content/gl_ulb.md
View File

@ -1,56 +0,0 @@
---
title: Translating the ULB
question: What are the guidelines for translating the ULB?
manual: gateway
volume: 3
slug: gl_ulb
dependencies: ["gl_strategy", "gl_translate"]
status: drafted
tags:
recommended: ["gl_adaptulb", "gl_udb"]
original_url:
credits:
---
### Translation Theory for Translating the ULB
The *Unlocked Literal Bible* (ULB) is designed to be used in conjunction with the translationNotes and the *Unlocked Dynamic Bible* (UDB) as a tool for Bible translation. Unlike the UDB and unlike an end-user Bible, the ULB is designed to reflect the forms of the source languages, so that the Other Language (OL) translator can see what they are. By using the ULB, the OL translator can "look through" it to see how the original Bible expressed the biblical ideas. As you translate the ULB, therefore, you must try to retain the grammatical and syntactic structures of the original as far as the target language (Gateway Language) will allow. If the original structure does not make sense in the target language, then you will need to change it into a structure that does make sense. It does no good to make a translation that the OL translator using this tool will not be able to understand. But as far as the target language will allow, retain the structures of the original in your translation of the ULB.
### What method should be used to translate the ULB?
When translating the ULB, keep the English source open in front of you. This means that if you are translating using MAST methodology, do not use the step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the ULB is a tool that must retain the original, biblical language structures in order to be useful to the translator. The best way to guard these structures is to translate with the English source ULB open in front of you so that you can be sure to keep these structures as they are in the English ULB, as far as the target language will allow.
#### Does Translation of the ULB Require a Back Translation?
We expect that the people translating the ULB into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the ULB will usually not be necessary. The exception to this will be if the translation of the ULB is done by a secular translation company. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
### What are the structures of the ULB that should be retained?
The translation of the ULB needs to retain the original grammatical forms (as far as is possible), the idioms, and the figures of speech of the original so that the OL translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a Gateway Language (GL) translation of the ULB, then the OL translator will never see them and the translationNotes about them will not make sense. Keep in mind that the ULB and the UDB are only going to be translated into the GLs, because they are translation tools for the use of the OL translator. We want these tools to be as useful as possible. For the ULB, this means that it should retain structures that we would not always retain in an end-user Bible. The GL translator must understand that this translation will lack naturalness and sometimes also lack clarity because it is aiming at reproducing these original language structures and figures of speech that may not translate well into the GL. Wherever the ULB translation lacks clarity, however, there should also be a translationNote to explain the meaning of the structure for the OL translator. The translationNotes and the UDB will provide the meaning wherever that meaning is in doubt in the ULB. In this way, the tools will work together to provide the OL translator with a full set of information about both the form and the meaning of the original Bible.
### Examples
#### Grammatical Forms
The ULB of Luke 2:47 reproduces a grammatical form from the Greek source language that is also natural in English, but that might not be natural in other languages. When talking about the boy Jesus at the temple, it says, "All who heard him were amazed at his understanding and his answers." The nouns "understanding" and "answers" refer to events, not things, and so must be translated as verbs in many languages.
The UDB of the same verse gives an example of how these nouns can be translated as verbs. It says, "All the people who heard what he said were amazed at how much he *understood* and how well he *answered* the questions that the teachers asked."
When translating the ULB, however, these nouns should be translated as nouns if that will make sense in the target language.
#### Idioms
The ULB of Matthew 2:20 reproduces an idiom from the Greek source language. It refers to Herod and his soldiers who were trying to kill the child Jesus as, "those who sought the child's life." In some languages this is clear, and in others it is not.
The UDB of the same verse tries to make the meaning clear by translating this idiom as, "the people who were trying to kill the child."
When translating the ULB, however, this idiom should be translated as it is, so that the Other Language translator can consider it and use it if it makes sense. The UDB and the translationNotes will provide the meaning.
#### Figures of Speech
The ULB of John 1:17 reproduces a figure of speech from the Greek source language. It says, "grace and truth came through Jesus Christ." (This figure of speech is called "personification;" see [Personification](https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_personification.md).) This figure of speech talks as if grace and truth were like people who can come and go, and it talks as if Jesus Christ were like a doorway that they can come through. In some languages this makes sense, but in other languages it does not. The plain meaning is that Jesus Christ acted toward us with grace and taught us true things about God.
The UDB of the same verse tries to make this plain meaning clear by translating it as, "Jesus Christ was kind to us far beyond what we deserved and taught us true things about God."
When translating the ULB, however, this figure of speech should be translated as it is, so that the Other Language translator can consider it and use it if it makes sense. If it does not, the UDB provides an alternative way to translate it.

42
content/gl_words.md
View File

@ -1,42 +0,0 @@
---
title: Translating translationWords
question: What are the guidelines for translating translationWords?
manual: gateway
volume: 3
slug: gl_words
dependencies: ["gl_notes", "gl_ulb", "gl_adaptulb"]
status: drafted
tags:
recommended: ["gl_questions"]
original_url:
credits:
---
### Why
It is important that the Other Language translators understand all of the words that they are translating. But some of the words in the Bible are not used in everyday life in our time or in our cultures, and so the translator may not be familiar with them. Other words are used in everyday life, but they are used in a different way in the Bible. Some of these words have very important or special meanings in the Bible. They tell us a lot about God and his relationship with us. So in order for the Other Language translator to completely understand these words, we have provided the definitions in translationWords. When you translate this list into the Gateway Language, it will help all of the Other Language translators who will use it to translate the Bible for their people with good understanding.
### Guidelines
#### Does the entire Bible need translated first?
It is not necessary to have the **entire** ULB and UDB Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
#### What is the "Definition" section of translationWords?
tW definitions have several parts, the first part is "Definition." This gives the meaning of the word as it is used in the Bible. Please do not use definitions from a modern Gateway Language dictionary, because the way words are used in the Bible can be different from the way they are used in modern, everyday life. We want to make sure that the Other Language translator understands the way that the word is used in the Bible.
It is possible that the Gateway Language might express the meaning of the English word by different words, with each of those words having part of the meaning of the English word. In this case, you will need to list each of those words at the top, separated by commas. Several of the English tW entries already have multiple words at the top like this, such as "prophet, prophecy, prophesy, seer, prophetess" (see https://door43.org/en/obe/kt/prophet ). Then, in the "Definition" part, you will need to list those words in separate paragraphs with a definition for each one. The Other Language translator can then choose the word that he needs to understand from that list and translate it correctly in the passage that he is translating.
#### What is the "Translation Suggestions" section of translationWords?
The second part of a tW entry is "Translation Suggestions" or "Translation Strategies." This section gives different ideas for how the Other Language translator can translate the word. This section gives more than one way to translate the word because it can mean slightly different things in different contexts. Be sure that you understand the differences of meaning between the different contexts in which the word is used so that you can translate them correctly.
In the Gateway Language, some of the tW are not used in all of the same contexts as the English tW are. **In that case, you will need to adjust your translation**. If one of the Translation Suggestions does not work in the Gateway Language, then do not translate that Translation Suggestion. Instead, write a Translation Suggestion that shows how that word is used in the Gateway Language. Think about the different ways that the word is used in the Bible, and try to make sure that there is a Translation Suggestion for each of the primary uses. We want the Other Language translator to see and consider the differences and the similarity in meaning between the uses of the word so that he can choose the best word in his language to express those meanings.
As you translate the ULB and UDB, you may find that you need to add a meaning to a word in the tW entry, or you may need to add another word to the entry because the Gateway Language uses more than one word for the idea of that important tW. Go ahead and do this as you find more words or meanings for the words.
Under the "Translation Suggestions" or "Translation Strategies" section is a line that says, "(See also...)." You only need to translate the words "See also," and you only need to translate this one time, not for every tW. The rest of the line will be created automatically, if the translation is done in translationStudio Desktop.
#### Do I translate the "Bible References" and "Examples for the Bible Stories" sections of translationWords?
The third and fourth parts are "Bible References" and "Examples from the Bible Stories." You only need to translate these words of the titles, and you only need to translate them one time, not for every tW. You do not need to translate the rest of these parts. They will be created automatically, if the translation is done in translationStudio Desktop.

225
docs/Makefile Normal file
View File

@ -0,0 +1,225 @@
# Makefile for Sphinx documentation
#
# You can set these variables from the command line.
SPHINXOPTS =
SPHINXBUILD = sphinx-build
PAPER =
BUILDDIR = _build
# Internal variables.
PAPEROPT_a4 = -D latex_paper_size=a4
PAPEROPT_letter = -D latex_paper_size=letter
ALLSPHINXOPTS = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
# the i18n builder cannot share the environment and doctrees with the others
I18NSPHINXOPTS = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
.PHONY: help
help:
@echo "Please use \`make <target>' where <target> is one of"
@echo " html to make standalone HTML files"
@echo " dirhtml to make HTML files named index.html in directories"
@echo " singlehtml to make a single large HTML file"
@echo " pickle to make pickle files"
@echo " json to make JSON files"
@echo " htmlhelp to make HTML files and a HTML help project"
@echo " qthelp to make HTML files and a qthelp project"
@echo " applehelp to make an Apple Help Book"
@echo " devhelp to make HTML files and a Devhelp project"
@echo " epub to make an epub"
@echo " epub3 to make an epub3"
@echo " latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
@echo " latexpdf to make LaTeX files and run them through pdflatex"
@echo " latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
@echo " text to make text files"
@echo " man to make manual pages"
@echo " texinfo to make Texinfo files"
@echo " info to make Texinfo files and run them through makeinfo"
@echo " gettext to make PO message catalogs"
@echo " changes to make an overview of all changed/added/deprecated items"
@echo " xml to make Docutils-native XML files"
@echo " pseudoxml to make pseudoxml-XML files for display purposes"
@echo " linkcheck to check all external links for integrity"
@echo " doctest to run all doctests embedded in the documentation (if enabled)"
@echo " coverage to run coverage check of the documentation (if enabled)"
@echo " dummy to check syntax errors of document sources"
.PHONY: clean
clean:
rm -rf $(BUILDDIR)/*
.PHONY: html
html:
$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
.PHONY: dirhtml
dirhtml:
$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
@echo
@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
.PHONY: singlehtml
singlehtml:
$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
@echo
@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
.PHONY: pickle
pickle:
$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
@echo
@echo "Build finished; now you can process the pickle files."
.PHONY: json
json:
$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
@echo
@echo "Build finished; now you can process the JSON files."
.PHONY: htmlhelp
htmlhelp:
$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
@echo
@echo "Build finished; now you can run HTML Help Workshop with the" \
".hhp project file in $(BUILDDIR)/htmlhelp."
.PHONY: qthelp
qthelp:
$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
@echo
@echo "Build finished; now you can run "qcollectiongenerator" with the" \
".qhcp project file in $(BUILDDIR)/qthelp, like this:"
@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/ResourceContainer.qhcp"
@echo "To view the help file:"
@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/ResourceContainer.qhc"
.PHONY: applehelp
applehelp:
$(SPHINXBUILD) -b applehelp $(ALLSPHINXOPTS) $(BUILDDIR)/applehelp
@echo
@echo "Build finished. The help book is in $(BUILDDIR)/applehelp."
@echo "N.B. You won't be able to view it unless you put it in" \
"~/Library/Documentation/Help or install it in your application" \
"bundle."
.PHONY: devhelp
devhelp:
$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
@echo
@echo "Build finished."
@echo "To view the help file:"
@echo "# mkdir -p $$HOME/.local/share/devhelp/ResourceContainer"
@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/ResourceContainer"
@echo "# devhelp"
.PHONY: epub
epub:
$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
@echo
@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
.PHONY: epub3
epub3:
$(SPHINXBUILD) -b epub3 $(ALLSPHINXOPTS) $(BUILDDIR)/epub3
@echo
@echo "Build finished. The epub3 file is in $(BUILDDIR)/epub3."
.PHONY: latex
latex:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo
@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
@echo "Run \`make' in that directory to run these through (pdf)latex" \
"(use \`make latexpdf' here to do that automatically)."
.PHONY: latexpdf
latexpdf:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through pdflatex..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
.PHONY: latexpdfja
latexpdfja:
$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
@echo "Running LaTeX files through platex and dvipdfmx..."
$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
.PHONY: text
text:
$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
@echo
@echo "Build finished. The text files are in $(BUILDDIR)/text."
.PHONY: man
man:
$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
@echo
@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
.PHONY: texinfo
texinfo:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo
@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
@echo "Run \`make' in that directory to run these through makeinfo" \
"(use \`make info' here to do that automatically)."
.PHONY: info
info:
$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
@echo "Running Texinfo files through makeinfo..."
make -C $(BUILDDIR)/texinfo info
@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
.PHONY: gettext
gettext:
$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
@echo
@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
.PHONY: changes
changes:
$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
@echo
@echo "The overview file is in $(BUILDDIR)/changes."
.PHONY: linkcheck
linkcheck:
$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
@echo
@echo "Link check complete; look for any errors in the above output " \
"or in $(BUILDDIR)/linkcheck/output.txt."
.PHONY: doctest
doctest:
$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
@echo "Testing of doctests in the sources finished, look at the " \
"results in $(BUILDDIR)/doctest/output.txt."
.PHONY: coverage
coverage:
$(SPHINXBUILD) -b coverage $(ALLSPHINXOPTS) $(BUILDDIR)/coverage
@echo "Testing of coverage in the sources finished, look at the " \
"results in $(BUILDDIR)/coverage/python.txt."
.PHONY: xml
xml:
$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
@echo
@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
.PHONY: pseudoxml
pseudoxml:
$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
@echo
@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."
.PHONY: dummy
dummy:
$(SPHINXBUILD) -b dummy $(ALLSPHINXOPTS) $(BUILDDIR)/dummy
@echo
@echo "Build finished. Dummy builder generates no files."

341
docs/conf.py Normal file
View File

@ -0,0 +1,341 @@
# -*- coding: utf-8 -*-
#
# Resource Container documentation build configuration file, created by
# sphinx-quickstart on Tue Sep 20 15:27:28 2016.
#
# This file is execfile()d with the current directory set to its
# containing dir.
#
# Note that not all possible configuration values are present in this
# autogenerated file.
#
# All configuration values have a default; values that are commented out
# serve to show the default.
# If extensions (or modules to document with autodoc) are in another directory,
# add these directories to sys.path here. If the directory is relative to the
# documentation root, use os.path.abspath to make it absolute, like shown here.
#
# import os
# import sys
# sys.path.insert(0, os.path.abspath('.'))
# -- General configuration ------------------------------------------------
# If your documentation needs a minimal Sphinx version, state it here.
#
# needs_sphinx = '1.0'
# Add any Sphinx extension module names here, as strings. They can be
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
# ones.
extensions = []
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
# The suffix(es) of source filenames.
# You can specify multiple suffix as a list of string:
#
# source_suffix = ['.rst', '.md']
source_suffix = '.rst'
# The encoding of source files.
#
# source_encoding = 'utf-8-sig'
# The master toctree document.
master_doc = 'index'
# General information about the project.
project = u'Gateway Language Manual'
copyright = u'2018, unfoldingWord'
author = u'unfoldingWord'
# The version info for the project you're documenting, acts as replacement for
# |version| and |release|, also used in various other places throughout the
# built documents.
#
# The short X.Y version.
version = u'0.1'
# The full version, including alpha/beta/rc tags.
release = u'0.1'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
#
# This is also used if you do content translation via gettext catalogs.
# Usually you set "language" from the command line for these cases.
language = None
# There are two options for replacing |today|: either, you set today to some
# non-false value, then it is used:
#
# today = ''
#
# Else, today_fmt is used as the format for a strftime call.
#
# today_fmt = '%B %d, %Y'
# List of patterns, relative to source directory, that match files and
# directories to ignore when looking for source files.
# This patterns also effect to html_static_path and html_extra_path
exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
# The reST default role (used for this markup: `text`) to use for all
# documents.
#
# default_role = None
# If true, '()' will be appended to :func: etc. cross-reference text.
#
# add_function_parentheses = True
# If true, the current module name will be prepended to all description
# unit titles (such as .. function::).
#
# add_module_names = True
# If true, sectionauthor and moduleauthor directives will be shown in the
# output. They are ignored by default.
#
# show_authors = False
# The name of the Pygments (syntax highlighting) style to use.
pygments_style = 'sphinx'
# A list of ignored prefixes for module index sorting.
# modindex_common_prefix = []
# If true, keep warnings as "system message" paragraphs in the built documents.
# keep_warnings = False
# If true, `todo` and `todoList` produce output, else they produce nothing.
todo_include_todos = False
# -- Options for HTML output ----------------------------------------------
# The theme to use for HTML and HTML Help pages. See the documentation for
# a list of builtin themes.
#
#html_theme = 'alabaster'
import sphinx_rtd_theme
html_theme = "sphinx_rtd_theme"
html_theme_path = [sphinx_rtd_theme.get_html_theme_path()]
# Theme options are theme-specific and customize the look and feel of a theme
# further. For a list of options available for each theme, see the
# documentation.
#
# html_theme_options = {}
# Add any paths that contain custom themes here, relative to this directory.
# html_theme_path = []
# The name for this set of Sphinx documents.
# "<project> v<release> documentation" by default.
#
# html_title = u''
# A shorter title for the navigation bar. Default is the same as html_title.
#
# html_short_title = None
# The name of an image file (relative to this directory) to place at the top
# of the sidebar.
#
# html_logo = None
# The name of an image file (relative to this directory) to use as a favicon of
# the docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
# pixels large.
#
# html_favicon = None
# Add any paths that contain custom static files (such as style sheets) here,
# relative to this directory. They are copied after the builtin static files,
# so a file named "default.css" will overwrite the builtin "default.css".
html_static_path = ['_static']
# Add any extra paths that contain custom files (such as robots.txt or
# .htaccess) here, relative to this directory. These files are copied
# directly to the root of the documentation.
#
# html_extra_path = []
# If not None, a 'Last updated on:' timestamp is inserted at every page
# bottom, using the given strftime format.
# The empty string is equivalent to '%b %d, %Y'.
#
# html_last_updated_fmt = None
# If true, SmartyPants will be used to convert quotes and dashes to
# typographically correct entities.
#
# html_use_smartypants = True
# Custom sidebar templates, maps document names to template names.
#
# html_sidebars = {}
# Additional templates that should be rendered to pages, maps page names to
# template names.
#
# html_additional_pages = {}
# If false, no module index is generated.
#
# html_domain_indices = True
# If false, no index is generated.
#
# html_use_index = True
# If true, the index is split into individual pages for each letter.
#
# html_split_index = False
# If true, links to the reST sources are added to the pages.
#
# html_show_sourcelink = True
# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
#
# html_show_sphinx = True
# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
#
# html_show_copyright = True
# If true, an OpenSearch description file will be output, and all pages will
# contain a <link> tag referring to it. The value of this option must be the
# base URL from which the finished HTML is served.
#
# html_use_opensearch = ''
# This is the file name suffix for HTML files (e.g. ".xhtml").
# html_file_suffix = None
# Language to be used for generating the HTML full-text search index.
# Sphinx supports the following languages:
# 'da', 'de', 'en', 'es', 'fi', 'fr', 'hu', 'it', 'ja'
# 'nl', 'no', 'pt', 'ro', 'ru', 'sv', 'tr', 'zh'
#
# html_search_language = 'en'
# A dictionary with options for the search language support, empty by default.
# 'ja' uses this config value.
# 'zh' user can custom change `jieba` dictionary path.
#
# html_search_options = {'type': 'default'}
# The name of a javascript file (relative to the configuration directory) that
# implements a search results scorer. If empty, the default will be used.
#
# html_search_scorer = 'scorer.js'
# Output file base name for HTML help builder.
htmlhelp_basename = 'GLManual'
# -- Options for LaTeX output ---------------------------------------------
latex_elements = {
# The paper size ('letterpaper' or 'a4paper').
#
# 'papersize': 'letterpaper',
# The font size ('10pt', '11pt' or '12pt').
#
# 'pointsize': '10pt',
# Additional stuff for the LaTeX preamble.
#
# 'preamble': '',
# Latex figure (float) alignment
#
# 'figure_align': 'htbp',
}
# Grouping the document tree into LaTeX files. List of tuples
# (source start file, target name, title,
# author, documentclass [howto, manual, or own class]).
latex_documents = [
(master_doc, 'GLManual.tex', u'Gateway Language Manual',
u'unfoldingWord', 'manual'),
]
# The name of an image file (relative to this directory) to place at the top of
# the title page.
#
# latex_logo = None
# For "manual" documents, if this is true, then toplevel headings are parts,
# not chapters.
#
# latex_use_parts = False
# If true, show page references after internal links.
#
# latex_show_pagerefs = False
# If true, show URL addresses after external links.
#
# latex_show_urls = False
# Documents to append as an appendix to all manuals.
#
# latex_appendices = []
# It false, will not define \strong, \code, itleref, \crossref ... but only
# \sphinxstrong, ..., \sphinxtitleref, ... To help avoid clash with user added
# packages.
#
# latex_keep_old_macro_names = True
# If false, no module index is generated.
#
# latex_domain_indices = True
# -- Options for manual page output ---------------------------------------
# One entry per manual page. List of tuples
# (source start file, name, description, authors, manual section).
man_pages = [
(master_doc, 'GatewayLanguageManual', u'Gateway Language Manual',
[author], 1)
]
# If true, show URL addresses after external links.
#
# man_show_urls = False
# -- Options for Texinfo output -------------------------------------------
# Grouping the document tree into Texinfo files. List of tuples
# (source start file, target name, title, author,
# dir menu entry, description, category)
texinfo_documents = [
(master_doc, 'GatewayLanguageManual', u'Gateway Language Manual',
author, 'GatewayLanguageManual', 'One line description of project.',
'Miscellaneous'),
]
# Documents to append as an appendix to all manuals.
#
# texinfo_appendices = []
# If false, no module index is generated.
#
# texinfo_domain_indices = True
# How to display URL addresses: 'footnote', 'no', or 'inline'.
#
# texinfo_show_urls = 'footnote'
# If true, do not generate a @detailmenu in the "Top" node's menu.
#
# texinfo_no_detailmenu = False

125
docs/gl_checking.rst Normal file
View File

@ -0,0 +1,125 @@
Checking Gateway Language Materials
===================================
Checking the ULB
----------------
question: What are the guidelines for checking the ULB?
dependencies: ["vol2_steps", "vol2_things_to_check", "gl_adaptulb", "gl_ulb"]
recommended: ["gl_notes", "check_udb", "check_notes"]
When checking the ULB, remember that the ULB needs to retain the original grammatical forms (as far as possible), the idioms, and the figures of speech of the original so that the OL translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a Gateway Language (GL) translation of the ULB, then the OL translator will never see them and the Notes about them will not make sense. When you are checking the GL translation of the ULB, you must only compare it to the English ULB. Do not refer to any other version of the Bible when checking the ULB. The GL translation of the ULB will not be as smooth and clear as the Gateway Language Bible that you are used to, because it is showing the OL translator the forms of the original biblical languages. Please do not try to make the ULB sound like your favorite translation of the Bible in your language.
What Should Be Checked in the ULB?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In addition to the things mentioned in [Types of Things to Check](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md), the ULB needs to be checked in these areas:
1. **Idioms** - If there is an idiom in the source ULB, then that same idiom should be in the target ULB. If the idiom does not make sense in the target language, make sure that there is a Note that explains its meaning. If there is not a note for it, then write one in the Gateway Language translationNotes that explains its meaning.
1. **Figures of Speech** - If there is a figure of speech in the source ULB, then that same figure of speech should be in the target ULB. If the figure of speech does not make sense in the target language, make sure that there is a Note that explains its meaning. If there is not a note for it, then write one in the Gateway Language translationNotes that explains its meaning.
1. **Grammatical Forms** - Check to see if the grammatical forms, that is, the order of words in the sentence or the way that the words are arranged, is the same in the target Gateway Language ULB as they are in the English source ULB. If the words are arranged differently, ask yourself if they could be arranged the same as the words in the English ULB and still make good sense, or if it is necessary for them to be arranged in a different way in the Gateway Language ULB. If they would still make good sense in a way that an Other Language translator would understand, then put them in the same arrangement as in the English. If they are in a different arrangement because that is what makes sense in the target Gateway Language, then leave them in the different arrangement.
What Should Not Be Checked in the ULB?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is not necessary to check the ULB for naturalness with speakers of the Gateway Language. The ULB will not be natural in some cases, because it is designed to retain the forms of the biblical languages, as far as the Gateway Language allows.
Checking the UDB
----------------
question: What are the guidelines for checking the UDB?
dependencies: ["vol2_steps", "vol2_things_to_check", "gl_udb"]
recommended: ["gl_notes", "check_udb", "check_notes"]
When checking the UDB, remember that the UDB does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the UDB is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible. When you are checking the GL translation of the UDB, you must only compare it to the English UDB. Do not refer to any other version of the Bible when checking the UDB. The GL translation of the UDB will not be as smooth and natural as the Gateway Language Bible that you are used to, because it does not use many of the forms of expression that make a language sound natural. These forms of expression are different for every language. So please do not try to make the UDB sound like your favorite translation of the Bible in your language.
What Should Be Checked in the UDB?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In addition to the things mentioned in [Types of Things to Check](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md), the UDB needs to be checked in these areas. For definitions and examples of these things, see [Translating the UDB](https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_udb.md):
1. **Sentence length** - If you see any long or complex sentences in the Gateway Language UDB, see how you might break them up into shorter sentences.
1. **Passive voice** - If you see this construction in the Gateway Language UDB, check to see what it was in the English source UDB and change it so that it is active.
1. **Abstract Nouns** - If you see one of these in the Gateway Language UDB, check to see what it was in the English source UDB and change it back to an action or description word.
1. **Events out of order** - Make sure that the events in the Gateway UDB are in the order that they occurred. Also make sure that the logical flow of arguments, such as occur in many of the New Testament letters, is in a natural order that makes sense in the GL.
1. **Figures of speech and idioms** - Make sure that the GL UDB does not contain any figures of speech or idioms. Instead, it should use only plain, clear language.
If you see any of these forms in the English UDB, email <help@door43.org> to let them know of the error.
It is also useful to check the UDB for clarity with speakers of the Gateway Language, but do not confuse clarity with naturalness (see below). You can read a passage from the UDB to a speaker of the Gateway Language, and ask if the meaning is clear. If they say, "Yes," that is enough. If they also say, "But I would say it differently," that is fine. We expect that they would say it differently. But the UDB needs to say it in a plain way. As long as the meaning of the GL UDB is clear, it is a successful translation.
What Should Not Be Checked in the UDB?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is not necessary to check the UDB for naturalness with speakers of the Gateway Language. The UDB will very often not be completely natural, because it avoids some forms that languages naturally use, such as idioms and figures of speech. The UDB avoids these because they are specific to individual languages, and do not translate well from one language to another.
Checking translationNotes
-------------------------
question: What are the guidelines for checking translationNotes?
dependencies: ["vol2_steps", "vol2_things_to_check", "gl_notes"]
recommended: ["check_udb", "check_ulb"]
When checking translationNotes, remember that tN are very closely tied to the text of the ULB. The purpose of tN is to explain any phrases or sentences in the ULB that are hard to understand or hard to translate.
What Should Be Checked?
^^^^^^^^^^^^^^^^^^^^^^^
In addition to the things mentioned in [Types of Things to Check](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md), tN need to be checked in these areas.
1. Although the GL tN are a translation of the English tN, it is important that the phrase in each Note that reproduces the phrase from the ULB is exactly the same as it is in the GL ULB. So you must check the meaning of the Note in the English tN and make sure that the GL tN has the same meaning. Then you must also check the wording of the phrase that comes from the GL ULB and make sure that the words are exactly the same.
1. In the same way, make sure that any quotations of the UDB have the exact wording of the GL UDB.
1. Check that the GL tN makes sense with the GL ULB. It is possible that the GL translator made a good translation of the English tN, but when the Note is read with the new GL ULB, it might not explain the GL ULB in the right way, or it might not make sense with the GL ULB. In that case, you will need to discuss the problem with the translator. Then you will need to decide how to change the Note so that it explains the GL ULB in a way that will be helpful to the OL translator.
1. Check that all references to the UDB make sense with the GL UDB.
1. If the GL translator has decided that a Note does not apply to the GL ULB and has deleted the note from the GL tN, check to make sure that the Note was not needed.
1. If the GL translator has written a new Note, check to make sure that it was needed, and that it makes sense with the GL ULB.
In order to check the tN for naturalness and clarity, you will need to have people read them together with the GL ULB and UDB. Then ask them to mark anything that is not clear to them, or that they would say in a different way. Then give this feedback to the translator so that he can make those places clearer and more natural.
Finishing Checking
------------------
question: How do I know when I have finished the checking for each level?
dependencies: ["gl_translate", "vol2_steps", "vol2_things_to_check"]
recommended: ["self_assessment", "intro_publishing", "source_text_process"]
It can be difficult to know when you have sufficiently checked a text for errors or for ways that it could be improved. In a sense, this process is never completely finished, and people continually find ways to improve texts that have been checked already by many people. For example, there are many Bible translations in English that have been checked by many biblical scholars and are considered to be excellent translations. Yet it is possible to find places where they could be made better, and over time, they are continually revised and new versions are published. This is the process that you should expect to happen with these Bible translations, as well.
Checking Evaluation Lists
^^^^^^^^^^^^^^^^^^^^^^^^^
The following lists can help you to consider whether or not you have checked a GL resource sufficiently.
Level One
"""""""""
Level one checking includes:
* Initial study of the related materials, including:
* The guidelines for translation of the specific materials in the Gateway Languages Manual
* The translationNotes
* The definitions of translationWords
* Reading each chapter connected to the translated materials in both ULB and UDB
* Careful comparison with the source text, including:
* Individual self edit
* Peer edit
* Key word check as a team
* Accuracy check as a team
* Final editing, including everything learned from the earlier editing sessions, the translationNotes, and the definitions of translationWords
Level Two
"""""""""
In addition to the steps listed above for level one, all parts of the resource have been checked by at least 2 respected church leaders, preferably pastors, who are mother-tongue speakers of the target language and bilingual in English. Also, these people are from different denominations and must not have been involved in translating the resource. These people can attest:
* The Translation conforms to the Statement of Faith (see http://ufw.io/faith ) and Translation Guidelines (see http://ufw.io/guidelines ).
* The Translation accurately communicates the content of the source document in the target language.
* The style of the Translation conforms to the guidelines set forth for translation of this resource in the Gateway Languages Manual.
* The translation team has edited the Translation to their satisfaction.
Level Three
"""""""""""
For level three, at least 2 more people need to have checked every part of the resource. These people must meet the following criteria: people who were not involved in the translation, were not part of the checking process of level two for that resource, and are bilingual in English. In addition, these people are leaders of different church networks or denominations who are either Bible scholars themselves or who can delegate the level 3 checking to trusted associates who are Bible scholars, able to compare the GL translations with the original biblical languages. They also need to affirm the same statements as in level two.
Additional questions that can help you to evaluate if the translation has been sufficiently checked are in [Self-Assessment Rubric](https://git.door43.org/Door43/en-ta-checking-vol1/src/master/content/self_assessment.md). Just be aware that the ULB and the UDB are not intended to be completely natural in the Gateway Language.

405
docs/gl_translation.rst Normal file
View File

@ -0,0 +1,405 @@
Gateway Language Translation
============================
question: What must be translated in the Gateway Languages?
dependencies: ["gl_strategy", "open_license"]
recommended: ["gl_ulb", "gl_udb", "translation_difficulty"]
What Needs To Be Translated
---------------------------
The following materials must be translated into the gateway languages and checked to the levels stated.
* translationAcademy vol 1 & vol 2 - Level 2
* Open Bible Stories text - Level 3
* OBS translationNotes - Level 3
* OBS translationQuestions - Level 2
* ULB Text - Level 3
* UDB Text - Level 3
* Bible translationNotes - Level 3
* Bible translationQuestions - Level 2
* translationWords - Level 2
It is important that you translate the text of the ULB and the UDB before you translate tN and tQ. However, another good method would be to translate all of the translation resources for each chunk of the Bible together. In this case, for each chunk of text, you would translate the ULB and the UDB of those verses, then tN, tW, and tQ for those same verses. Then you would move to the next chunk and translate each of the resources for that chunk, as well, in that order. (For information about which books of the Bible to translate first, see [Choosing What to Translate](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/translation_difficulty.md).)
Why Translate Two Bibles into the Gateway Languages?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Some people might ask this question, because adequate Bibles already exist in most of the Gateway languages. However, these are end-user Bibles, designed to be read and studied by people who speak those languages in their homes and churches. The Bibles that we are translating are not end-user Bibles. They are Bibles designed to be used in conjunction with each other and with the other translation helps as a set of tools that will allow speakers of other languages to use them to translate a Bible into their own languages. What they produce from these tools will be an end-user Bible.
To make an end-user Bible, it is always best to translate from more than one version, so that the translator does not fall into the habit of following the form of any one version too closely. Also, it is always possible to translate something in more than one way in a target language, and often the biblical language has more than one possible meaning. Looking at multiple versions that between them reveal these differences gives the translator a window into those things that a single version would not give. This benefit is maximized when the two (or more) source Bibles use very different styles, such as literal and dynamic. Having a literal version and a dynamic version side by side give the translator a "three-dimensional" view into the original text, allowing him to see both the form and the meaning at the same time. It is for this purpose that we are providing the ULB and the UDB.
Translating the ULB
-------------------
question: What are the guidelines for translating the ULB?
dependencies: ["gl_strategy", "gl_translate"]
recommended: ["gl_adaptulb", "gl_udb"]
Translation Theory for Translating the ULB
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The *Unlocked Literal Bible* (ULB) is designed to be used in conjunction with the translationNotes and the *Unlocked Dynamic Bible* (UDB) as a tool for Bible translation. Unlike the UDB and unlike an end-user Bible, the ULB is designed to reflect the forms of the source languages, so that the Other Language (OL) translator can see what they are. By using the ULB, the OL translator can "look through" it to see how the original Bible expressed the biblical ideas. As you translate the ULB, therefore, you must try to retain the grammatical and syntactic structures of the original as far as the target language (Gateway Language) will allow. If the original structure does not make sense in the target language, then you will need to change it into a structure that does make sense. It does no good to make a translation that the OL translator using this tool will not be able to understand. But as far as the target language will allow, retain the structures of the original in your translation of the ULB.
What method should be used to translate the ULB?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
When translating the ULB, keep the English source open in front of you. This means that if you are translating using MAST methodology, do not use the step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the ULB is a tool that must retain the original, biblical language structures in order to be useful to the translator. The best way to guard these structures is to translate with the English source ULB open in front of you so that you can be sure to keep these structures as they are in the English ULB, as far as the target language will allow.
Does Translation of the ULB Require a Back Translation?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We expect that the people translating the ULB into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the ULB will usually not be necessary. The exception to this will be if the translation of the ULB is done by a secular translation company. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
What are the structures of the ULB that should be retained?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The translation of the ULB needs to retain the original grammatical forms (as far as is possible), the idioms, and the figures of speech of the original so that the OL translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a Gateway Language (GL) translation of the ULB, then the OL translator will never see them and the translationNotes about them will not make sense. Keep in mind that the ULB and the UDB are only going to be translated into the GLs, because they are translation tools for the use of the OL translator. We want these tools to be as useful as possible. For the ULB, this means that it should retain structures that we would not always retain in an end-user Bible. The GL translator must understand that this translation will lack naturalness and sometimes also lack clarity because it is aiming at reproducing these original language structures and figures of speech that may not translate well into the GL. Wherever the ULB translation lacks clarity, however, there should also be a translationNote to explain the meaning of the structure for the OL translator. The translationNotes and the UDB will provide the meaning wherever that meaning is in doubt in the ULB. In this way, the tools will work together to provide the OL translator with a full set of information about both the form and the meaning of the original Bible.
Examples
^^^^^^^^
Grammatical Forms
"""""""""""""""""
The ULB of Luke 2:47 reproduces a grammatical form from the Greek source language that is also natural in English, but that might not be natural in other languages. When talking about the boy Jesus at the temple, it says, "All who heard him were amazed at his understanding and his answers." The nouns "understanding" and "answers" refer to events, not things, and so must be translated as verbs in many languages.
The UDB of the same verse gives an example of how these nouns can be translated as verbs. It says, "All the people who heard what he said were amazed at how much he *understood* and how well he *answered* the questions that the teachers asked."
When translating the ULB, however, these nouns should be translated as nouns if that will make sense in the target language.
Idioms
""""""
The ULB of Matthew 2:20 reproduces an idiom from the Greek source language. It refers to Herod and his soldiers who were trying to kill the child Jesus as, "those who sought the child's life." In some languages this is clear, and in others it is not.
The UDB of the same verse tries to make the meaning clear by translating this idiom as, "the people who were trying to kill the child."
When translating the ULB, however, this idiom should be translated as it is, so that the Other Language translator can consider it and use it if it makes sense. The UDB and the translationNotes will provide the meaning.
Figures of Speech
"""""""""""""""""
The ULB of John 1:17 reproduces a figure of speech from the Greek source language. It says, "grace and truth came through Jesus Christ." (This figure of speech is called "personification;" see [Personification](https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_personification.md).) This figure of speech talks as if grace and truth were like people who can come and go, and it talks as if Jesus Christ were like a doorway that they can come through. In some languages this makes sense, but in other languages it does not. The plain meaning is that Jesus Christ acted toward us with grace and taught us true things about God.
The UDB of the same verse tries to make this plain meaning clear by translating it as, "Jesus Christ was kind to us far beyond what we deserved and taught us true things about God."
When translating the ULB, however, this figure of speech should be translated as it is, so that the Other Language translator can consider it and use it if it makes sense. If it does not, the UDB provides an alternative way to translate it.
Translating the UDB
-------------------
question: What are the guidelines for translating the UDB?
dependencies: ["gl_strategy", "gl_translate", "gl_ulb"]
recommended: ["gl_notes", "check_udb"]
Translation Theory for Translating the UDB
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The *Unlocked Dynamic Bible* (UDB) is designed to be used in conjunction with the *Unlocked Literal Bible* (ULB) and the translationNotes as a tool for Bible translation. Unlike the ULB and unlike an end-user Bible, the UDB does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the UDB is to show the plain meaning of all of those things wherever they occur in the ULB. Because the UDB lacks these things, it is not a beautiful end-user Bible. An end-user Bible will use the figures of speech and idioms that speak naturally and beautifully in the target language, but the UDB does not use them. As the Other Language translator uses both the UDB and the ULB together as his translation source, he will be able to see the figures of speech, idioms, and other forms of the original Bible in the ULB and also see what their meaning is in the UDB. Then he can use the figures of speech or other forms from the ULB that are clear and natural in his language. When the forms in the ULB are not clear or natural in his language, then he can choose other forms in his language that have the same meaning as the UDB translation or the Notes. When translating the UDB, please do not use idioms, figures of speech, or difficult grammatical forms in the Gateway Language translation. The purpose of the UDB is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible.
The UDB avoids using long or complex sentences. In many languages, long or complex sentences are unnatural and unclear. When translating the UDB, keep the sentences short and simple.
The UDB often fills in the participants when these are lacking in the original Bible and the ULB. In the original biblical languages, these participants could be left out and still understood by the reader. But in many languages these must be included for the translation to be clear and natural. When translating the UDB, therefore, be sure to include all of the participants that are there in the UDB.
What method should be used to translate the UDB?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
When translating the UDB, keep the English source open in front of you. This means that if you are translating using MAST methodology, do not use the step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the UDB is a tool that carefully avoids certain structures that can be difficult to translate in some languages, as explained above. If the translator is using blind drafting, he might accidentally replace the simple structures of the UDB with structures that are natural in the target Gateway Language but unwanted in the UDB, such as idioms and figures of speech from the target GL. In order to guard against replacing these structures, it is best to translate the UDB with the English source text open to look at.
Does Translation of the UDB Require a Back Translation?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We expect that the people translating the UDB into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the UDB will usually not be necessary. The exception to this will be if the translation of the UDB is done by a secular translation company. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
Examples
^^^^^^^^
The following are examples of ways that the text of the Bible can be unclear for some languages and what the UDB does to overcome those problems. When you translate the UDB, make sure that your translation of the UDB also avoids these problems.
Passive Voice
"""""""""""""
Passive voice is a grammatical construction that is common in Greek and English but it is not used in many other languages, so it can be very confusing. For that reason, it is not used in the UDB. In passive voice, the receiver of the action changes places with the actor. In English, the actor normally comes first in the sentence. But in passive voice, the receiver of the action comes first. Often, the actor is left unstated. In that case, the UDB will fill in the actor. See "Missing Participants" below.
For example, the ULB of Romans 2:24 says, "... the name of God is dishonored among the Gentiles because of you."
The action is "dishonor," the actors are "the Gentiles" (non-Jews), and the receiver of the action is "the name of God." The reason for the action is "because of you."
The UDB rearranges the verse to put the actor and the receiver of the action in a more normal order. It says, "The non-Jews speak evil about God because of the evil actions of you Jews." This is more clear for many languages. When you translate the UDB, make sure that you do not use any passive voice constructions.
Abstract Nouns
""""""""""""""
The ULB of Romans 2:10 says, "But praise, honor, and peace will come to everyone who practices good..."
In this verse, the words "praise," "honor," "peace," and "good" are abstract nouns. That is, they are words that refer to things that we cannot see or touch. They are ideas. The ideas that these nouns express are closer to actions or descriptions than they are to things. In many languages, therefore, these ideas must be expressed by verbs or description words, not by nouns.
For this reason, the UDB expresses these nouns as actions or descriptions. It says, "But God will praise, honor, and give a peaceful spirit to every person who habitually does good deeds."
When translating the UDB, avoid using abstract nouns. For more information on abstract nouns, see [Abstract Nouns](https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_abstractnouns.md).
Long, Complex Sentences
"""""""""""""""""""""""
The ULB translates the first three verses of Romans as one complex sentence. It says, "<sup>1</sup> Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God, <sup>2</sup> which he promised beforehand by his prophets in the holy scriptures, <sup>3</sup> concerning his Son, who was born from the descendants of David according to the flesh."
The UDB breaks that into five sentences that are more simple in form. It says, "<sup>1</sup> I, Paul, who serve Christ Jesus, am writing this letter to all of you believers in the city of Rome. God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him. <sup>2</sup> Long before Jesus came to earth, God promised that he would reveal this good news by means of what his prophets wrote in the sacred scriptures. <sup>3</sup> This good news is about his Son. As to his Son's physical nature, he was born a descendant of King David."
When translating the UDB, keep the sentences short and simple.
Missing Participants
""""""""""""""""""""
In the ULB, Romans 1:1 says, "Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God..."
In this verse, there is a participant that is left unstated, but still understood. This participant is God. It is God who called Paul to be an apostle and who set him apart for the Gospel. In some languages, this participant must be stated.
Therefore the UDB of Romans 1:1 says, "God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him."
When translating the UDB, be sure to include all of the participants that are there in the UDB.
Events out of Order
"""""""""""""""""""
The ULB of Luke 2:6-7 says, "<sup>6</sup> Now it came about that while they were there, the time came for her to deliver her baby. <sup>7</sup> She gave birth to a son, her firstborn child, and she wrapped him snugly in strips of cloth. Then she put him in an animal feeding trough, because there was no room for them in a guest room."
In some languages, events need to be told in the order in which they happened, or else the story will be confusing and hard to understand. People might understand from these verses that Mary delivered her baby outside in the street, and then looked for somewhere to stay and, after a long search, ended up putting him in an animal feeding trough.
The UDB tells these events in the order in which they happened, so that it is clear that Mary was already in the shelter for animals when she gave birth. It says, "<sup>6-7</sup> When they arrived in Bethlehem, there was no place for them to stay in a place where visitors usually stayed. So they had to stay in a place where animals slept overnight. While they were there the time came for Mary to give birth and she gave birth to her first child, a son. She wrapped him in wide strips of cloth and placed him in the feeding place for the animals."
Figures of Speech
"""""""""""""""""
The ULB of Romans 2:21 says, "You who preach not to steal, do you steal?"
This is a figure of speech called a rhetorical question. It is not a real question that is used to seek an answer. It is used to make a point. In this case, Paul is using it to scold his audience and to condemn their hypocrisy. Many languages do not use rhetorical questions, or they do not use them in this way.
To show how to translate this meaning without a rhetorical question, the UDB says, "You who preach that people should not steal things, it is disgusting that you yourself steal things!"
When you translate the UDB, be sure to not use rhetorical questions or other figures of speech. (For more examples of figures of speech, see [Figures of Speech](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_intro.md) and the modules linked there.)
Idioms
""""""
The ULB of Deuteronomy 32:10 says, "he guarded him as the apple of his eye."
The word "apple" here does not refer to a kind of fruit, but instead refers to the pupil, the dark center of a person's eye. The phrase "the apple of his eye" is an idiom that refers to anything that is extremely precious to a person, or the one thing that is the most precious to a person. In many languages this idiom makes no sense, but they have other idioms that have this meaning. The Other Language translator should use one of these idioms from the target language in the OL translation, but there should be no idiom in the translation of the UDB.
To show the meaning of this verse, the UDB expresses this in plain language, without an idiom. It says, "He protected them and took care of them, as every person takes good care of his own eyes."
The Notes add another way to translate this that makes the meaning clear. It says, "He protected the people of Israel as something most valuable and precious." When you translate the UDB, be sure that you do not use any idioms. Only use plain language that makes the meaning clear. (For more information on idioms, see [Idiom](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_idiom.md).)
(For more examples of how the UDB avoids difficult grammatical constructions, idioms, and figures of speech, see the section of examples in [Translating the ULB](https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_ulb.md).)
Adapt the ULB
-------------
question: What are the guidelines for adapting an existing translation as the ULB?
dependencies: ["gl_ulb", "gl_udb", "gl_translate"]
recommended: ["gl_notes", "open_license"]
Prerequisites for Adapting an Existing Translation for the ULB
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**What is needed to adapt an existing translation and use it as the ULB for a Gateway Language (GL)?**
In order to adapt an existing translation and use it as the ULB for a Gateway Language (GL), it is necessary that the existing translation be a literal translation. That is, it should follow the same order of clauses as the original biblical languages and reproduce the original biblical idioms and figures of speech. Most Bibles that were translated into Gateway Languages in the first half of the twentieth century or earlier are literal translations.
It is also necessary that the Bible that you adapt as the ULB not be encumbered by copyright. That means that it must be in the public domain or have a license that permits us to reproduce and translate it. (For more information on copyrights and licensing, see [Open License](https://git.door43.org/Door43/en-ta-intro/src/master/content/open_license.md).)
If the Bible is very old, you will need to update the language and the style so that it uses words that people use now and "talks" in the way that people talk now. Even though the ULB has a literal style, it must use words that people know so that they can understand it.
Methodology for Adapting an Existing Translation for the ULB
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**What are the steps for adapting an existing translation for the ULB?**
Because adapting an existing translation is a process of editing rather than of translating, the first four steps of the MAST process cannot be used for this. Especially do not use the step of blind drafting. Instead, you should follow these steps:
#. Read the chapter in the English ULB and the Notes for that chapter. If you are beginning to translate a book, also read the overview of the book.
#. Read the chapter in the Bible that you are adapting as the ULB.
#. Go through the chapter and change old words to words that people use now.
#. Using the list of translationWords for that chapter, check to make sure that a good translation for each of those words is used in the Gateway Language ULB.
#. If some sentences are put together in a strange way, check to see if they are also that way in the English ULB.
#. If the sentences are also put together in that same strange way in the English ULB, it is because the original Bible has that structure. Leave them as they are. There will be a Note that will explain that structure.
#. If the sentences are not put together in that same strange way in the English ULB, then change the sentence so that it is clearer for modern readers.
#. If you see that any verse or phrase in the Bible that you are adapting is very different than the English ULB, then change it so that it is more like the English ULB.
#. If you see that any verse is missing in the Bible that you are adapting but it is there in the English ULB, then translate that verse from the English ULB.
After you do these things so that the text is ready to use as the Gateway Language ULB, you will need to translate the translationNotes. As you translate the translationNotes, you may see that there are parts of your adapted ULB that should be different so that the translationNote can make sense. Also, you may see that some translationNotes need to be changed so that they can refer to the right parts of the adapted ULB. In this way, you will need to make changes to both the Gateway Language ULB and the Notes as you adapt them to each other so that they make sense and are truly helpful for the OL translator. (For more information about this process, see [Translate the translationNotes](https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_notes.md).)
Does Adapting a Translation of the ULB Require a Back Translation?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
**How does the church ensure the translation conforms to these guidelines?**
We expect that the translation that has been adapted as the ULB already went through a series of checks to ensure that it accurately reflects the original meaning of the biblical text. This would have been done by the entity that originally translated and published the Bible translation. We also expect that the people adapting this translation for use as the ULB in the Gateway Language will be well-educated and have good theological training. They will also be connected into church networks that will have adequate resources for checking the adapted translation. For this reason, back translations of the adapted ULB will usually not be necessary. The exception to this will be if the adaptation of the translation is done by a secular translation company, and there is no church network that speaks the Gateway Language that is available to check the adaptation. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
Translate the translationNotes
------------------------------
question: What are the guidelines for translating or adapting the translationNotes?
dependencies: ["gl_adaptulb", "gl_ulb"]
recommended: ["resources_types", "gl_words", "check_notes"]
Why
^^^
translationNotes offer alternative ways to translate a phrase from the ULB. It is important that the phrase that you use to translate this kind of translationNote be a direct substitute for the phrase that it replaces in the ULB. In other words, the phrase has to have the same grammatical construction as the phrase in the ULB. That is, it needs to fit into the sentence in the ULB just like the original phrase did. In order to make sure that the phrase in the GL Note fits the sentence in the GL ULB, you must be able to always look at both the English translationNote and the GL ULB as you translate. Translating the translationNotes while having the source visible, therefore, is the most efficient way to translate them and this will also reduce the number of errors in translation. (For more information on the types of translationNotes, see [Using the translationNotes](https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/resources_types.md).)
Guidelines
^^^^^^^^^^
Does the entire Bible need translated first?
""""""""""""""""""""""""""""""""""""""""""""
It is not necessary to have the **entire** ULB and UDB Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
When I am translating the notes, do I need the ULB and UDB available and translated?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
When you translate the translationNotes for the Bible, you must also have both the ULB and the UDB in front of you, already translated into the target Gateway Language. You must have the ULB available so that you can copy the part of the ULB text that the translationNote is talking about directly into the translationNote. You must also have the UDB text already translated and available, because the translationNotes often copy part of the UDB text in order to show another way to translate the same part of the verse. Other times, the translationNote does not quote the UDB but it does refer to it. In that case, you need to be able to see what the UDB says in order to translate the translationNote in the best way.
In addition, the translationNotes directly comment on parts of the ULB text, so you must read the part of the ULB text that the translationNote comments on in order to properly translate the translationNote. After you read and understand the ULB text, then you can translate the translationNote so that it makes sense together with the ULB text that it refers to.
May I use blind drafting?
"""""""""""""""""""""""""
Do not use the method of blind drafting to translate the translationNotes. Always translate the translationNotes with the Gateway Language ULB and UDB in front of you, and the English translationNotes also visible. This is because you must copy the ULB phrase into the translationNote exactly as it is in the ULB, and you must also copy the UDB phrase if the translationNote also quotes the UDB.
How does the church ensure the translation conforms to these guidelines?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
We expect that the people translating the translationNotes into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the translationNotes will usually not be necessary. The exception to this will be if the translation of the translationNotes is done by a secular translation company. In this case, we will need to also request a back translation into English, done according to the guidelines set forth in [Back Translation](https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md) and following modules.
Adapting the translationNotes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
May I change a note so that it makes sense in my language?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Often, the ULB in the target Gateway Language will say things in a different way than the ULB said them in English. In order for the translationNote to be useful in the target Gateway Language, you will need to adapt the translationNote so that it talks about the text of the ULB as it is in the Gateway Language translation. This means that you will need to copy the phrase of the Gateway ULB that is the translation of the same phrase from the English ULB into the translationNote, and then sometimes change the translationNote so that it makes sense and is helpful for the Other Language translator who will use these translationNotes as translation tools.
May I delete a note that does not apply to my language?
"""""""""""""""""""""""""""""""""""""""""""""""""""""""
Because languages can be very different from each other, sometimes there will be translationNotes that are important and necessary for some languages, but that are not needed for other languages. If there is a translationNote that does not make sense when applied to the ULB text in the target Gateway Language, then you as the translator will need to modify the translationNote so that it does make sense in relation to the ULB in your target Gateway Language. If the translationNote does not apply at all to the target GL text of the ULB, then you may delete that note from your translation of the translationNotes. But be sure to think about it very carefully before you delete a translationNote, to be sure that it is not necessary for the GL translation.
May I add a note that would help with translation in my language?
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
For the same reason, sometimes you will realize that the Other Language translator will need a translationNote in order to understand a phrase in the target Gateway Language ULB, but there might not be a translationNote already written for that phrase, because it was not necessary for the English ULB. In that case, you will need to write a new translationNote and include it in your translation. Usually these translationNotes will be to explain a phrase or way of saying something that is normal in the Gateway Language but that is not normal in the Other Languages that you know of. When writing your translationNote, follow the same style and format of the existing translationNotes.
Remember that speakers of many different languages will be using these Gateway Language translationNotes to help them translate the Bible. There will be many things that you will understand about the Bible in the Gateway Language that the OL translator may not understand. For that reason, if you think that there is something difficult to understand in the GL ULB, write a translationNote that can help the OL translator to understand it. There will probably be many Other Language translators who will benefit from reading the translationNote and who will make a better translation because of it.
Because the translationNotes need to be adapted in these ways and not simply translated, it is best if the people adapting the translationNotes be people who are well educated in biblical studies so that they can understand the various problems that the translationNotes explain.
Translating translationWords
----------------------------
question: What are the guidelines for translating translationWords?
dependencies: ["gl_notes", "gl_ulb", "gl_adaptulb"]
recommended: ["gl_questions"]
Why
^^^
It is important that the Other Language translators understand all of the words that they are translating. But some of the words in the Bible are not used in everyday life in our time or in our cultures, and so the translator may not be familiar with them. Other words are used in everyday life, but they are used in a different way in the Bible. Some of these words have very important or special meanings in the Bible. They tell us a lot about God and his relationship with us. So in order for the Other Language translator to completely understand these words, we have provided the definitions in translationWords. When you translate this list into the Gateway Language, it will help all of the Other Language translators who will use it to translate the Bible for their people with good understanding.
Guidelines
^^^^^^^^^^
Does the entire Bible need translated first?
""""""""""""""""""""""""""""""""""""""""""""
It is not necessary to have the **entire** ULB and UDB Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
What is the "Definition" section of translationWords?
"""""""""""""""""""""""""""""""""""""""""""""""""""""
tW definitions have several parts, the first part is "Definition." This gives the meaning of the word as it is used in the Bible. Please do not use definitions from a modern Gateway Language dictionary, because the way words are used in the Bible can be different from the way they are used in modern, everyday life. We want to make sure that the Other Language translator understands the way that the word is used in the Bible.
It is possible that the Gateway Language might express the meaning of the English word by different words, with each of those words having part of the meaning of the English word. In this case, you will need to list each of those words at the top, separated by commas. Several of the English tW entries already have multiple words at the top like this, such as "prophet, prophecy, prophesy, seer, prophetess" (see https://door43.org/en/obe/kt/prophet ). Then, in the "Definition" part, you will need to list those words in separate paragraphs with a definition for each one. The Other Language translator can then choose the word that he needs to understand from that list and translate it correctly in the passage that he is translating.
What is the "Translation Suggestions" section of translationWords?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
The second part of a tW entry is "Translation Suggestions" or "Translation Strategies." This section gives different ideas for how the Other Language translator can translate the word. This section gives more than one way to translate the word because it can mean slightly different things in different contexts. Be sure that you understand the differences of meaning between the different contexts in which the word is used so that you can translate them correctly.
In the Gateway Language, some of the tW are not used in all of the same contexts as the English tW are. **In that case, you will need to adjust your translation**. If one of the Translation Suggestions does not work in the Gateway Language, then do not translate that Translation Suggestion. Instead, write a Translation Suggestion that shows how that word is used in the Gateway Language. Think about the different ways that the word is used in the Bible, and try to make sure that there is a Translation Suggestion for each of the primary uses. We want the Other Language translator to see and consider the differences and the similarity in meaning between the uses of the word so that he can choose the best word in his language to express those meanings.
As you translate the ULB and UDB, you may find that you need to add a meaning to a word in the tW entry, or you may need to add another word to the entry because the Gateway Language uses more than one word for the idea of that important tW. Go ahead and do this as you find more words or meanings for the words.
Under the "Translation Suggestions" or "Translation Strategies" section is a line that says, "(See also...)." You only need to translate the words "See also," and you only need to translate this one time, not for every tW. The rest of the line will be created automatically, if the translation is done in translationStudio Desktop.
Do I translate the "Bible References" and "Examples for the Bible Stories" sections of translationWords?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
The third and fourth parts are "Bible References" and "Examples from the Bible Stories." You only need to translate these words of the titles, and you only need to translate them one time, not for every tW. You do not need to translate the rest of these parts. They will be created automatically, if the translation is done in translationStudio Desktop.
Translating translationQuestions
--------------------------------
question: What are the guidelines for translating translationQuestions?
dependencies: ["mast", "gl_words", "gl_notes", "gl_ulb"]
recommended: ["check_ulb", "check_notes"]
Why
^^^
We want all translations of the Bible to communicate clearly the message that God wants them to communicate. One tool that we are providing so that the OL translators can make sure that their translations are communicating correctly is translationQuestions (tQ). The OL translators will use tQ to conduct community checks of each chapter of the Bible that they translate.
Guidelines
^^^^^^^^^^
Does the entire Bible need to be translated first?
""""""""""""""""""""""""""""""""""""""""""""""""""
It is not necessary to have the **entire** ULB and UDB Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
MAST Method
"""""""""""
1. Read the chapter of the ULB that the Questions are about, so that you understand it.
1. Draft each Question with its answer as one chunk. Work through the Questions for that chapter of the ULB, translating each pair of questions and answers.
1. When you finish translating each question-answer pair for that chapter, go back and do the checking steps, comparing your translation with the English source questions and answers.
1. Now compare your translation of each answer with the Gateway Language ULB of that verse. It is important that your answer to each Question match very closely to the words of the ULB. At this step, you may need to adjust the words of your answers so that they are the same as the words of the ULB. This is so the OL translators and checkers of the OL translation can use your questions and answers and easily see if the their translation is communicating the right message. When the words of your answer are the same as the words of the ULB, the OL checker can see where that answer is in the translation and know what part of their translation they need to make more clear if the person answering the question gives a different answer.
Modified MAST Method
""""""""""""""""""""
This is an alternative method for translating tQ.
1. Read the chapter of the ULB that the Questions are about, so that you understand it.
1. Translate only the question part of each question-answer pair using the MAST method of blind drafting. Each Question will be one chunk. Draft all of Questions for one chapter.
1. In the self-edit stage of checking, edit each Question to correct any mistakes or to add things that you left out.
1. Now copy the answer to each question from the words of the Gateway Language ULB of that verse that match the answer to that question in the English source. In this way, the words of each answer will always match the words of the Gateway Language ULB.
You may want to try both methods and see which one works best for you.
If the ULB Has Not Been Translated
""""""""""""""""""""""""""""""""""
If the ULB has not been translated already, an alternative method would be to translate the ULB together with the other resources, chunk by chunk. In this case, for each chunk of text, you would translate the ULB and the UDB of those verses, then tN, tW, and tQ for those same verses. Then you would move to the next chunk and translate each of the resources for that chunk, as well. After you finish drafting all of the resources for one chunk, then go back and do the checking steps for all of the resources for that chunk.
Translating translationAcademy
------------------------------
question: What are the guidelines for translating translationAcademy?
dependencies: ["ta_intro", "gl_strategy", "gl_notes", "gl_ulb"]
recommended: ["check_ulb", "check_notes"]
Recommended Training and Experience
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
translationAcademy contains many lessons on specialized topics, such as language, translation issues, biblical studies, software, and audio equipment. Some of the vocabulary is also specialized. We recommend that the people who translate tA into a Gateway Language have a **college-level education or some training and experience in the particular area that they are translating**. For example, if you are translating the Translation Manual, it would be good if you have training and experience in linguistics and translation. If you are translating the Audio Manual, it would be good if you have training and experience using audio equipment. You will be able to translate more accurately and clearly if you have experience in the topic.
This means that you will want to have **several specialists** on your translation team, with each specialist translating the parts that they are most familiar with. If you find that some lessons are unclear, discuss the problem with other members of the team until you understand what the lesson is trying to teach. You cannot translate something that you do not understand. If you try to do that, the Other Language translator will not be able to understand or use it.
Recommended Reference Materials
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We recommend that you use specialized dictionaries as you translate to hep you understand the concepts that you are translating. Do not use unusual or technical words in your translation if there is a simpler way to communicate the same thing. Remember that the OL translators speaks the Gateway Language as a second language, they will not know unusual or technical words. Try to keep the lessons uncomplicated and clear, using simple language as much as you can. We have tried to write the lessons of tA using simple language, so please follow this same style.

18
docs/index.rst Normal file
View File

@ -0,0 +1,18 @@
.. Resource Container documentation master file, created by
sphinx-quickstart on Tue Sep 20 15:27:28 2016.
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.
Gateway Language Manual
=======================
This resource provides helpful information for Gateway Language teams to learn what needs to be translated to open a Gateway Language.
Contents:
.. toctree::
:maxdepth: 2
gl_translation
gl_checking

281
docs/make.bat Normal file
View File

@ -0,0 +1,281 @@
@ECHO OFF
REM Command file for Sphinx documentation
if "%SPHINXBUILD%" == "" (
set SPHINXBUILD=sphinx-build
)
set BUILDDIR=_build
set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% .
set I18NSPHINXOPTS=%SPHINXOPTS% .
if NOT "%PAPER%" == "" (
set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
set I18NSPHINXOPTS=-D latex_paper_size=%PAPER% %I18NSPHINXOPTS%
)
if "%1" == "" goto help
if "%1" == "help" (
:help
echo.Please use `make ^<target^>` where ^<target^> is one of
echo. html to make standalone HTML files
echo. dirhtml to make HTML files named index.html in directories
echo. singlehtml to make a single large HTML file
echo. pickle to make pickle files
echo. json to make JSON files
echo. htmlhelp to make HTML files and a HTML help project
echo. qthelp to make HTML files and a qthelp project
echo. devhelp to make HTML files and a Devhelp project
echo. epub to make an epub
echo. epub3 to make an epub3
echo. latex to make LaTeX files, you can set PAPER=a4 or PAPER=letter
echo. text to make text files
echo. man to make manual pages
echo. texinfo to make Texinfo files
echo. gettext to make PO message catalogs
echo. changes to make an overview over all changed/added/deprecated items
echo. xml to make Docutils-native XML files
echo. pseudoxml to make pseudoxml-XML files for display purposes
echo. linkcheck to check all external links for integrity
echo. doctest to run all doctests embedded in the documentation if enabled
echo. coverage to run coverage check of the documentation if enabled
echo. dummy to check syntax errors of document sources
goto end
)
if "%1" == "clean" (
for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
del /q /s %BUILDDIR%\*
goto end
)
REM Check if sphinx-build is available and fallback to Python version if any
%SPHINXBUILD% 1>NUL 2>NUL
if errorlevel 9009 goto sphinx_python
goto sphinx_ok
:sphinx_python
set SPHINXBUILD=python -m sphinx.__init__
%SPHINXBUILD% 2> nul
if errorlevel 9009 (
echo.
echo.The 'sphinx-build' command was not found. Make sure you have Sphinx
echo.installed, then set the SPHINXBUILD environment variable to point
echo.to the full path of the 'sphinx-build' executable. Alternatively you
echo.may add the Sphinx directory to PATH.
echo.
echo.If you don't have Sphinx installed, grab it from
echo.http://sphinx-doc.org/
exit /b 1
)
:sphinx_ok
if "%1" == "html" (
%SPHINXBUILD% -b html %ALLSPHINXOPTS% %BUILDDIR%/html
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The HTML pages are in %BUILDDIR%/html.
goto end
)
if "%1" == "dirhtml" (
%SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
goto end
)
if "%1" == "singlehtml" (
%SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
goto end
)
if "%1" == "pickle" (
%SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
if errorlevel 1 exit /b 1
echo.
echo.Build finished; now you can process the pickle files.
goto end
)
if "%1" == "json" (
%SPHINXBUILD% -b json %ALLSPHINXOPTS% %BUILDDIR%/json
if errorlevel 1 exit /b 1
echo.
echo.Build finished; now you can process the JSON files.
goto end
)
if "%1" == "htmlhelp" (
%SPHINXBUILD% -b htmlhelp %ALLSPHINXOPTS% %BUILDDIR%/htmlhelp
if errorlevel 1 exit /b 1
echo.
echo.Build finished; now you can run HTML Help Workshop with the ^
.hhp project file in %BUILDDIR%/htmlhelp.
goto end
)
if "%1" == "qthelp" (
%SPHINXBUILD% -b qthelp %ALLSPHINXOPTS% %BUILDDIR%/qthelp
if errorlevel 1 exit /b 1
echo.
echo.Build finished; now you can run "qcollectiongenerator" with the ^
.qhcp project file in %BUILDDIR%/qthelp, like this:
echo.^> qcollectiongenerator %BUILDDIR%\qthelp\ResourceContainer.qhcp
echo.To view the help file:
echo.^> assistant -collectionFile %BUILDDIR%\qthelp\ResourceContainer.ghc
goto end
)
if "%1" == "devhelp" (
%SPHINXBUILD% -b devhelp %ALLSPHINXOPTS% %BUILDDIR%/devhelp
if errorlevel 1 exit /b 1
echo.
echo.Build finished.
goto end
)
if "%1" == "epub" (
%SPHINXBUILD% -b epub %ALLSPHINXOPTS% %BUILDDIR%/epub
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The epub file is in %BUILDDIR%/epub.
goto end
)
if "%1" == "epub3" (
%SPHINXBUILD% -b epub3 %ALLSPHINXOPTS% %BUILDDIR%/epub3
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The epub3 file is in %BUILDDIR%/epub3.
goto end
)
if "%1" == "latex" (
%SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
if errorlevel 1 exit /b 1
echo.
echo.Build finished; the LaTeX files are in %BUILDDIR%/latex.
goto end
)
if "%1" == "latexpdf" (
%SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
cd %BUILDDIR%/latex
make all-pdf
cd %~dp0
echo.
echo.Build finished; the PDF files are in %BUILDDIR%/latex.
goto end
)
if "%1" == "latexpdfja" (
%SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
cd %BUILDDIR%/latex
make all-pdf-ja
cd %~dp0
echo.
echo.Build finished; the PDF files are in %BUILDDIR%/latex.
goto end
)
if "%1" == "text" (
%SPHINXBUILD% -b text %ALLSPHINXOPTS% %BUILDDIR%/text
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The text files are in %BUILDDIR%/text.
goto end
)
if "%1" == "man" (
%SPHINXBUILD% -b man %ALLSPHINXOPTS% %BUILDDIR%/man
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The manual pages are in %BUILDDIR%/man.
goto end
)
if "%1" == "texinfo" (
%SPHINXBUILD% -b texinfo %ALLSPHINXOPTS% %BUILDDIR%/texinfo
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The Texinfo files are in %BUILDDIR%/texinfo.
goto end
)
if "%1" == "gettext" (
%SPHINXBUILD% -b gettext %I18NSPHINXOPTS% %BUILDDIR%/locale
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The message catalogs are in %BUILDDIR%/locale.
goto end
)
if "%1" == "changes" (
%SPHINXBUILD% -b changes %ALLSPHINXOPTS% %BUILDDIR%/changes
if errorlevel 1 exit /b 1
echo.
echo.The overview file is in %BUILDDIR%/changes.
goto end
)
if "%1" == "linkcheck" (
%SPHINXBUILD% -b linkcheck %ALLSPHINXOPTS% %BUILDDIR%/linkcheck
if errorlevel 1 exit /b 1
echo.
echo.Link check complete; look for any errors in the above output ^
or in %BUILDDIR%/linkcheck/output.txt.
goto end
)
if "%1" == "doctest" (
%SPHINXBUILD% -b doctest %ALLSPHINXOPTS% %BUILDDIR%/doctest
if errorlevel 1 exit /b 1
echo.
echo.Testing of doctests in the sources finished, look at the ^
results in %BUILDDIR%/doctest/output.txt.
goto end
)
if "%1" == "coverage" (
%SPHINXBUILD% -b coverage %ALLSPHINXOPTS% %BUILDDIR%/coverage
if errorlevel 1 exit /b 1
echo.
echo.Testing of coverage in the sources finished, look at the ^
results in %BUILDDIR%/coverage/python.txt.
goto end
)
if "%1" == "xml" (
%SPHINXBUILD% -b xml %ALLSPHINXOPTS% %BUILDDIR%/xml
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The XML files are in %BUILDDIR%/xml.
goto end
)
if "%1" == "pseudoxml" (
%SPHINXBUILD% -b pseudoxml %ALLSPHINXOPTS% %BUILDDIR%/pseudoxml
if errorlevel 1 exit /b 1
echo.
echo.Build finished. The pseudo-XML files are in %BUILDDIR%/pseudoxml.
goto end
)
if "%1" == "dummy" (
%SPHINXBUILD% -b dummy %ALLSPHINXOPTS% %BUILDDIR%/dummy
if errorlevel 1 exit /b 1
echo.
echo.Build finished. Dummy builder generates no files.
goto end
)
:end

29
meta.yaml
View File

@ -1,29 +0,0 @@
########################################################################
# TRANSLATABLE FIELDS:
# --------------------
# manual_title
# contributors
# checking_entity
#
# * DO NOT TRANSLATE ANYTHING BEFORE A COLON.
# * ONLY TRANSLATE TEXT AFTER THE COLON.
#
########################################################################
manual: "gateway"
manual_title: "Gateway Languages Manual"
volume: "3"
contributors: "unfoldingWord; Wycliffe Associates"
checking_level: "3"
checking_entity: "Wycliffe Associates"
comments: ""
license: "CC BY-SA 4.0"
publish_date: "2016-07-01"
source_text: "en"
source_text_version: "5"
version: "5"
language:
code: "en"
name: "English"
anglicized_name: "English"
direction: "ltr"

11
testtW.md
View File

@ -1,11 +0,0 @@
"Aron"
"Gipili sa Dios si Aron nga mahimong unang kinatas-ang pari sa katawhan sa Israel. \n
* Si Aron mao ang magulang ni Moises. \n
* Gitabangan ni Aron si Moses nga makigsulti kang Paraon nga pagawason niya ang mga Israelita gikan sa pagka-ulipon sa mga taga-Ehipto. \n
* Samtang nagbyahi ang mga Israelita sa disyerto, nakasala si Aron pinaagi sa paghimo ug diosdiosan aron simbahon sa mga tawo. \n
* Gipili sa Dios si Aron ug iyang mga kaliwat nga mahimong mga pari sa mga katawhan sa Israel."
### Translation Suggestions
* test line

71
toc.yaml
View File

@ -1,71 +0,0 @@
###############################################################################
# Table of Contents
#
# Follow this format
# ==================
#
# - title: Text to display for the menu item
# slug: page_slug
# subitems:
# - title: Test to display for the next item
# - slug: page_2_slug
#
# - title: This is a header, not a link to a page
# subitems:
# - title: Text to display for another menu item
# slug: page_3_slug
#
# NOTES:
# * NO TAB CHARACTERS ALLOWED. Be sure your editor does not insert tabs
# because bad things will happen.
# * There must be a space after the initial dash and after the colon.
# * The slug is also the name of the file that goes with the menu item, but
# without the ".md" extension.
# * Quotation marks are not required around the values, but they are
# recommended, especially if the value contains characters other than
# ASCII letters a-z and A-Z. They can also improve readability.
# * If there are no subitems you do not need to include the "subitems:" tag.
# * Sub levels are indented 2 spaces more than the parent level.
# * To include headers in the menu that are not links to a module, add an
# item with a title but no slug.
#
# TRANSLATABLE FIELDS:
# --------------------
# title
#
# * DO NOT TRANSLATE THE SLUG FIELD.
# * DO NOT TRANSLATE ANYTHING BEFORE A COLON.
# * ONLY TRANSLATE TEXT AFTER THE COLON.
#
###############################################################################
- title: "Gateway Language Translation"
subitems:
- title: "Translating in the Gateways"
slug: gl_translate
- title: "Translating the ULB"
slug: gl_ulb
- title: "Translating the UDB"
slug: gl_udb
- title: "Adapt the ULB"
slug: gl_adaptulb
- title: "Translating translationNotes"
slug: gl_notes
- title: "Translating translationWords"
slug: gl_words
- title: "Translating translationQuestions"
slug: gl_questions
- title: "Translating translationAcademy"
slug: gl_academy
- title: "Checking Gateway Language Translation Materials"
subitems:
- title: "Checking the ULB"
slug: check_ulb
- title: "Checking the UDB"
slug: check_udb
- title: "Checking translationNotes"
slug: check_notes
- title: "Finishing Checking"
slug: gl_done_checking