Update merge conflicts

.gitignore

@@ -1,2 +1 @@
-.idea
-.DS_Store
+.idea

LICENSE.md

@@ -1,5 +1,4 @@
 # License
-
 ## Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
 
 This is a human-readable summary of (and not a substitute for) the [license](http://creativecommons.org/licenses/by-sa/4.0/).
@@ -15,7 +14,7 @@ The licensor cannot revoke these freedoms as long as you follow the license term
 
 ### Under the following conditions:
 
-  * **Attribution** — You must attribute the work as follows: "Original work available at https://unfoldingword.bible/academy/." Attribution statements in derivative works should not in any way suggest that we endorse you or your use of this work.
+  * **Attribution** — You must attribute the work as follows: "Original work available at https://door43.org/." Attribution statements in derivative works should not in any way suggest that we endorse you or your use of this work.
   * **ShareAlike** — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
 
 **No additional restrictions** — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

README.md

@@ -1,53 +1,89 @@
-# unfoldingWord translationAcademy
+# English translationAcademy
 
-## Description
+## Overview
 
-unfoldingWord translationAcademy is a modular handbook that provides a condensed explanation of Bible translation and checking principles that the global Church has implicitly affirmed define trustworthy translations. It enables translators to learn how to create trustworthy translations of the Bible in their own language.
+translationAcademy is intended to enable anyone, anywhere to equip themselves so that they will be able to make high-quality translations of biblical content into their own language. translationAcademy is designed to be highly flexible. It can be used in a systematic, in-advance approach or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
 
-## Downloading
+translationAcademy was developed by the [Door43 World Missions Community](https://door43.org) in conjunction with [Wycliffe Associates](http://www.wycliffeassociates.org/). The entire project is made
+available under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0), see the [LICENSE](https://git.door43.org/Door43/en_ta/src/master/LICENSE.md) file for more information.
 
-If you want to download English translationAcademy to use, go here: [https://unfoldingword.bible/academy/](https://unfoldingword.bible/academy/). tA is also included in [tS](http://ufw.io/ts) and [tC](http://ufw.io/tc).
+Please use the [issue queue](https://git.door43.org/Door43/en_ta/issues) to provide feedback or suggestions for improvement.
 
-## Improving tA
+## Resources
 
-Please use the [issue queue](https://git.door43.org/unfoldingWord/en_ta/issues) to provide feedback or suggestions for improvement.
+If you want to download English translationAcademy to use, go here: https://unfoldingword.org/academy/. tA is also included in [tS](http://ufw.io/ts) and [tC](http://ufw.io/tc).
 
-If you want to make your suggested changes then you may use the online editor to do so. See the [protected branch workflow](https://forum.ccbt.bible/t/protected-branch-workflow/76) document for step by step instructions.
+## Contributing or Translating
 
-## Structure
+### Contributions are always welcomed. 
+The translationAcademy is a collaborative work between several organzations. We seek those that would like to contribute to the work. Presently there is an Oversight Team that is responsible for the maintenance of the content. The members of this team represent various organizations and are experienced Biblical Scholars, Linguists and Bible Translators.
+All contributions will be reviewed by the Oversight Team.
 
-The tA are written in a simple Markdown format and organized according to the [Resource Container Manual](https://resource-container.readthedocs.io/en/latest/container_types.html#manual-man) type.  See that link for more information but here is a quick summary.
+#### Submit an Issue
+Submitting an issue is the preferred way to let the Oversight Team know of errors in the content. When you find an error, please note where the error is, if possible copy the error, open an [Issue](https://git.door43.org/Door43/en_ta/issues), paste in the error, then offer a correction, and then submit the Issue.
 
-Each manual has it's own directory in this repository (for example, the Checking Manual is in the [checking](https://git.door43.org/unfoldingWord/en_ta/src/branch/master/checking) directory). Each module has its own directory inside of these manual directories. Inside each of these are three files:
+#### Pull Request
+To contribute to the content of the translationAcademy please fork a copy of the repository, make your changes and then submit a Pull Request to the repository.
+The Oversight Team will then review the PR and then decide on the merging of the content into the master repository.
 
-* `01.md` - This is the main body of the module
-* `sub-title.md` - This file contians the question that the module is intended to answer.
-* `title.md` - This contains the title of the module
+### Explanation of the content file layout
 
-There are also YAML formatted files in each manual's directory.  The `toc.yaml` file is for encoding the Table of Contents and the `config.yaml` file is for encoding dependencies between the modules.
+Each manual has it's own directory in this repository (for example, the Checking Manual is in the checking directory). The content of the files are in a hybrid YAML/markdown format, beginning with a YAML header followed by the body of the article in markdown.
 
-## GL Translators
+YAML is a markup language that is compact and easy to read. The YAML header bounded on the top and bottom by `---`. Each line within the header is a key-value pair, with the key and the value separated by a colon. Because the key is used by the publishing process, __it should never be translated or changed.__ Some of the values can be translated, and those are enumerated below in the instructions for translating.
 
-### tA Translation Philosophy
+Following the YAML header is the body of the article, which uses a format called "markdown." If you aren't familiar with markdown, you may find this [markdown tutorial](http://www.markdowntutorial.com/) helpful. Also, this README file, the one you are reading now, is written in markdown.
 
-To learn the philosophy of how to translate the tA please see the [Translate translationAcademy](http://gl-manual.readthedocs.io/en/latest/gl_translation.html#translating-translationacademy) article in the [Gateway Language Manual](http://gl-manual.readthedocs.io/).
+### Before you get started translating
 
-If you are translating online, please fork the [Door43-Catalog/en_ta](https://git.door43.org/Door43-Catalog/en_ta) repository, following this workflow: [Translate Content Online](https://forum.ccbt.bible/t/translate-content-online/75).
+* DO NOT RENAME ANY FILES. The name of the file is the same as the slug and is used to link the file to other files.
 
-### Technical Information for Translating tA
+* If you do any translation work, be sure to put your name in the `manifest.yaml` file.
+    * Left click on the file found in the root of the repository.
+    * Click on the pencil icon to edit the file.
+    * You will add the name(s) under the 'contributor' list heading (see line 5 and under)
+    * Click on the end of line 7 (after 'Wycliffe Associates') and then press the enter key to start a new line.
+    * Type in a dash then space then the name of a contributor between single quote marks.
+    * Type in additional names as necessary.
+    * Click on the green "Commit Changes" button at the bottom of the page to save the changes.
 
-* *Do not* rename any files or directories.  Only translate what is inside the files.
-* The `config.yaml` and `toc.yaml` files do not need to be changed unless you add a new module. When you are finished translating, you may want to update the `title` fields in the `toc.yaml` file, but you shouldn't make any other changes in those files.
-* Images that are included in tA should be no more than 600px wide. Leave the image links alone to use the original images.
-* Hyperlinks (links to other articles or to other pages on the internet) follow this pattern: `[text to display](http://www.example.com)`. You can translate the "text to display" inside the square brackets but not the web address that follows inside the parentheses.
+* The `LICENSE.md` file does not need to be translated or modified.
+* The `README.md` does not need to be translated or modified.
 
-You are free to add additional modules. In order for the new modules to be included when tA is published, all of the following conditions need to be satisfied:
+### Images
 
-* You must create a directory in one of the manual directories (like the translate directory) that has the short name of the module you want to write.  For example, to create a new module on "testing" in the Translation Manual, you will want to put the file in "translate/testing/01.md".
-* The file must be included in the table of contents, `toc.yaml` for the appropriate manual.
-* The value of the slug in the `toc.yaml` file and the directory (without the extension) must be the same as the directory name (`testing` in this example).
-* The slug must be unique, and not used in any of the other tA repositories. This is a requirement so that it is possible to create unambiguous links to articles in other tA manuals.
+Images that are included in tA should be no more than 600px wide.
 
-## License
+### Instructions for translating translationAcademy
 
-See the [LICENSE](https://git.door43.org/unfoldingWord/en_ta/src/branch/master/LICENSE.md) file for licensing information.
+__The instructions for translating `meta.yaml` (metadata) and `toc.yaml` (table of contents) are included in the header of those files.__
+
+The first step is to __fork this repository.__ When you do this, change the name of the repository to start with your language code rather than
+`en`.
+
+When translating the files for each manual:
+
+* In the YAML header, you are free to translate the values following the `title`, `question` and `credits` keys. __DO NOT TRANSLATE THE KEYS__.
+None of the other values should be translated. They contain slugs that are used to identify this article and to link it to other articles.
+
+* Translating hyperlinks: Hyperlinks (links to other articles or to other pages on the internet) follow this pattern,
+
+```
+[text to display](http://www.example.com)
+```
+
+You can translate the "text to display" inside the square brackets but not the web address that follows inside the parentheses.
+
+You are free to add additional pages. In order for the new page to be included when tA is published, all of the following conditions need to be satisfied:
+
+1. You must create a directory in one of the manual directories (like the translate directory) that has the short name of the module you want to write. For example, to create a new module on "testing" in the Translation Manual, you will want to put the file in "translate/testing/01.md".
+
+1. The file must be included in the table of contents, `toc.yaml` for the appropriate manual.
+
+1. The value of the slug in the YAML header and the file name (without the extension) must be the same as the directory name.
+
+1. The slug must be unique, and not used in any of the other tA repositories. This is a requirement so that it is possible to create unambiguous links to articles in other tA manuals.
+
+## Historical
+
+If you would like to see the deprecated tranlsationAcademy pages in DokuWiki, go to https://dw.door43.org/en/ta. You can still see the workbench pages at https://dw.door43.org/en/ta/workbench.

archive/checking/accurate/01.md

@@ -0,0 +1,6 @@
+
+### An Accurate Translation
+
+It is very important to make sure that the new translation is accurate. Those who have been chosen to check the translation for accuracy have the responsibility to make sure that it communicates the same meaning as the original writer intended and expected to communicate.
+
+For instructions on how to do this, go to [Accuracy Check](../accuracy-check/01.md), and follow the steps in the section under the heading "All Levels."

archive/checking/accurate/sub-title.md

@@ -0,0 +1 @@
+Is the translation accurate?

archive/checking/accurate/title.md

@@ -0,0 +1 @@
+Accurate Translation

archive/checking/alphabet/01.md

@@ -0,0 +1,10 @@
+
+### The Alphabet for the Translation
+
+As you read the translation, ask yourself these questions about the way words are spelled. These questions will help to determine if an appropriate alphabet has been chosen to represent the sounds of the language and if words have been written in a consistent way so that the translation will be easy to read.
+
+1. Is the alphabet suitable to represent the sounds of the language of the new translation? (Are there any sounds that make a difference in meaning but have to use the same symbol as another sound? Does this make the words hard to read? Can additional marks be used to adjust these letters and show the differences?)
+1. Is the spelling used in the book consistent? (Are there rules that the writer should follow to show how words change in different situations? Can they be described so others will know how to read and write the language easily?)
+1. Has the translator used expressions, phrases, connectors, and spellings that will be recognized by most of the language community?
+
+If there is something about the alphabet or spelling that is not right, make a note of that so that you can discuss it with the translation team.

archive/checking/alphabet/sub-title.md

@@ -0,0 +1 @@
+Does the translation use an appropriate alphabet?

archive/checking/alphabet/title.md

@@ -0,0 +1 @@
+Appropriate Alphabet

archive/checking/church-leader-check/01.md

@@ -0,0 +1,16 @@
+
+### How to do a Church Leader Check
+
+After the translation has been checked by community members for clarity, it will be checked by a group of church leaders for accuracy. This group must consist of at least three church leaders who are native speakers of the target language, and who understand well one of the languages in which the source text is available. They should not be related to, or otherwise closely connected with, the translation team. Usually these reviewers will be pastors. These church leaders should represent the different church networks in the language community. We recommend that the group includes church leaders from three different church networks, if the community has that many.
+
+These reviewers should follow these steps:
+
+1. Read the [Translation Guidelines](../../intro/translation-guidelines/01.md) to make sure that the translation is in agreement with both of those as they review the translation.
+1. Answer the questions about the translator or translation team that are located at [Translator Qualifications](../../translate/qualifications/01.md).
+1. Verify that the translation has been done in a style that is acceptable to the intended audience by asking the questions at [Acceptable Style](../acceptable/01.md).
+1. Verify that the translation accurately communicates the meaning of the source text by following the guidelines at [Accuracy Check](../accuracy-check/01.md).
+1. Verify that the translation is complete by following the guidelines at [Complete Translation](../complete/01.md).
+1. After you have reviewed several chapters or one book of the Bible, meet with the translation team and ask about each problem. Discuss with the translation team how they might adjust the translation in order to fix the problems. Make plans to meet again with the translation team at a later time, after they have had time to adjust the translation and test it with the community.
+1. Meet again with the translation team to verify that they have fixed the problems.
+1. Affirm that the translation is good. See [Level 2 Affirmation](../good/01.md) to do that on the Level Two Affirmation page.
+

archive/checking/church-leader-check/sub-title.md

@@ -0,0 +1 @@
+How can the church leaders help improve the translation?

archive/checking/church-leader-check/title.md

@@ -0,0 +1 @@
+Church Leader Check

archive/checking/language-community-check/01.md

@@ -0,0 +1,12 @@
+
+### Level two Checking
+
+The level two check focuses on pastors and the Christian community within the target language. Once the translation team has reached level one with its translation, the translation is ready to be shared outside the team for further review. Ideally, a leader on the translation team will work with local pastors and Christians to check the scripture's clarity and naturalness. 
+
+The translator or leader will read (if it is a written translation) a portion of the translation to the gathered listeners. Before reading, he should tell the people listening  to stop him if they hear something that does not sound natural. Alternatively, if the people are literate, each one in the group can be asked to read a passage of the newly translated material. It is best, even if everyone in the group is literate, to have the portions read out loud to the whole group. Portions should not be too long (this is subjective to the abilities of the group, and type of passage). It's also very important for  listeners to understand that they are now a part of the team helping to improve and affirm the quality of the scripture. They, themselves are not being tested. Rather the questions are designed to help them provide feedback on the meaningfulness of the new translation. 
+
+These tools have been created to assist teams in checking and are recommending for use during this level--translation questions, translation notes, and the reviewer's guide.  They are available on bibleineverylanguage.org. Additionally, the translation questions and translation notes are embedded in tStudio. During the MAST workshop, the translation team was asked to develop a rubric for testing and affirming the quality of their work. More information on this strategy is available at v-raft.org. This rubric will help the team determine which tools and methods to apply to the level two check within their community. 
+
+Key elements of this level of checking are:  pastors AND Christians in the community have read (or listened to) the translated scriptures and contributed to their improvement, the above listed tools have been employed for ensuring accuracy and completeness, the translation team has been  responsible to respond to feedback and implement changes in the translation where needed. When this has been done, the translation is considered to be at level two. 
+
+

archive/checking/language-community-check/sub-title.md

@@ -0,0 +1 @@
+How pastors and other believers can be involved in checking the translation.

archive/checking/language-community-check/title.md

@@ -0,0 +1 @@
+Level Two--Pastoral and Christian Community Check

archive/checking/level1-affirm/01.md

@@ -0,0 +1,24 @@
+
+### Proper Documentation for Level 1 Affirmation
+
+We, the members of the translation team, affirm that we have completed the steps below for level 1 checking:
+
+* Initial study of the text, using:
+  * The translationNotes
+  * The definitions of translationWords
+* Individual blind drafting
+* Individual self check
+* Peer check
+* Key word check as a team
+* Verse-by-verse accuracy check as a team
+* Final editing, including everything learned from the earlier editing sessions, the translationNotes, and the definitions of translationWords
+
+Names of translation team members:
+
+* Name or pseudonym:
+* Name or pseudonym:
+* Name or pseudonym:
+* Name or pseudonym:
+* Name or pseudonym:
+* Name or pseudonym:
+

archive/checking/level1-affirm/sub-title.md

@@ -0,0 +1 @@
+How do I affirm that I have finished level 1 checking?

archive/checkingl/evel1-affirm/title.md

@@ -0,0 +1 @@
+Level 1 Affirmation

archive/process/config.yaml

@@ -0,0 +1,65 @@
+intro-publishing:
+  recommended: []
+  dependencies:
+    - prechecking-training
+intro-share:
+  recommended:
+    - share-content
+  dependencies:
+    - intro-publishing
+platforms:
+  recommended:
+    - setup-ts
+    - pretranslation-training
+  dependencies:
+    - process-manual
+    - file-formats
+prechecking-training:
+  recommended:
+    - intro-check
+    - goal-checking
+    - required-checking
+  dependencies:
+    - pretranslation-training
+pretranslation-training:
+  recommended:
+    - choose-team
+    - translate-source-text
+    - translate-alphabet
+    - writing-decisions
+    - translation-difficulty
+  dependencies:
+    - translate-process
+    - translate-why
+process-manual:
+  recommended: []
+  dependencies:
+    - finding-answers
+required-checking:
+  recommended:
+    - intro-publishing
+  dependencies:
+    - prechecking-training
+setup-team:
+  recommended:
+    - choose-team
+    - qualifications
+    - translate-source-text
+    - translate-alphabet
+    - writing-decisions
+    - translation-difficulty
+  dependencies:
+    - translate-process
+setup-ts:
+  recommended: []
+  dependencies:
+    - platforms
+share-content:
+  recommended: []
+  dependencies:
+    - intro-share
+source-text-process:
+  recommended:
+    - intro-share
+  dependencies:
+    - intro-publishing

archive/process/intro-publishing/01.md

@@ -0,0 +1,12 @@
+
+### Publishing Overview
+
+Once a work has been uploaded to Door43, it is automatically available online under your user account. This is referred to as self-publishing. You will have access to a web version of your project at http://door43.org/u/user_name/project_name (where user_name is your username and project_name is your translation project). The translationStudio app will give you the correct link when you upload. You can also browse all works on http://door43.org.
+
+From your Door43 project page you can:
+
+* See the web version of your project with default formatting
+* Download documents of your project (like a PDF)
+* Get the links to the source files (USFM or Markdown) for your project
+* Interact with others about your project
+

archive/process/intro-publishing/sub-title.md

@@ -0,0 +1 @@
+What is publishing?

archive/process/intro-publishing/title.md

@@ -0,0 +1 @@
+Introduction to Publishing

archive/process/intro-share/01.md

@@ -0,0 +1,15 @@
+
+### Distribution Overview
+
+Content is worthless unless it is disseminated and used. One advantage of using the Door43 translation and publishing platform is that it provides multiple, simple ways of distributing content.
+
+### Open License
+
+The biggest factor that encourages distribution of content is the [Open License](../../intro/open-license/01.md) that is used for all content on Door43. This license gives everybody the freedom they need to:
+
+* **Share** — copy and redistribute the material in any medium or format
+* **Adapt** — remix, transform, and build upon the material
+
+for any purpose, even commercially.
+
+Under the terms of the license.

archive/process/intro-share/sub-title.md

@@ -0,0 +1 @@
+How can I distribute content?

archive/process/intro-share/title.md

@@ -0,0 +1 @@
+Introduction to Distribution

archive/process/platforms/01.md

@@ -0,0 +1,8 @@
+
+### Recommended Platform
+
+The recommended platform for doing translation in the Door43 ecosystem is translationStudio (http://ufw.io/ts/). This is where the translation and checking teams will do their work. You may set up translationStudio on Android, Windows, Mac, or Linux devices, (see [Setting up translationStudio](../setup-ts/01.md) for more information).
+
+### Other Options
+
+If using translationStudio is not an option for your team, then you may consider using other online or offline tools. Note that it will be your responsibility to get the content into USFM or Markdown format if you do not use translationStudio (see [File Formats](../../translate/file-formats/01.md) for more information).

archive/process/platforms/sub-title.md

@@ -0,0 +1 @@
+What tool can I use to translate?

archive/process/platforms/title.md

@@ -0,0 +1 @@
+Selecting a Platform

archive/process/prechecking-training/01.md

@@ -0,0 +1,4 @@
+
+### Before Checking
+
+It is recommended that you consult the [Checking Manual](../../checking/intro-check/01.md) frequently as you check this content. Before you start checking, we recommend that you start working your way through the Checking Manual until you understand what is required at each level. As you work through the checking process, you will need to consult the Checking Manual frequently.

archive/process/prechecking-training/sub-title.md

@@ -0,0 +1 @@
+What should I know about checking before I begin?

archive/process/prechecking-training/title.md

@@ -0,0 +1 @@
+Training Before Checking Begins

archive/process/pretranslation-training/01.md

@@ -0,0 +1,18 @@
+
+### What to Know Before Translation
+
+It is recommended that you consult the [Translation Manual](../../translate/translate-manual/01.md) frequently as you translate this content. Before you start translating, we recommend that you start working your way through the Translation Manual at least until you know the difference between a literal translation and a meaning-based translation. Much of the rest of the Translation Manual can be used as a "just-in-time" learning resource.
+
+Some important subjects that must be learned before starting a translation project:
+
+* [The Qualities of a Good Translation](../../translate/guidelines-intro/01.md) - The definition of a good translation
+* [The Translation Process](../../translate/translate-process/01.md) - How a good translation is made
+  * [Form and Meaning](../../translate/translate-fandm/01.md) - The difference between form and meaning
+  * [Meaning-Based Translations](../../translate/translate-dynamic/01.md) - How to make a meaning-based translation
+
+Some other important topics as you get started include:
+
+* [Choosing What to Translate](../../translate/translation-difficulty/01.md) - Suggestions for where to start translating
+* [First Draft](../../translate/first-draft/01.md) - How to make a first draft
+* [Help with Translating](../../translate/translate-help/01.md) - Using translation helps
+

archive/process/pretranslation-training/sub-title.md

@@ -0,0 +1 @@
+What should I know about translation before I start?

archive/process/pretranslation-training/title.md

@@ -0,0 +1 @@
+Training Before Translation Begins

archive/process/process-manual/01.md

@@ -0,0 +1,8 @@
+
+### Welcome
+
+The Process Manual is a step-by-step guide to help translation teams know what they need to do, from the start of a project to its completion. This guide will help a translation team from its initial setup to final publishing of translated and checked content.
+
+### Getting Started
+
+Translation is a complicated task and takes organization and a plan. There are many required steps to take a translation from an idea to completed, checked, distributed, and in use translation. The information in this Process Manual will help you know all of the necessary steps in the translation process.

archive/process/process-manual/sub-title.md

@@ -0,0 +1 @@
+What is the Process Manual?

archive/process/process-manual/title.md

@@ -0,0 +1 @@
+Introduction to the Process Manual

archive/process/required-checking/01.md

@@ -0,0 +1,16 @@
+
+### Purpose of Checking Levels
+
+The purpose of the Checking Levels (see [Checking Manual](../../checking/intro-check/01.md)) is primarily to help ensure that the translation has been made in accordance with the [Statement of Faith](../../intro/statement-of-faith/01.md) and the [Translation Guidelines](../../intro/translation-guidelines/01.md). Another reason is to increase the input and ownership of the community that will be using it.
+
+#### Checking Level 1
+
+Checking Level 1 is done primarily by the translation team, with some input from the language community. See [Checking Level One - Affirmation by Translation Team](../../checking/level1/01.md). After completing the Level 1 Check, you are encouraged to upload to Door43 (see [Introduction to Publishing](../intro-publishing/01.md)) and continue on to Checking Level 2 (see below).
+
+#### Checking Level 2
+
+Checking Level 2 is done to verify that representative groups from the local language community agree that the translation is a good one (see [Checking Level Two - Affirmation by Community](../../checking/level2/01.md)). It is done with a language community check (see [Language Community Check](../../checking/language-community-check/01.md)) and a church leader check (see [Church Leader Check](../../checking/church-leader-check/01.md)). After completing the Level 2 Check, you are encouraged to upload to Door43 (see [Introduction to Publishing](../intro-publishing/01.md)) and continue on to Checking Level 3 (see below), if you so desire.
+
+#### Checking Level 3
+
+Checking Level 3 is done when leaders of at least two church networks agree that the translation is a good one (see [Checking Level Three - Affirmation by Church Leadership](../../checking/level3/01.md)). Be sure you work through the Level 3 Checking Questions (see [Questions for Checking on Level Three](../../checking/level3-questions/01.md)) while you complete this checking level. After completing the Level 3 Check, you are encouraged to upload to Door43 (see [Introduction to Publishing](../intro-publishing/01.md)). This is the highest checking level. Gateway Languages should also complete the [Source Text Process](../source-text-process/01.md)

archive/process/required-checking/sub-title.md

@@ -0,0 +1 @@
+How do I check a translation?

archive/process/required-checking/title.md

@@ -0,0 +1 @@
+How to Check

archive/process/setup-team/01.md

@@ -0,0 +1,25 @@
+
+### Choosing a Team
+
+As you begin selecting a translation and checking team, there are many different types of people and roles that are needed. There are also specific qualifications that are needed for each team.
+
+* [Choosing a Translation Team](../../translate/choose-team/01.md) - Describes many of the roles that are needed
+* [Translator Qualifications](../../translate/qualifications/01.md) - Describes some of the skills needed by the translators
+* Remember that everyone on the team needs to sign a statement that they agree with (forms are available at http://ufw.io/forms/ ):
+  * [Statement of Faith](../../intro/statement-of-faith/01.md)
+  * [Translation Guidelines](../../intro/translation-guidelines/01.md)
+  * [Open License](../../intro/open-license/01.md)
+* Everyone on the team also needs to know the qualities of a good translation (see [The Qualities of a Good Translation](../../translate/guidelines-intro/01.md)).
+* The team will also need to know where they can find answers (see [Finding Answers](../../intro/finding-answers/01.md)).
+
+### Translation Decisions
+
+There are many decisions the translation team will have to make, many of them right at the beginning of the project. Included are the following:
+
+* [Choosing What to Translate](../../translate/translation-difficulty/01.md) - Choosing what to translate first is another decision to be made
+* [Choosing a Source Text](../../translate/translate-source-text/01.md) - Choosing a good source text is very important
+  * [Copyrights, Licensing, and Source Texts](../../translate/translate-source-licensing/01.md) - Copyright issues must be considered when choosing a source text
+  * [Source Texts and Version Numbers](../../translate/translate-source-version/01.md) - Translating from the latest version of a source text is best
+* [Alphabet/Orthography](../../translate/translate-alphabet/01.md) - Many languages have alphabet decisions that need to be made
+* [Decisions for Writing Your Language](../../translate/writing-decisions/01.md) - Writing style, punctuation, translating names, spelling, and other decisions have to be made
+

archive/process/setup-team/sub-title.md

@@ -0,0 +1 @@
+How can I set up a translation team?

archive/process/setup-team/title.md

@@ -0,0 +1 @@
+Setting Up a Translation Team

archive/process/setup-ts/01.md

@@ -0,0 +1,21 @@
+
+### Installing tS for Mobile
+
+The mobile (Android) edition of translationStudio is available from the [Google Play Store](https://play.google.com/store/apps/details?id=com.translationstudio.androidapp ) or via direct download from http://ufw.io/ts/. If you install from the Play Store, then you will be notified by the Play Store when a new version is available. Note that you may also side load the installation apk to other devices to share the app.
+
+### Installing tS for Desktop
+
+The latest version of translationStudio for desktop or laptop computers (Windows, Mac, or Linux) is available from http://ufw.io/ts/. To install the program, navigate to the "Desktop" section and download the latest release. Note that you may also copy the installation file to other computers to share the app.
+
+### Using tS
+
+Once installed, both editions of translationStudio are designed to work similarly. You *do not* need an internet connection to use translationStudio! First-time use of translationStudio will require an agreement to the [Statement of Faith](../../intro/statement-of-faith/01.md), the [Translation Guidelines](../../intro/translation-guidelines/01.md), and the [Open License](../../intro/open-license/01.md).
+
+After the first-use screen, you will be brought to the Home screen where you can create a new project. Once your project is created, you may start translating right away. There are translationHelps built right into the app which you are encouraged to use to gain a better understanding of the source text. Note that your work is automatically saved. You may also choose to back up, share, or upload your work at various intervals (use the menu to access these functions).
+
+### After Using tS
+
+1. We strongly recommend that your translation be checked (see [Training Before Checking Begins](../prechecking-training/01.md)).
+1. Once the checking is complete (to any level), you may upload your work from the app (Menu → Upload).
+1. Once uploaded, you can see your work online on Door43 (see [Publishing](../intro-publishing/01.md))
+

archive/process/setup-ts/sub-title.md

@@ -0,0 +1 @@
+How do I set up translationStudio?

archive/process/setup-ts/title.md

@@ -0,0 +1 @@
+Setting Up translationStudio

archive/process/share-content/01.md

@@ -0,0 +1,12 @@
+
+### Sharing Content from tS
+
+Sharing content that is in translationStudio is easy. For offine sharing, use the Backup feature from the tS menu. For online sharing, use the Upload feature from the tS menu.
+
+### Sharing Content on Door43
+
+If you upload your work from translationStudio, then it automatically appears on the Internet on Door43. All of your uploaded content will appear under your user account. For example, if your username is *test_user* then you may find all your work at http://door43.org/u/test_user/. You can share your work with others online by giving them the link to the projects you have uploaded.
+
+### Sharing Content Offline
+
+You may also generate and download documents from your project pages on Door43. Once you have these downloaded, you can transfer them to others however you would like, including printing and distributing hard copies.

archive/process/share-content/sub-title.md

@@ -0,0 +1 @@
+How can I share content?

archive/process/share-content/title.md

@@ -0,0 +1 @@
+How to Share Content

archive/process/source-text-process/01.md

@@ -0,0 +1,32 @@
+
+### Source Text Process
+
+Source text publishing is required for all Gateway Languages so that they can be used as source texts by Other Languages. Note that this process only applies to Gateway Languages.
+
+#### Prerequisites
+
+Before a Gateway Language translation can become a source text, the following prerequisites must all be met:
+
+* **Whole Resource** - The whole resource must be translated and checked to the required level. Parts of resources (e.g. half of the Open Bible Stories, only a few chapters of a book of the Bible) cannot be published.
+* **Checking** - A translation must have reached the appropriate checking level. For Bible translations, that means [Checking Level Three - Affirmation by Church Leadership](../../checking/level3/01.md).
+* **On Door43** - Door43 must have the version that will be published. If the work was done on multiple devices, then it may need to be merged together. Get the help of a Content Tech to make merging easier (either email <help@door43.org> or use the #content-techs channel on Slack).
+* **Agreements** - Everyone involved in the translation and checking must have agreed to the [Statement of Faith](../../intro/statement-of-faith/01.md), the [Translation Guidelines](../../intro/translation-guidelines/01.md), and the [Open License](../../intro/open-license/01.md). This can be done by either creating Door43 accounts or by physically signing the documents and digitizing them (scanning or photos). See http://ufw.io/forms for downloadable agreement forms.
+
+#### Source Text Request Form
+
+Once you have the prerequisites, you may fill out the source text request form at http://ufw.io/pub/. A few notes about the form:
+
+* You must have a Door43 account to create a request.
+* You must include the names or pseudonyms of everyone involved. You must also include their Door43 usernames if you are not attaching signed license agreements for them.
+* Note that the information you enter will be public and will become a part of the front matter of the source text.
+
+After your form has been submitted, you will be contacted if anything is missing. Once the request has been approved, it will go into the publishing queue where a developer will work to make the translation a source text. You may also be contacted by the developer if there are any issues encounted during the publishing process. You will be notified when the process is completed and you may review a PDF of the work.
+
+### Finishing the Source Text Process
+
+After the source text publishing process is completed, your work will then be available:
+
+* Online on the unfoldingWord website
+* As a PDF, downloadable from unfoldingWord
+* In translationStudio as a source text for Other Languages to use (may require a tS update first)
+

archive/process/source-text-process/sub-title.md

@@ -0,0 +1 @@
+How do I make my Gateway Language translation a source text?

archive/process/source-text-process/title.md

@@ -0,0 +1 @@
+Source Text Process

archive/process/toc.yaml

@@ -0,0 +1,41 @@
+title: "Table of Contents"
+sections:
+  - title: "1. Getting Started"
+    sections:
+      - title: "Introduction to the Process Manual"
+        link: process-manual
+
+  - title: "2. Setting Up a Translation Team"
+    sections:
+      - title: "Setting Up A Translation Team"
+        link: setup-team
+
+  - title: "3. Translating"
+    sections:
+      - title: "Training Before Translation Begins"
+        link: pretranslation-training
+      - title: "Choosing a Translation Platform"
+        link: platforms
+      - title: "Setting Up translationStudio"
+        link: setup-ts
+
+  - title: "4. Checking"
+    sections:
+      - title: "Training Before Checking Begins"
+        link: prechecking-training
+      - title: "How to Check"
+        link: required-checking
+
+  - title: "5. Publishing"
+    sections:
+      - title: "Introduction to Publishing"
+        link: intro-publishing
+      - title: "Source Text Process"
+        link: source-text-process
+
+  - title: "6. Distributing"
+    sections:
+      - title: "Introduction to Distribution"
+        link: intro-share
+      - title: "How to Share Content"
+        link: share-content

archive/readme.md

@@ -0,0 +1 @@
+This folder has been created to preserve topics or pages that are no longer necessary but should not be deleted.

archive/translate/figs-inclusive/01.md

@@ -0,0 +1,26 @@
+
+
+### Description
+
+Some languages have more than one form of "we": an **inclusive** form that means "I and you" and an **exclusive** form that means "I and someone else but not you." The inclusive form includes the person being spoken to and possibly others. This is also true for "us," "our," "ours," and "ourselves." Some languages have inclusive forms and exclusive forms for each of these.
+
+See the pictures. The people on the right are the people that the speaker is talking to. The yellow highlight shows who the inclusive "we" and the exclusive "we" refer to.
+
+![](https://cdn.door43.org/ta/jpg/vocabulary/we_us_inclusive.jpg)
+
+![](https://cdn.door43.org/ta/jpg/vocabulary/we_us_exclusive.jpg)
+
+### Reasons this is a translation issue
+
+The Bible was first written in the Hebrew, Aramaic, and Greek languages. Like English, these languages do not have separate exclusive and inclusive forms for "we." Translators whose language has separate exclusive and inclusive forms of "we" will need to understand what the speaker meant so they can decide which form of "we" to use.
+
+### Examples from the Bible
+
+>... the shepherds said one to each other, "Let <u>us</u> now go to Bethlehem, and see this thing that has happened, which the Lord has made known to <u>us</u>." (Luke 2:15 ULB)
+
+The shepherds were speaking to one another. When they said "us," they were including the people they were speaking to - one another.
+
+>Now it happened on one of those days that Jesus and his disciples entered into a boat, and he said to them, "Let <u>us</u> go over to the other side of the lake." Then they set sail. (Luke 8:22 ULB)
+
+When Jesus said "us," he was referring to himself and to the disciples he was speaking to.
+

archive/translate/figs-inclusive/sub-title.md

@@ -0,0 +1 @@
+What is inclusive "we"?

archive/translate/figs-inclusive/title.md

@@ -0,0 +1 @@
+Inclusive "We"

archive/translate/figs-informremind/01.md

@@ -0,0 +1,70 @@
+
+### Should we delete this document and folder? - Archived.
+
+Some languages can use a word or phrase with a noun to give information about that noun or to remind people of something about it.
+
+* Mary gave some of the food to her sister, <u>who was very thankful</u>.
+
+The phrase "who was very thankful" immediately follows the word "sister" and informs us about how Mary's sister responded when Mary gave her the food. In this case it does not distinguish this sister from another sister that Mary might have. It simply gives added information about that sister.
+
+### Description
+
+Some languages can use a word or phrase with a noun to give information about that noun or to remind people of something about it.
+
+* Mary gave some of the food to her sister, <u>who was very thankful</u>.
+
+The phrase "who was very thankful" immediately follows the word "sister" and informs us about how Mary's sister responded when Mary gave her the food. In this case it does not distinguish this sister from another sister that Mary might have.
+
+**Reason people use these phrases**: People often present either reminders or new information in a weak way. They do this when they want their listener to give most of his attention to something else they are saying. In the example above, the speaker wants most attention to be given to what Mary did, NOT to how her sister responded.
+
+### Reasons this is a translation issue
+
+Languages have different ways of signaling the parts of communication that the listener should pay most attention to.
+
+### Translation principles
+
+* If your language does not use phrases with a noun for new information or a reminder, you may need to put that information or reminder in a different part of the sentence.
+* Try to present it in a weak way.
+* Ask yourself: In our language, how do we express information in a strong way, and how do we express it in a weaker way?
+
+### Examples from the Bible
+
+>The name of the third river is Tigris, <u>which flows east of Asshur</u>. (Genesis 2:14 ULB)
+
+There is only one Tigris River. The phrase "which flows east of Asshur" gives more information about where the Tigris River was. This would have been helpful to the original audience, because they knew were Asshur was.
+
+>I will wipe away mankind <u>whom I have created</u> from the surface of the earth. (Genesis 6:7 ULB)
+
+The phrase "whom I have created" is a reminder of the relationship between God and mankind. It is the reason God had the right to wipe away mankind.
+
+>I will bring an end to the <u>worthless</u> idols of Memphis. (Ezekiel 30:13 ULB)
+
+All idols are worthless. This is why God said he would destroy them.
+
+>... for your <u>righteous</u> judgments are good. (Psalm 119:39 ULB)
+
+All of God's judgments are righteous. This is why the person who wrote this psalm said that they are good.
+
+### Translation Strategies
+
+If people would understand the purpose of a phrase with a noun, then consider keeping the phrase and the noun together. Otherwise, here are other strategies of showing that the phrase is used to inform or remind.
+
+1. Put the information in another part of the sentence and add words that show its purpose.
+1. Use one of your language's ways for expressing information in a weak way. It may be by adding a small word, or by changing the way the voice sounds. Sometimes changes in the voice can be shown with punctuation marks, such as parentheses or commas.
+
+### Examples of Translation Strategies Applied
+
+1. Put the information in another part of the sentence and add words that show its purpose.
+  * **I hate those who serve <u>worthless</u> idols** (Psalm 31:6 ULB) - By saying "worthless idols," David was commenting about all idols and giving his reason for hating those who serve them. He was not distinguishing worthless idols from valuable idols.
+      * <u>Because</u> idols are worthless, I hate those who serve them.
+  * **... for your <u>righteous</u> judgments are good.** (Psalm 119:39 ULB)
+      * ... for your judgments are good <u>because</u> they are righteous.
+  * **Can Sarah, <u>who is ninety years old</u>, bear a son?** (Genesis 17:17-18 ULB) - The phrase "who is ninety years old" is a reminder of Sarah's age. It tells why Abraham was asking the question. He did not expect that a woman who was that old could bear a child.
+      * Can Sarah bear a son <u>even when</u> she is ninety years old?
+  * **I will call on Yahweh, <u>who is worthy to be praised</u> ...** (2 Samuel 22:4 ULB) - There is only one Yahweh. The phrase "who is worthy to be praised" gives a reason for calling on Yahweh.
+      * I will call on Yahweh, <u>because</u> he is worthy to be praised ...  
+  
+1. Use one of your language's ways for expressing information in a weak way.
+  * **The name of the third river is Tigris, <u>which flows east of Asshur</u>.** (Genesis 2:14 ULB)
+      * The name of the third river is Tigris. <u>It flows east of Asshur</u>.
+

archive/translate/figs-informremind/sub-title.md

@@ -0,0 +1 @@
+When phrases are used with nouns, what are phrases that inform or remind and how can I translate them?

archive/translate/figs-informremind/title.md

@@ -0,0 +1 @@
+Phrases that Inform or Remind

archive/translate/figs-infostructure/01.md

@@ -0,0 +1,67 @@
+### Description
+
+Different languages arrange the parts of the sentence in different ways. In English, a sentence normally has the subject first, then the verb, then the object, then other modifiers, like this:
+
+**Peter painted his house yesterday.**
+
+Many other languages normally put these things in a different order, such as:
+
+**Painted yesterday Peter his house.**
+
+Although all languages have a normal order for parts of a sentence, this order can change depending on what information the speaker or writer considers to be the most important. Suppose that someone is answering the question, "What did Peter paint yesterday?" The person asking the question already knows all of the information in our sentence above except for the object: "his house." Therefore, that becomes the most important part of the information, and a person answering in English might say:
+
+**His house is what Peter painted (yesterday).**
+
+This puts the most important information first, which is normal for English. Many other languages would normally put the most important information last. In the flow of a text, the most important information is usually what the writer considers to be new information for the reader. In some languages the new information comes first, and in others it comes last.
+
+### Reasons this is a translation issue
+
+* Different languages arrange the parts of a sentence in different ways. If a translator copies the order of the parts of a sentence from the source, it may not make sense in his language.
+* Different languages put important or new information in different places in the sentence. If a translator keeps the important or new information in the same place that it had in the source language, it may be confusing or give the wrong message in his language.
+
+### Examples from the Bible
+
+>They all ate until they were satisfied. (Mark 6:42 ULB)
+
+The parts of this sentence were in a different order in the original Greek source language. They were like this:
+
+* And they ate all and they were satisfied.
+
+In English, this means that the people ate everything. But the next verse says that they took up twelve baskets full of leftover pieces of food. In order for this to not be so confusing, the translators of the ULB put the parts of the sentence in the right order for English.
+
+>Now the day was about to come to an end, and the twelve came to him and said, "Send the crowd away that they may go into the surrounding villages and countryside to find lodging and food, because we are here in an isolated place." (Luke 9:12 ULB)
+
+In this verse, what the disciples say to Jesus puts the important information first - that he should send the crowd away. But in languages that put the important information last, people would understand that the reason that they give - being in an isolated place - is the most important part of their message to Jesus. They might then think that the disciples are afraid of the spirits in that place, and that sending the people to buy food is a way to protect them from the spirits. That is the wrong message.
+
+>Woe to you when all men speak well of you, for that is how their ancestors treated the false prophets. (Luke 6:26 ULB)
+
+In this verse, the most important part of the information is first - that "woe" is coming on the people for what they are doing. The reason that supports that warning comes last. This could be confusing for people who expect the important information to come last.
+
+### Translation Strategies
+
+1. Study how your language arranges the parts of a sentence, and use that order in your translation.
+1. Study where your language puts the new or important information, and rearrange the order of information so that it follows the way it is done in your language.
+
+### Translation Strategies Applied
+
+1. Study how your language arranges the parts of a sentence, and use that order in your translation.
+
+* And he went out from there and came to the hometown his, and they followed him the disciples his. (Mark 6:1)
+
+This is the verse in the original Greek order. The ULB has put this into the normal order for English:
+>He went out from there and came to his hometown, and his disciples followed him. (Mark 6:1 ULB)
+
+1. Study where your language puts the new or important information, and rearrange the order of information so that it follows the way it is done in your language.
+
+>Now the day was about to come to an end, and the twelve came to him and said, "Send the crowd away that they may go into the surrounding villages and countryside to find lodging and food, because we are here in an isolated place." (Luke 9:12 ULB)
+
+If your language puts the important information last, you can change the order of the verse:
+
+* Now the day was about to come to an end, and the twelve came to him and said, "Because we are here in an isolated place, send the crowd away that they may go into the surrounding villages and countryside to find lodging and food."
+
+>Woe to you, when all men speak well of you, for that is how their ancestors treated the false prophets. (Luke 6:26 ULB)
+
+If your language puts the important information last, you can change the order of the verse:
+
+* When all men speak well of you, which is just as their ancestors treated the false prophets, then woe to you!
+

archive/translate/figs-infostructure/sub-title.md

@@ -0,0 +1 @@
+How do languages arrange the parts of a sentence?

archive/translate/figs-infostructure/title.md

@@ -0,0 +1 @@
+Information Structure

archive/translate/figs-quotemarks/01.md

@@ -0,0 +1,70 @@
+
+
+### Description
+
+Some languages use quotation marks to mark off direct quotes from the rest of the text. English uses the mark " before and after a quote.
+
+* John said, "I do not know when I will arrive."
+
+Quotation marks are not used with indirect quotes.
+
+* John said that he did not know when he would arrive.
+
+When there are many layers of quotes inside of quotes, it might be hard for readers to understand who is saying what. Alternating two kinds of quote marks can help careful readers to keep track of them. In English the outermost quote has double quote marks, and the next quote inside has single marks. The next quote inside of that has double quote marks.
+
+* Mary said, "John said, 'I do not know when I will arrive.' "
+* Bob said, "Mary said, 'John said, "I do not know when I will arrive." ' "
+
+Some languages use other kinds of quotation marks: Here are some examples: ‚ ' „ " ‹ › « » ⁊ — .
+
+### Examples from the Bible
+
+The examples below show the kind of quote marking used in the ULB.
+
+#### A quotation with only one layer
+
+A first layer direct quote has double quote marks around it.
+>So the king replied, "That is Elijah the Tishbite." (2 Kings 1:8 ULB)
+
+#### Quotations with two layers
+
+A second layer direct quote has single quote marks around it. We have underlined it and the phrase for you to see it clearly.
+>They asked him, "Who is the man that said to you, <u>'Pick up your bed and walk'</u>?" (John 5:12 ULB)
+
+>... he sent two of the disciples, saying, "Go into the next village. As you enter, you will find a colt that has never been ridden. Untie it and bring it to me. If any one asks you, <u>'Why are you untying it?'</u> say, <u>'The Lord has need of it.'</u> " (Luke 19:29-31 ULB)
+
+#### A quotation with three layers
+
+A third layer direct quote has double quote marks around it. We have underlined it for you to see it clearly.
+>Abraham said, "Because I thought, 'Surely there is no fear of God in this place, and they will kill me because of my wife.' Besides, she is indeed my sister, the daughter of my father, but not the daughter of my mother; and she became my wife. When God caused me to leave my father's house and travel from place to place, I said to her, 'You must show me this faithfulness as my wife: At every place where we go, say about me, <u>"He is my brother."</u>'" (Genesis 20:10-13 ULB)
+
+#### A quotation with four layers
+
+A fourth layer direct quote has single quote marks around it. We have underlined it for you to see it clearly.
+>They said to him, "A man came to meet us who said to us, 'Go back to the king who sent you, and say to him, "Yahweh says this: <u>'Is it because there is no God in Israel that you sent men to consult with Baal-Zebub, the god of Ekron? Therefore you will not come down from the bed to which you have gone up; instead, you will certainly die.'</u>"'" (2 Kings 1:5-6 ULB)
+
+### Quote Marking Strategies
+
+Here are some ways you may be able to help readers see where each quote starts and ends so they can more easily know who said what.
+
+1. Alternate two kinds of quote marks to show layers of direct quotation. English alternates double quote marks and single quote marks.
+1. Translate one or some of the quotes as indirect quotes in order to use fewer quote marks, since indirect quotes do not need them. (see [Direct and Indirect Quotations](../figs-quotations/01.md))
+1. If a quotation is very long and has many layers of quotation in it, indent the main overall quote, and use quote marks only for the direct quotes inside of it.
+
+### Examples of Quote Marking Strategies Applied
+
+1. Alternate two kinds of quote marks to show layers of direct quotation as shown in the ULB text below.
+
+    * **They said to him, "A man came to meet us who said to us, 'Go back to the king who sent you, and say to him, "Yahweh says this: 'Is it because there is no God in Israel that you sent men to consult with Baal-Zebub, the god of Ekron? Therefore you will not come down from the bed to which you have gone up; instead, you will certainly die.'"'"** (2 Kings 1:6 ULB)  
+  
+1. Translate one or some of the quotes as indirect quotes in order to use fewer quote marks, since indirect quotes do not need them. In English the word "that" can introduce an indirect quote. In the example below, everything after the word "that" is an indirect quote of what the messengers said to the king. Within that indirect quote, there are some direct quotes marked with " and '.
+
+    * **They said to him, "A man came to meet us who said to us, 'Go back to the king who sent you, and say to him, "Yahweh says this: 'Is it because there is no God in Israel that you sent men to consult with Baal-Zebub, the god of Ekron? Therefore you will not come down from the bed to which you have gone up; instead, you will certainly die.'"'"** (2 Kings 1:6 ULB)
+      * They told him <u>that</u> a man came to meet them who said to them, "Go back to the king who sent you, and say to him, 'Yahweh says this: "Is it because there is no God in Israel that you sent men to consult with Baal-Zebub, the god of Ekron? Therefore you will not come down from the bed to which you have gone up; instead, you will certainly die."'"  
+  
+1. If a quotation is very long and has many layers of quotation in it, indent the main overall quote, and use quote marks only for the direct quotes inside of it.
+
+      * **They said to him, "A man came to meet us who said to us, 'Go back to the king who sent you, and say to him, "Yahweh says this: 'Is it because there is no God in Israel that you sent men to consult with Baal-Zebub, the god of Ekron? Therefore you will not come down from the bed to which you have gone up; instead, you will certainly die.'"'"** (2 Kings 1:6 ULB)
+        * They said to him,  
+          A man came to meet us who said to us, "Go back to the king who sent you, and say to him, 'Yahweh says this: "Is it because there is no God in Israel that you sent men to consult with Baal-Zebub, the god of Ekron? Therefore you will not come down from the bed to which you have gone up; instead, you will certainly die."'"
+

archive/translate/figs-quotemarks/sub-title.md

@@ -0,0 +1 @@
+How can quotes be marked, especially when there are quotes within quotes?

archive/translate/figs-quotemarks/title.md

@@ -0,0 +1 @@
+Quote Markings

archive/translate/figs-synonparallelism/01.md

@@ -0,0 +1,60 @@
+
+### Description
+
+**Parallelism with the same meaning** is a poetic device in which one complex idea is expressed in two or more different ways. Speakers may do this in order to emphasize the idea that is the same in the two phrases. This is also called "synonymous parallelism."
+
+Note: We use the term "parallelism with the same meaning" for long phrases or clauses that have the same meaning. We use the term [Doublet](../figs-doublet/01.md) for words or very short phrases that mean basically the same thing and are used together.
+>Yahweh <u>sees everything a person does</u> and <u>watches all the paths he takes</u>. (Proverbs 5:21 ULB)
+
+The first underlined phrase and the second underlined phrase mean the same thing. There are three ideas that are the same between these two phrases. "Sees" corresponds to "watches," "everything ... does" corresponds to "all the paths ... takes," and "a person" corresponds to "he."
+
+Synonymous parallelism in poetry has several effects:
+
+* It shows that something is very important by saying it more than once and in more than one way.
+* It helps the hearer to think more deeply about the idea by saying it in different ways.
+* It makes the language more beautiful and above the ordinary way of speaking.
+
+### Reasons this is a translation issue
+
+In some languages people do not expect someone to say the same thing twice, even in different ways. They expect that if there are two phrases or two sentences, they must have different meanings. So they do not understand that the repetition of ideas serves to emphasize the idea.
+
+### Examples from the Bible
+
+>Your word is a lamp to my feet and a light for my path. (Psalm 119:105 ULB)
+
+Both parts of the sentences are metaphors saying that God's word teaches people how to live. The words "lamp" and "light" are similar in meaning because they refer to light, and the words "my feet" and "my path" are related, because they refer to a person walking.
+><u>Praise Yahweh</u>, all you nations; <u>exalt him</u>, all you peoples. (Psalm 117:1 ULB)
+
+Both parts of this verse tell people everywhere to praise Yahweh. The words 'Praise' and 'exalt' mean the same thing, 'Yahweh' and 'him' refer to the same person, and 'all you nations' and 'all you peoples' refer to the same people.
+>For Yahweh has a <u>lawsuit with his people</u>, and he will <u>fight in court against Israel</u>. (Micah 6:2 ULB)
+
+The two parts of this verse say that Yahweh has a serious disagreement with his people, Israel. These are not two different disagreements or two different groups of people.
+
+### Translation Strategies
+
+If your language uses parallelism in the same way as the biblical languages, that is, to strengthen a single idea, then it would be appropriate to use it in your translation. But if your language does not use parallelism in this way, then consider using one of the following translation strategies.
+
+1. Combine the ideas of both clauses into one.
+1. If it appears that the clauses are used together to show that what they say is really true, you could include words that emphasize the truth such as "truly" or "certainly."
+1. If it appears that the clauses are used together to intensify an idea in them, you could use words like "very," "completely" or "all."
+
+### Examples of Translation Strategies Applied
+
+1. Combine the ideas of both clauses into one.
+ * **Until now you have <u>deceived me and told me lies</u>.** (Judges 16:13, ULB)<br/><br/>Delilah expressed this idea twice to emphasize that she was very upset.<br/><br/>
+      * Until now you have <u>deceived me with your lies</u>.
+ * **Yahweh <u>sees</u> <u>everything a person does</u> and <u>watches</u> <u>all the paths he takes</u>.** (Proverbs 5:21 ULB)<br/><br/>The word "watches" us a synonym for "sees," and the phrase "all the paths he takes" is a metaphor for "all he does."<br/><br/>
+      * Yahweh <u>pays attention</u> to <u>everything a person does</u>.
+ * **For Yahweh has a <u>lawsuit with his people</u>, and he will fight in court against Israel.** (Micah 6:2 ULB)<br/><br/>This parallelism describes one serious disagreement that Yahweh had with one group of people. If this is unclear, the phrases can be combined:<br/><br/>
+      * For Yahweh has a <u>lawsuit with his people</u>, Israel.  
+  
+1. If it appears that the clauses are used together to show that what they say is really true, you could include words that emphasize the truth such as "truly" or "certainly."
+ * **Yahweh <u>sees everything</u> a person does and watches all the paths he takes.** (Proverbs 5:21 ULB)
+      * Yahweh <u>truly sees everything</u> a person does.  
+  
+1. If it appears that the clauses are used together to intensify an idea in them, you could use words like "very," "completely" or "all."
+ * **... you have deceived me <u>and</u> told me lies.** (Judges 16:13 ULB)
+      * ... <u>all</u> you have done is lie to me.
+ * **Yahweh sees everything a person does <u>and</u> watches all the paths he takes.** (Proverbs 5:21 ULB)
+      * Yahweh sees <u>absolutely everything</u> that a person does.
+

archive/translate/figs-synonparallelism/sub-title.md

@@ -0,0 +1 @@
+What is parallelism with the same meaning?

archive/translate/figs-synonparallelism/title.md

@@ -0,0 +1 @@
+Parallelism with the Same Meaning

archive/translate/resources-clarify/01.md

@@ -0,0 +1,26 @@
+
+### Description
+
+Sometimes a Note suggests a translation from the UDB. In that case the text from the UDB will be followed by "(UDB)."
+
+### Translation Notes Examples
+
+>He who <u>sits in the heavens</u> will sneer at them (Psalm 2:4 **ULB**)
+
+>But the one who <u>sits on his throne in heaven</u> laughs at them (Psalm 2:4 **UDB**)
+
+The Note for this verse says:
+
+* **sits in the heavens** - Here sitting represents ruling. What he sits on can be stated clearly. AT: "rules in the heavens" or "sits on his throne in heaven" (UDB) (See: [Metonymy](../figs-metonymy/01.md) and [Explicit](../figs-explicit/01.md))
+
+Here there are two suggested translations for the phrase 'sits in the heavens.' The first expresses clearly what "sits in the heavens" represents. The second gives a hint about the idea of ruling by stated clearly that he sits on his "throne." This suggestion is from the UDB.
+
+>When he saw Jesus, <u>he fell on his face</u>. (Luke 5:12 **ULB**)
+
+>When he saw Jesus, <u>he bowed down to the ground</u>. (Luke 5:12 **UDB**)
+
+The Note for this verse says:
+
+* **he fell on his face** - "he knelt and touched the ground with his face" or "he bowed down to the ground" (UDB)
+
+Here the words from the UDB are provided as another translation suggestion.

archive/translate/resources-clarify/sub-title.md

@@ -0,0 +1 @@
+Why do some translationNotes have quotes from the UDB?

archive/translate/resources-clarify/title.md

@@ -0,0 +1 @@
+Notes that Include a Quote from the UDB

archive/translate/translate-decimal/01.md

@@ -0,0 +1,65 @@
+
+### Description
+
+The decimal point, or decimal comma, is a mark placed to the left of a number to show that the number refers to part of a whole number. For example .1 meter is not a whole meter but is only one tenth of a meter and .5 meter is not five meters, but is only five tenths of a meter. 3.7 meters is three and seven tenths of a meter. Numbers like these are used in the *Unlocked Dynamic Bible* (UDB).
+
+In some countries people use a decimal point, and in other countries people use a decimal comma. So translators in countries that use a decimal comma would write "3.7 meters" as "3,7 meters." In some cultures people prefer fractions. (see [Fractions](../translate-fraction/01.md))
+
+In the Unlocked Dynamic Bible (UDB) parts of a number are written as decimals or fractions. When they are used with a measurement such as meters, grams, and liters, the are usually written as decimals.
+
+#### Decimal Numbers in the UDB
+
+| Decimal | Fraction | Simpler Fraction |
+| -------- | -------- | -------- |
+|.1 |one tenth | |
+|.2 |two tenths | one fifth |
+|.3 |three tenths | |
+|.4 |four tenths | two fifths|
+|.5 |five tenths | one half |
+|.6 |six tenths | three fifths |
+|.7 |seven tenths |  |
+|.8 |eight tenths | four fifths |
+|.9 |nine tenths | |
+|.25 |twenty-five one hundredths | one fourth |
+|.75 |seventy-five one hundredths | three fourths |
+
+### Reasons this is a translation issue
+
+* If translators want to use the measures in the UDB, they will need to be able to understand the decimal numbers that are used with them.
+* Translators will need to write the numbers in a way that their readers will understand them.
+
+### Examples from the Bible
+
+For telling about parts of a number, the Unlocked Literal Bible (ULB) uses fractions, and the Unlocked Dynamic Bible (UDB) uses mostly decimals when the number is used with a measurement. Another difference between the ULB and the UDB is that when measuring [Biblical Distance](../translate-bdistance/01.md), [Biblical Weight](../translate-bweight/01.md), and [Biblical Volume](../translate-bvolume/01.md), they use different systems, so the numbers in the ULB and the UDB are not the same for these measures.
+>They are to make an ark of acacia wood. Its length must be <u>two and a half cubits</u>; its width will be <u>one cubit and a half</u>; and its height will be <u>one cubit and a half</u>. (Exodus 25:10 ULB)
+
+The ULB uses the fraction "half." The phrases "two and a half cubits ... one cubit and a half" can be written as "2.5 cubits ... 1.5 cubits."
+
+>They are to make an ark of acacia wood. Its length must be <u>one meter</u>; its width will be <u>0.7 meter</u>; and its height will be <u>0.7 meter</u> high. (Exodus 25:10)
+
+Here the decimal 0.7 is used. This equals seven tenths.
+
+Two and a half cubits is about one meter.
+
+One and a half cubits is about .7 meter or seven tenths of a meter.
+
+### Translation Strategies
+
+* Decide whether you want to use only fractions, only decimals, or a combination of the two.
+* Decide whether you want to use the measures given in the ULB or the UDB or some other kind of measures.
+* If you decide to use fractions and the measures in the ULB, simply translate the numbers and measures in the ULB.
+* If you decide to use decimals and the measures in the UDB, simply translate the numbers and measures in the UDB.
+
+1. If you decide to use decimals and the measures in the ULB, you will need to change the fractions in the ULB to decimals.
+1. If you decide to use fractions and the measures in the UDB, you will need to change the decimals in the UDB to fractions.
+
+### Examples of Translation Strategies Applied
+
+1. If you decide to use decimals and the measures in the ULB, you will need to change the fractions in the ULB to decimals.
+  * **<u>three-tenths of an ephah</u> of fine flour mixed with oil as a grain offering, and <u>one log</u> of oil.** (Leviticus 14:10 ULB)
+      * <u>0.3 ephah</u> of fine flour mixed with oil as a grain offering, and <u>one log</u> of oil. 
+  
+1. If you decide to use fractions and the measures in the UDB, you will need to change the decimals in the UDB to fractions.
+  * **<u>about 6.5 liters</u> of a fine flour offering, mixed with olive oil, to be an offering, and about <u>one third liter</u> of olive oil.** (Leviticus 14:10 UDB)
+      * <u>about six and a half liters</u> of a fine flour offering, mixed with olive oil, to be an offering, and about <u>one third liter</u> of olive oil.
+

archive/translate/translate-decimal/sub-title.md

@@ -0,0 +1 @@
+What are ordinal numbers and how can I translate them?

archive/translate/translate-decimal/title.md

@@ -0,0 +1 @@
+Decimal Numbers

checking/authentic-assessment/01.md

@@ -0,0 +1 @@
+Authentic Assessment

checking/authentic-assessment/sub-title.md

@@ -0,0 +1 @@
+What qualities are essential to a good translation?

checking/authentic-assessment/title.md

@@ -0,0 +1 @@
+Authentic Assessment

checking/goal-checking/01.md

@@ -1,20 +1,20 @@
 
 ### Why Check?
 
-The goal of checking is to help the translation team produce a translation that is accurate, natural, clear, and accepted by the church. The translation team also wants to achieve this goal. This might seem easy, but it is actually very difficult to do, and takes many people and many, many revisions to the translation to achieve. For this reason, the checkers play a very important role in helping the translation team to produce a translation that is accurate, natural, clear, and accepted by the church.
+The translation team's goal is produce a translation that is accurate, natural, clear, and accepted by the church. This goal will likely require the partnership of different people, resources, and tools to accomplish. For this reason, the checkers play a very important role in helping the translation team accomplish their goal. 
 
 #### Accurate
 
-The checkers who are pastors, church leaders, and leaders of church networks will help the translation team produce a translation that is accurate. They will do this by comparing the translation with the source language and, when possible, also with the original languages of the Bible. (For more information about accurate translations, see [Create Accurate Translations](../../translate/guidelines-accurate/01.md).)
+The checkers who are pastors, church leaders, and leaders of church networks will help the translation team produce a translation that is accurate. They will do this by comparing the translation with the source language and, when possible, also with the original languages of the Bible. They are also encouraged to use the translation tools created specifically for checking and available at bibleineverylanguage.org. 
 
 #### Clear
 
-The checkers who are members of the language community will help the translation team produce a translation that is clear. They will do this by listening to the translation and pointing out to them the places where the translation is confusing or does not make sense to them. Then the translation team can fix those places so that they are clear.  (For more information about clear translations, see [Create Clear Translations](../../translate/guidelines-clear/01.md).)
+The checkers who are members of the language community will help the translation team produce a translation that is clear. They will do this by listening to (or reading) the translation and pointing out (to the translators) the places where the translation is confusing or does not make sense to them. Then the translation team can fix those places so that they are clear. 
 
 #### Natural
 
-The checkers who are members of the language community will also help the translation team produce a translation that is natural. They will do this by listening to the translation and pointing out to them the places where the translation sounds strange and does not sound like the way that someone who speaks their language would say it. Then the translation team can fix those places so that they are natural.  (For more information about natural translations, see [Create Natural Translations](../../translate/guidelines-natural/01.md).)
+The checkers who are members of the language community will also help the translation team produce a translation that is natural. They will do this by listening to (or reading) the translation and pointing out (to the translators) the places where the translation sounds strange-- does not sound the way that someone who speaks their language would say it. Then the translation team can fix those places so that they are natural. (Translation notes, available at bibleineverylanguage.org is a tool that provides suggestions for handing meaning naturally in difficult passages.)
 
 #### Church-approved
 
-The checkers who are members of a church in the language community will help the translation team produce a translation that is approved and accepted by the church in that community. They will do this by working together with members and leaders of other churches from the language community. When members and leaders that represent the churches of a language community work together and agree that the translation is good, then it will be accepted and used by the churches in that community. (For more information about translations that are approved by the church, see [Create Church-Approved Translations](../../translate/guidelines-church-approved/01.md).)
+The checkers who are members of a church in the language community will help the translation team produce a translation that is approved and accepted by the church in that community. They will do this by working together with members and leaders of other churches from the language community, using the tools available at bibleineverlanguage.org as well as their own resources and other translations to carefully check the content of the newly translated scripture. When members and leaders that represent the churches of a language community work together and agree that the translation is good, then it will be accepted and used by the churches in that community. 

checking/headings/01.md

@@ -5,7 +5,7 @@ One of the decisions that the translation team will have to make is whether or n
 
 Using section headings requires more work, because you will have to either write or translate each one, in addition to the text of the Bible. It will also make your translation of the Bible longer. But section headings can be very helpful to your readers. Section headings make it much easier to find where the Bible talks about different things. If a person is looking for something in particular, he can just read the section headings until he finds one that introduces the topic that he wants to read about. Then he can read that section.
 
-If you have decided to use section headings, then you will need to decide which kind to use. Again, you will want to find out which kind of section heading the language community prefers, and you may also choose to follow the style of the national language.  Be sure to use a kind of section heading that the people will understand is not part of the text that it introduces. The section heading is not a part of scripture; it is just a guide to the different parts of scripture. You might be able to make this clear by putting a space before and after the section heading and using a different font (style of letters), or a different size of letters. See how the Bible in the national language does this, and test different methods with the language community.
+If you have decided to use section headings, then you will need to decide which kind to use. Again, you will want to find out which kind of section heading the language community prefers, and you may also choose to follow the style of the national language. Be sure to use a kind of section heading that the people will understand is not part of the text that it introduces. The section heading is not a part of scripture; it is just a guide to the different parts of scripture. You might be able to make this clear by putting a space before and after the section heading and using a different font (style of letters), or a different size of letters. See how the Bible in the national language does this, and test different methods with the language community.
 
 ### Kinds of Section Headings
 

checking/intro-check/01.md

@@ -1,10 +1,10 @@
+**** Authentic Assessment process
+
+Translation teams should work together (This is oftn done during the second day of a translation workshop.) to develop an authentic assessment rubric of at least 10 qualities that must be present for a scripture translation to be considered good. These ten qualities are then defined and a measurement for testing them is created, usually in the form of a question. The translation team is guided through this process and the rubric is written down as a guide which will help translators to assess their quality as they go. Thus, the draft is being tested by the same objectivce criteria from the very start of the project. For steps to complete this process, and sample rubrics go to v-raft.com.
+
+
 
-### Translation Checking Manual
-
-This manual describes how to check translated biblical content for accuracy, clarity, and naturalness.
 
 
-The manual begins with instructions for checking the translation that the translation team will use to check each other's work. If they follow these instructions, they will complete checking level one. Then there are instructions for the translation team to use for checking the translation with the language community for clarity and naturalness, and for church leaders to use when they check the translation for accuracy. If they follow these instructions, they will complete checking level two. This manual also contains instructions for the leaders of church networks to use for checking the translation for accuracy at level three.
 
 
-The manual also includes further instructions for checking the translation that the leaders of church networks can use to check the translation. Because many leaders of church networks do not speak the language of the translation, there are also instructions for creating a back translation, which allows people to check a translation in a language that they do not speak.

checking/intro-check/sub-title.md

@@ -1 +1 @@
-What is the Checking Manual?
+What is Authentic Assessment and how does it apply to quality assurance?

checking/intro-check/title.md

@@ -1 +1 @@
-Introduction to the Checking Manual
+Introduction to Authentic Assessment in checking Scripture

checking/intro-checking/01.md

@@ -1,30 +1,14 @@
 
-### Translation Checking
 
-#### Introduction
+As part of the translation process, it is necessary that several people check the translation to make sure that it is clearly communicating the message that it should communicate. A beginning translator who was told that he needed to have his translation checked, once said, "But I speak my native language perfectly. The translation is for that language. What more is needed?" There are two specific thigs to keep in mind in answer to that question.
 
-As part of the translation process, it is necessary that several people check the translation to make sure that it is clearly communicating the message that it should communicate. A beginning translator who was told to check his translation once said, "But I speak my native language perfectly. The translation is for that language. What more is needed?" What he said was true, but there are two more things to keep in mind.
+One thing is that he may not have understood the source text correctly; someone else who knows the source language better may know what it should say and can help to correct the translation.  Or it could be that he did not understand something about what the Bible meant to communicate at a certain place. In this case, someone who knows the Bible well, such as a Bible teacher or a Bible translation checker, can clarify th emeaning of the passage and help the translator determine a more correct translation.
 
-One thing is that he may not have understood the source text correctly, and so someone who knows what it should say might be able to correct the translation. This could be because he did not correctly understand a phrase or expression in the source language. In this case, someone else who understands the source language well can correct the translation.
+The other thing is that, although the translator may know very well what the text should say, the way he translated it might mean something else to a different person. That is, another person might think that the translation is talking about something other than what the translator intended, or the person hearing or reading the translation might not understand what the translator was trying to say. That is why it is always necessary to check what someone else understands from the translation to improve both clarity and accuracy where needed. 
 
-Or it could be that he did not understand something about what the Bible meant to communicate at a certain place. In this case, someone who knows the Bible well, such as a Bible teacher or a Bible translation checker, can correct the translation.
+The checking process begins as soon as a draft has been completed. The MAST method includes four steps of checking, each providing opportunity for additional individuals to participate. When the eight steps of MAST have been completed properly, the translation is considered to be level 1 checked. 
 
-The other thing is that, although the translator may know very well what the text should say, the way he translated it might mean something else to a different person. That is, another person might think that the translation is talking about something other than what the translator intended, or the person hearing or reading the translation might not understand what the translator was trying to say. That is why it is always necessary to check what someone else understands from the translation so that we can make it more accurate and more clear.
+Two additional levels of checking allow for more exposure to a broader group within the language community. These are not to be viewed as hierarchial but rather spherical--the levels expand the number of eyes that have assessed the translation. 
 
-This is a guide to the process of checking, in the form of a scale with three levels.
-
-This checking scale helps to show the extent to which the accuracy and clarity of a translation have been verified. These checking levels have been developed by the unfoldingWord project (see https://unfoldingword.bible ), the same group that manages Door43 with the help of many volunteers, and they are used to indicate the checking level of all biblical content on Door43.
-
-#### The Checking Levels
-
-There are three checking levels:
-
-* [Checking Level One - Affirmation by Translation Team](../level1/01.md)
-* [Checking Level Two - Affirmation by Community](../level2/01.md)
-* [Checking Level Three - Affirmation by Church Leadership](../level3/01.md).
-
-Any translation that has not yet been checked to Level One is considered to have not been checked and is assigned no checking status.
-
-The purpose of having several Checking Levels is to make translated materials quickly available to the church, while also allowing the content to continue to be checked and corroborated in an open environment. At all times, the degree to which its accuracy has been checked will be clearly indicated. We believe this will result in a faster checking process, allow broad church participation and ownership, and produce better translations.
 
 *Credits: Quotation used by permission, © 2013, SIL International, Sharing Our Native Culture, p. 69.*

checking/intro-levels/01.md

@@ -3,21 +3,21 @@
 
 Here are some important tips to remember when working with Checking Levels:
 
-* Only translations that have reached Checking Level One or higher will be made available on the unfoldingWord website and the unfoldingWord mobile app. (see http://ufw.io/content/)
-* Only translations that have reached Checking Level Three will be approved as source texts for other translations.
-* When a checking level has been completed and all appropriate edits have been made to the translation on door43, the checkers will inform unfoldingWord of the details of the check, including who did the checking and their title or qualifications as a translation checker. unfoldingWord will then harvest a copy of what is on door43, digitally publish a static copy of it on the unfoldingWord website (see https://unfoldingword.bible ) and make it available on the unfoldingWord mobile app. A print-ready PDF will also be produced and made available for download. It will continue to be possible to change the checked version on door43, allowing for future checking and editing.
-* For *Open Bible Stories* projects: Only *Open Bible Stories* translations that have been made from version 3.0 or higher of the English source text are eligible to be checked to Level One (or higher). Translations made from versions before 3.0 must be updated before proceeding with Checking Levels. (see [Source Texts and Version Numbers](../../translate/translate-source-version/01.md))
+* Only translations that have reached Checking Level One or higher will be made available on the unfoldingWord website and the unfoldingWord mobile app. 
+* Only scripture translations that have reached Checking Level Three will be approved as source texts for other translations.
+* The levels are designed to expand the sphere of people who have the opportunity to check the quality of the translation. 
+
 
 ### The Checking Levels
 
-The strategy for quality assurance of unfoldingWord content, including *Open Bible Stories*, is described briefly here and in detail at http://ufw.io/qa/.
+The three checking levels are as follows:
 
-The three-level checking scale we use is dependent on the unfoldingWord [Translation Guidelines](../../intro/translation-guidelines/01.md). All translated content is compared against the theology of the Statement of Faith and against the procedures and methodologies of the Translation Guidelines. With these documents forming the foundation, these are the three levels of checking used in the unfoldingWord project:
+* Checking level one: approved by the translation team. 
+* Checking level two: approved by the leaders of a local church and the christian community.
+* Checking level three: approved by the leaders of multiple local churches, a network of churches, or multiple evangelical denominations.
 
-* [Checking Level One - Affirmation by Translation Team](../level1/01.md)
-* [Checking Level Two - Affirmation by Community](../level2/01.md)
-* [Checking Level Three - Affirmation by Church Leadership](../level3/01.md)
+During a MAST workshop the translators engage in the checking steps (step 5-8) as a team. This platform assures that the individual's work is edited by other members. Additionally, these steps give team members the responsibility of working together to agree on and affirm the final prodect. Once this is done, level one has been achieved. 
 
-### Checking the Checkers
+Once level one has been achieived, the team is encourageed to print or otherwise publish their translation so that it can be immediately useful. At this time they are also invited to upload their translation to the Wycliffe Associates content server. This provides for the next two checking levels. When the translation has been tested by church leaders and other Christian members of the community it is considered to have reached level two. Finally, some translation teams may wish to have their work tested and approved by a network of denominational leaders and scholars. If this is achieived the translation is considered to have reached a level three. 
 
-The process and checking framework described in this document depends on an ongoing process of checking and revising content, as determined by the Church that uses the content. Feedback loops are encouraged (and modeled in translation software, where feasible) with a view to maximizing input from the greatest number of users of the content. The translations of the content are made available on the translation platform (see http://door43.org ), which is designed to make it easy for users to collaboratively create content that increases in quality over time.
+Once the translation has reached level one, the translation team and church leaders will determine what further checking and subsequent levels should be reached. The levels as explained in this manuel are a guide for affirming quality and expanding the exposure of a new translation. 

checking/level1/01.md

@@ -1,22 +1,17 @@
 
 ### Checking Level One – Translation Team Check
 
-Level One checking will be done primarily by the translation team, with some help from others in the language community. The translator or translation team should check their translation before they translate very many stories or chapters of the Bible, so that they can correct mistakes as early as possible in the translation process. Many of the steps in this process will need to be done several times before the translation is finished.
+Level One checking will be done primarily by the translation team; it can also include help from others in the language community. The translator or translation team should check their translation often (usually as soon as a whole chapter is drafted) so that they can correct mistakes as early as possible in the translation process. Sometimes a step will have to be repeated before moving on to the next step. 
 
-For the purposes of the unfoldingWord project, translations of Bible texts and biblical content are able to be published after they reach Checking Level One. This enables the broadest reach of the content as an active project, with an open invitation to others in the language community (implied or direct) to help improve the translation.
+Translations of Bible texts and biblical content are able to be published after they reach Checking Level One. This enables the broadest reach of the content as an active project, with an open invitation to others in the language community (implied or direct) to help improve the translation.
 
-### Steps for checking under Level One:
+### Steps for level one checking:
 
 These are the steps that the translation team must follow in order to achieve Checking Level One:
 
-1. **Contact.**  Make contact with at least one element of the unfoldingWord network, notifying unfoldingWord that you intend to begin translation. To get information about how to do that, see [Finding Answers](../../intro/finding-answers/01.md)
-1. **Review.**  Review the [Translation Guidelines](../../intro/translation-guidelines/01.md).
-1. **Agree.**  Agree that the Statement of Faith is an accurate reflection of your own beliefs and that you intend to translate the content in harmony with it and also in accordance with the Translation Guidelines by signing the form. (see http://ufw.io/forms/)
-1. **Draft.**  Make a draft translation of some portions of the text. For instructions on how to make a draft translation, see [First Draft](../../translate/first-draft/01.md)
-1. **Self Check**. For instructions on how to do a Self Check of your draft translation, see [Self Check](../self-check/01.md).
-1. **Peer Check**. For instructions on how to do a Peer Check of your draft translation, see [Peer Check](../peer-check/01.md).
-1. **translationWord Check**. For instructions on how to do an translationWord Check of your draft translation, see [translationWord Check](../important-term-check/01.md).
-1. **Accuracy Check**. For instructions on how to do an Accuracy Check of your draft translation, see [Accuracy Check](../accuracy-check/01.md).
-1. **Affirmation**. Affirm that you, as a translation team or individual, have made full use of the translationNotes, the definitions of translationWords, and the other exegetical and translation checking resources in the translation process, and that you have followed the steps for checking under Level One.
+1. Once a portion has been drafted, the translator of that section will perform a self-edit, using the source text, and other available tools to check the draft. 
+2. When the translator has completed the self-edit, another translator on the team will perform a peer edit, carefuly comparing the translated text to the source text and using any other available tools to confirm the accuracy and meaningfulness of the translation. He may also provide feedback and comments on spelling, naturalness and flow. The person conducting the peer edit does not have authority to make changes; his role is to provide feedback and suggestions to the translator of the draft who then makes changes as he deems necessary. 
+3. The keywords of the passage or systematically checked against the list of key words in the available tool designed specifically to support this checking step. Alternatively, the translation team can create their own list of key words--abstract spiritual terms, historical and geographical terms and names--and carefully compare their drafted text to that list. This step is typically done by the translator and at least one other member of the translation team. 
+4. Each verse is carefully checked comparing the drafted text to the original source text, looking for any missing portions or added material. This check is typically done with the translator of the passage and at least one other member of the translation team--preferably a different member than assisted in the keyword check. 
 
-(For instructions on how to affirm completion of Level One, see [Level 1 Affirmation](../level1-affirm/01.md).)
+When these steps have been completed,  edits have been incorporated into the translated portion, and the translation team is collectively satisifed with the product, it is considered level one checked. At this point, if the translation team desires to do so, they are invited to upload the translation to the Wycliffe Associates content server. It can then be published to bibleineverylanguage.org to reach a broader community. 

checking/level2/01.md

@@ -1,11 +1,16 @@
 
 ### Checking Level Two - External Check
 
-The purpose of Level Two checking is to verify that representative groups from the local language community agree that the translation is a good one.
+The purpose of Level Two checking is to engage representative groups from the local language community to assess the quality of the translating and contribute to its improvement where needed. 
 
-Level Two checking will be done in two ways:
+### Level two Checking
+
+The level two check focuses on pastors and the Christian community within the target language. Once the translation team has reached level one with its translation, the translation is ready to be shared outside the team for further review. Ideally, a leader on the translation team will work with local pastors and Christians to check the scripture's clarity and naturalness. 
+
+The translator or leader will read (if it is a written translation) a portion of the translation to the gathered listeners. Before reading, he should tell the people listening  to stop him if they hear something that does not sound natural. Alternatively, if the people are literate, each one in the group can be asked to read a passage of the newly translated material. It is best, even if everyone in the group is literate, to have the portions read out loud to the whole group. Portions should not be too long (this is subjective to the abilities of the group, and type of passage). It's also very important for  listeners to understand that they are now a part of the team helping to improve and affirm the quality of the scripture. They, themselves are not being tested. Rather the questions are designed to help them provide feedback on the meaningfulness of the new translation. 
+
+These tools have been created to assist teams in checking and are recommending for use during this level--translation questions, translation notes, and the reviewer's guide.  They are available on bibleineverylanguage.org. Additionally, the translation questions and translation notes are embedded in tStudio. During the MAST workshop, the translation team was asked to develop a rubric for testing and affirming the quality of their work. More information on this strategy is available at v-raft.org. This rubric will help the team determine which tools and methods to apply to the level two check within their community. 
+
+Key elements of this level of checking are:  pastors AND Christians in the community have read (or listened to) the translated scriptures and contributed to their improvement, the above listed tools have been employed for ensuring accuracy and completeness, the translation team has been  responsible to respond to feedback and implement changes in the translation where needed. When this has been done, the translation is considered to be at level two. 
 
-1. **Language Community Check**. The translation will be checked by members of the language community to make sure that it is clear, natural, and understandable. For the steps to follow to do the Language Community Check, see [Language Community Check](../language-community-check/01.md).
-1. **Church Leader Check**. The translation will be checked by a group of church leaders from the language community to make sure that it is accurate. For the steps to follow to do the Church Leader Check, see [Church Leader Check](../church-leader-check/01.md).
 
-Once this has been done, this work needs to be affirmed (see [Level 2 Affirmation](../good/01.md)).

checking/level3-questions/01.md

@@ -5,7 +5,7 @@ These are the questions for the Level Three checkers to keep in mind as they rea
 
 You can answer these questions after you read portions of the translation or as you come across problems in the text. If you answer "no" to any of these questions in the first group, please explain in more detail, include the specific passage that you feel is not right, and give your recommendation for how the translation team should correct it.
 
-Keep in mind that the goal of the translation team is to express the meaning of the source text in a natural and clear way in the target language. This means that they may have needed to change the order of some clauses and that they had to represent many single words in the source language with multiple words in the target language. These things are not considered to be problems in Other Language (OL) translations. The only times that translators should avoid making these changes is for Gateway Language (GL) translations of the ULT and UST. The purpose of the ULT is to show the OL translator how the original biblical languages expressed the meaning, and the purpose of the UST is to express that same meaning in simple, clear forms, even though it might be more natural to use an idiom in the OL. GL translators need to remember those guidelines. But for OL translations, the goal is always to be natural and clear.
+Keep in mind that the goal of the translation team is to express the meaning of the source text in a natural and clear way in the target language. This means that they may have needed to change the order of some clauses and that they had to represent many single words in the source language with multiple words in the target language. These things are not considered to be problems in Other Language (OL) translations. The only times that translators should avoid making these changes is for Gateway Language (GL) translations of the ULB and UDB. The purpose of the ULB is to show the OL translator how the original biblical languages expressed the meaning, and the purpose of the UDB is to express that same meaning in simple, clear forms, even though it might be more natural to use an idiom in the OL. GL translators need to remember those guidelines. But for OL translations, the goal is always to be natural and clear.
 
 Also keep in mind that the translators may have included information that the original audience would have understood from the original message, but that the original author did not state explicitly. When this information is necessary for the target audience to understand the text, it is good to include it explicitly. For more about this, see [Implicit and Explicit Information](../../translate/figs-explicit/01.md).
 

checking/level3/01.md

@@ -1,12 +1,10 @@
 
-### Checking Level Three - Authenticated Check
+### Checking Level Three 
 
-Level Three checking will be done by groups or organizations that are recognized by the churches in a language community. The leaders from these groups will verify that they approve of the distribution and use of the translation among the people affiliated with them. This approval is not required for distribution of the translation, but rather serves to validate it.
+Level Three checking will be done by groups or organizations that are recognized by the churches in a language community. The leaders from these groups will verify that they approve the translation. This approval is not required for distribution of the translation, but rather serves to validate it.
 
-Those who do Level Three checking need to be other than the people who did Level Two checking.
+Participants in this level of checking need to be different from the ones who participated in level two. Each level is an expansion of exposure, and this is most significant in affirming the quality as well as noting any needed improvements. 
 
 The intent of this level is to affirm the alignment of the translation with the intent of the original texts and the sound doctrine of the Church historic and universal, through the review and affirmation by the leadership of the Church that speaks the language. Level 3 is thus achieved by the mutual agreement of the leadership of multiple church networks. The Church networks should be representative of the churches in the language community. Those checking the translation should be first-language speakers of the language, and those signing off on the check are those in leadership roles in the Church networks. A leader of a Church network who is also a first-language speaker of the language of the translation could both check the translation and sign off on its quality.
 
-Level 3 is completed when the translation has been thoroughly checked and approved by the leadership (or their delegates) of at least two church networks that have personnel trained in biblical languages and content.
-
-To proceed with Level Three checking, go to [Questions for Checking on Level Three](../level3-questions/01.md).
+Level 3 is completed when the translation has been thoroughly checked and approved by the leadership (or their delegates) of at least two church networks. At this level, those who are participating in the check should (when possible) be trained/ordained through the church network and should therefore use every aspect of their own knowledge and training tools to check the scriptures. Addtionally, translation notes, translation words, translation questions, and the Reviewer's Guide--tools that are freely accessible on Bibleineverylanguage.org--are ideal for using at this level of checking. A translator, as designated by the translation team, should work with these checkers. If any areas of correction are recommended, the translator will take these concerns and recommended changes to the translation team to decide how to best improve the translation and what edits need to be made. Once the translation team has addressed suggestions to the satisfaction of the checking team, the scripture is considered to be checked to level three. 

checking/other-methods/01.md

@@ -3,7 +3,7 @@
 
 As well as asking questions, there are other checking methods that you may also use to ensure that the translation is easy to read and sounds natural to the listeners. Here are some other methods that you may like to try:
 
-* **Retell Method**:  You, the translator or tester, can read a few verses and ask someone else to retell what was said. This helps to check the clarity and naturalness of the translation and offers alternate ways of saying the same thing.
+* **Retell Method**: You, the translator or tester, can read a few verses and ask someone else to retell what was said. This helps to check the clarity and naturalness of the translation and offers alternate ways of saying the same thing.
 
 * **Reading Method**: Someone other than you, the translator or tester, should read a portion of the translation while you take notes where the pauses and mistakes occur. This will show how easy or how difficult it is to read and understand the translation. Look at the places in the translation where the reader paused or made mistakes and consider what part of the translation was difficult. You may need to revise the translation at those points so that it is easier to read and understand.
 

checking/spelling/01.md

@@ -1,5 +1,5 @@
 
-In order for the reader to be able to read and understand the translation easily, it is important that you spell words consistently. This can be difficult if there is not a tradition of writing or spelling in the target language. Several people working on different parts of a translation also makes this difficult.  For that reason, it is important for the translation team to meet together before they start translating to talk about how they plan to spell words.
+In order for the reader to be able to read and understand the translation easily, it is important that you spell words consistently. This can be difficult if there is not a tradition of writing or spelling in the target language. Several people working on different parts of a translation also makes this difficult. For that reason, it is important for the translation team to meet together before they start translating to talk about how they plan to spell words.
 
 Discuss the words that are difficult to spell as a team. If the words have sounds in them that are difficult to represent, then you may need to make a change in the writing system that you are using (see [Alphabet/Orthography](../../translate/translate-alphabet/01.md)). If the sounds in the words can be represented in different ways, then the team will need to agree on how to spell them. Make a list of the agreed upon spellings of these words in alphabetical order. Make sure that each member of the team has a copy of the list, to consult when translating. Add to the list as you come across more difficult words, but make sure everyone has the current list. It may be helpful to use a spreadsheet to maintain your spelling list.
 

checking/verses/01.md

@@ -5,7 +5,7 @@ It is important that your target language translation include all of the verses
 
 1. **Textual Variants** - There are some verses that many Bible scholars do not believe were original to the Bible, but were added later. Therefore the translators of some Bibles chose to not include those verses, or included them only as footnotes. (For more information about this, see [Textual Variants](../../translate/translate-textvariants/01.md).) Your translation team will need to decide whether you will include these verses or not.
 1. **Different Numbering** - Some Bibles use a different system of verse numbering than other Bibles. (For more information about this, see [Chapter and Verse Numbers](../../translate/translate-chapverse/01.md).) Your translation team will need to decide which system to use.
-1. **Verse Bridges** - In some translations of the Bible, the contents of two or more verses are rearranged so that the order of information is more logical or easier to understand. When that happens, the verse numbers are combined, such as 4-5 or 4-6. The UST does this sometimes, and on rare occasions, also the ULT. Because not all of the verse numbers appear or they do not appear where you expect them to be, it might look like some verses are missing. But the contents of those verses are there. (For more information about this, see [Verse Bridges](../../translate/translate-versebridge/01.md).) Your translation team will need to decide whether to use verse bridges or not.
+1. **Verse Bridges** - In some translations of the Bible, the contents of two or more verses are rearranged so that the order of information is more logical or easier to understand. When that happens, the verse numbers are combined, such as 4-5 or 4-6. The UDB does this sometimes, and on rare occasions, also the ULB. Because not all of the verse numbers appear or they do not appear where you expect them to be, it might look like some verses are missing. But the contents of those verses are there. (For more information about this, see [Verse Bridges](../../translate/translate-versebridge/01.md).) Your translation team will need to decide whether to use verse bridges or not.
 
 ### Checking for Missing Verses
 

checking/vol2-backtranslation-guidelines/01.md

@@ -21,7 +21,7 @@ The back translator should use the same punctuation in the back translation as t
 
 #### e. Express the full meaning of complex words
 
-Sometimes words in the target language will be more complex than words in the language of wider communication. In this case, the back translator will need to represent the target language word with a longer phrase in the language of wider communication. This is necessary so that the translation checker can see as much of the meaning as possible. For example, to translate one word in the target language it might be necessary to use a phrase in the language of wider communication such as, "go up," or "be lying down."   Also, many languages have words that contain more information than the equivalent words in the language of wider communication. In this case, it is most helpful if the back translator includes that additional information in parentheses, such as "we (inclusive)," or "you (feminine, plural)."
+Sometimes words in the target language will be more complex than words in the language of wider communication. In this case, the back translator will need to represent the target language word with a longer phrase in the language of wider communication. This is necessary so that the translation checker can see as much of the meaning as possible. For example, to translate one word in the target language it might be necessary to use a phrase in the language of wider communication such as, "go up," or "be lying down."  Also, many languages have words that contain more information than the equivalent words in the language of wider communication. In this case, it is most helpful if the back translator includes that additional information in parentheses, such as "we (inclusive)," or "you (feminine, plural)."
 
 ### 2. Use the Language of Wider Communication Style for Sentence and Logical Structure
 

checking/vol2-backtranslation-purpose/01.md

@@ -1,7 +1,7 @@
 
 ### Why is a back translation necessary?
 
-The purpose of a back translation is to allow a consultant or checker of biblical material who does not understand the target language to be able to see what is in the target language translation, even though he or she does not understand the target language. Therefore, the language of the back translation needs to be a language that both the person doing the back translation (the back translator) and the checker understand well.  Often this means that the back translator will need to translate the target language text back into the same language of wider communication that was used for the source text.
+The purpose of a back translation is to allow a consultant or checker of biblical material who does not understand the target language to be able to see what is in the target language translation, even though he or she does not understand the target language. Therefore, the language of the back translation needs to be a language that both the person doing the back translation (the back translator) and the checker understand well. Often this means that the back translator will need to translate the target language text back into the same language of wider communication that was used for the source text.
 
 Some people might consider this to be unnecessary, since the biblical text already exists in the source language. But remember the purpose of the back translation: it is to allow the checker to see what is in the target language translation. Just reading the original source language text does not allow the checker to see what is in the target language translation. Therefore, the back translator must make a new translation back into the language of wider communication that is based only on the target language translation. For this reason, the back translator *cannot* look at the source language text when doing his back translation, but *only* at the target language text. In this way, the checker can identify any problems that might exist in the target language translation and work with the translator to fix those problems.
 

checking/vol2-intro/01.md

@@ -3,4 +3,4 @@ We have seen where the translation team will do a lot of checking of their own t
 
 For Level Two and Level Three, the translation team needs to bring their work to members of the language community and to the church leaders. This is necessary because the translation team is very close to and involved in their work, and so they sometimes do not see mistakes that others can see more easily. Other speakers of the language can suggest better ways of saying things that the translation team may not have thought of. Sometimes the translation team makes the translation sound strange because they are following the words of the source language too closely. Other speakers of the language can help them fix that. Also, the translation team may lack some of the expertise or knowledge of the Bible that others have, and so there may be some mistakes that others can correct for them. For these reasons, people that are not part of the translation team need to check the translation.
 
-The rest of this manual will  go over the guidelines that the church leaders can use to guide them in checking the translation for both Level Two and Level Three.
+The rest of this manual will go over the guidelines that the church leaders can use to guide them in checking the translation for both Level Two and Level Three.

checking/vol2-steps/01.md

@@ -5,14 +5,14 @@
 
 1. Find out ahead of time which set of stories or which Bible passage you will be checking.
 1. Read the passage in several versions in any languages you understand, including the original languages, if possible.
-1. Read the passage in the ULT and UST, and read the Notes and translationWords.
+1. Read the passage in the ULB and UDB, and read the Notes and translationWords.
 1. Make note of any parts that you think might be difficult to translate.
 1. Research these passages in translation helps and commentaries, making notes about what you discover.
 
 #### While Checking
 
 1. **Ask Questions**. When you see something that you think might be a problem in the translation, do not make a statement to the translator that there is a problem in the translation. If you do not speak the target language, then you do not know if there is a problem or not. You only suspect that there could be a problem. Even if you do speak the target language, it is more polite to ask a question than to make a statement that something is wrong. You could ask something like, "What would you think about saying it this way?" and then suggest an alternative way to translate it. Then together you can discuss the different translation ideas, and you can give reasons why you think one translation alternative might be better than another. Then, after considering the alternatives, the translator or translation team must decide which way is best.
-1. **Explore the target language and culture**.  The questions that you ask will be to discover what the phrase means in the target language. The best questions are the ones that help the translator to think about what the phrase means and how it is used. Useful questions are, "In what situations is this phrase used in your language?" or "Who usually says things like this, and why do they say it?" It is also useful to help the translator to think about what a person from his village would say if in the same situation as the person in the Bible.
+1. **Explore the target language and culture**. The questions that you ask will be to discover what the phrase means in the target language. The best questions are the ones that help the translator to think about what the phrase means and how it is used. Useful questions are, "In what situations is this phrase used in your language?" or "Who usually says things like this, and why do they say it?" It is also useful to help the translator to think about what a person from his village would say if in the same situation as the person in the Bible.
 1. **Teach the translator**. After you explore the meaning of a phrase in the target language and culture, you can tell the translator what the phrase means in the source language and culture. Then together you can decide if the phrase in the translation or the phrase he has just thought of has that same meaning or not.
 
 #### Checking the Translation Directly

checking/vol2-things-to-check/01.md

@@ -1,7 +1,6 @@
 
 ### Types of things to check
 
-
 1. Ask about anything that does not seem right to you, so that the translation team can explain it. If it also does not seem right to them, they can adjust the translation. In general:
 
     1. Check for anything that appears to be added, that was not a part of the meaning of the source text. (Remember, the original meaning also includes [Implicit Information](../../translate/figs-explicit/01.md).)

intro/finding-answers/01.md

@@ -1,15 +1,11 @@
 
-### How to Get Answers
-
 There are several resources available for finding answers to questions:
 
-* **translationAcademy** - This training manual is available at http://ufw.io/ta and has much information including:
-  * [Introduction](../ta-intro/01.md) - introduces the unfoldingWord project
-  * [Process Manual](../../process/process-manual/01.md)  - answers the question "what next?"
+* **Translation Manual** - This training manual is available [here](https://door43.org/u/WycliffeAssociates/en_ta/248d51ac0d/) and has much information including:
+  * [Introduction](https://door43.org/u/WycliffeAssociates/en_ta/248d51ac0d/#ta-intro) - introduces the information about  project
+  * [Process Manual](../../process/process-manual/01.md) - answers the question "what do I do to take a translation from start to finish?"
   * [Translation Manual](../../translate/translate-manual/01.md) - explains the basics of translation theory and practical translation helps
-  * [Checking Manual](../../checking/intro-check/01.md) - explains the basics of checking theory and best practices
-* **Slack Chatroom** - Join the Team43 community, post your questions to the "#helpdesk" channel, and get real-time answers to your questions (sign up at http://ufw.io/team43)
-* **CCBT Discussion Forum** - A place to ask questions and get answers to technical, strategic, translation, and checking issues, https://forum.ccbt.bible/
-* **Helpdesk** - email <help@door43.org> with your questions
+  * [Checking Manual](../../checking/intro-check/01.md) - explains the basics of MAST checking theory
 
+* **Helpdesk** - email <helpdesk@techadvancement.com> with your questions
 

intro/finding-answers/title.md

@@ -1 +1 @@
-Finding Answers
+Hot to Get Answers

intro/gl-strategy/01.md

@@ -1,6 +1,3 @@
-
-*The official version of this document is found at http://ufw.io/gl/.*
-
 ### Explanation
 
 The objective of the gateway languages strategy is to equip 100% of the people groups that comprise the global Church with biblical content that is released from copyright restrictions and made available in a language they understand well (a language of wider communication) together with unrestricted translation training and tools that enable them to translate it into a language they understand fully (their own language). A "gateway language" is a language of wider communication through which second-language speakers of that language can gain access to content and translate it into their own language.