Deleted this link because we archived the page. We don't do Version numbers
* **[Source Texts and Version Numbers](../translate-source-version/01.md)** - Is the text the latest, most updated version?
Issue 186 Moved ”The Importance of Form” and ”Levels of Meaning” into a folder called ”More about Form and Meaning” and it put this folder after ”Meaning-Based Translations”
Issue 186 Moved ”The Importance of Form” and ”Levels of Meaning” into a folder called ”More about Form and Meaning” and it put this folder after ”Meaning-Based Translations”
Issue 186 Moved "Form and Meaning" to after "Literal Translations" and "Meaning-based Translations", because goes into the issues more deeply. Changed name to "More about Form and Meaning"
Updated explanation of GL and OL to fit with what is on "Terms to Know"
(My old explanation implied that all target languages are OLs, but that's not right. The OLs are just the target langs that will have only the Bible and Biblical content -- not the translation resources.))
Issue 188 - Add The Unlocked Bibles to introduce ULB and UDB
Issue 189 - translate-formatsignals - named "A few Punctuation Marks in the Bible" and moved to Decisions.
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189: Reordered. Main sections are Introduction, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, Translation Resources, Decisions for Writing Your Language, Presentation of Translation, File Formats
Issue 189 Made this the order of the main sections: Intro, Defining a Good Translation, Before Translating, About the Bible, Types of Translation, The Translation Process, Translation Resources, Decisions for Writing your Language, Presentation of Translation, File Formats.
Issue 143
It talked about reaching or achieving checking levels. I changed it to be about using certain level checks to reach/achieve certain affirmation levels.
Deleted en_ta/translate files: choose-team, file-formats, level1, first-draft, translate/guidelines, mast, qualifications, resources, translate/translate, writing-decisions.
Moved biblicalimagery and bita to the top of the page.
Deleted because the content of en_ta/archive/checking/intro-check/01.md was put at the beginning of en_ta/checking/authentic-assessment/01.md
- title: "Authentic Assessment in Checking Scripture"
link: intro-check
Deleted the title "How to Start Translating." It was just a title (with no md files) and I had moved the "Help with Translating" to another part of the toc.
Issue 116 Finding Answers - Translation Manual sections. Deleted the info telling about what's in the Translation Manual because it is a duplicate of intro/ta-intro/01.md.
Put in info about BIEL.
Trying Links. These links work in DCS.
Now I'll change them to the format used in the rest of tA, so that eventually, they will work in the Interleaved pdfs.
In Strategies Applied for "Connecting Words,"
I put 4 spaces before each ULB,
6 spaces before each explanation in italics,
6 spaces before each strategy applied.
I want to see how it shows up in the Interleaved pdfs.
Changed links to Dead Metaphor and Metaphor parts so that they link to the folder rather than to the main page.
There are no links in tN to these two tA pages. Check the Matt pdf to see if they link. now that these are full links. If not, then it could be that the only way tA pages get into the pdf is if there is link for them in tN.
Deleted links to tW pages for "dreams" and "visions." The translators using this page won't need them. (Although they could be helpful for gateway language translators who will be translating this page.)
I deleted this from the Description section.
Here are two examples of elliptical sentences whose missing words are understood by convention. English speakers normally use the shorter forms.
* "Fire when ready" means "Fire when <u>you are</u> ready."
* "Back to the drawing board" means "<u>We need to go</u> back to the drawing board."
Here are three examples of elliptical sentences whose missing words were already used in a previous phrase.
* "I drank water, and Bob milk" means "I drank water, and Bob <u>drank</u> milk.
* "I drank water, not milk" means "I drank water; <u>I did</u> not <u>drink</u> milk.
* "I drank water, and Tom did, too" means "I drank water, and Tom <u>drank water</u>, too."
I had this information (worded differently) explaining each of the Examples of Translation Strategies Applied, but thought it may have been too cluttered. Maybe it's adequate without them.
* Starting a sentence with someone's name when he has not been introduced yet might be confusing in some languages.
* When pronouns occur in the first sentence of a chapter, readers might wonder whom they refer to.
* In some languages after the author identifies the main person in a story, he will often refer to that person with simply a pronoun.
Exchanged the rhyming translation below with an adaptation of Psalm 1:1-2 from the Scottish Psalter of 1650, which is in the public domain.
* Happy is the person not encouraged <u>to sin</u><br/>
Disrespect for God he will not <u>begin</u>.<br/>
To those who laugh at God, he is <u>no kin</u><br/>
God is his constant <u>delight</u>.<br/>
He does what God says <u>is right</u>.<br/>
He thinks of it all day <u>and night</u>.
Deleted some examples.
><u>Then</u> Jesus came from Galilee to the Jordan River to be baptized by John. (Matthew 3:13 ULB)
The word "then" shows that Jesus came to the Jordan River some time after the events in the previous verses.
Deleted these definitions at the beginning:
* **Assumed knowledge** is whatever a speaker assumes his audience knows before he speaks and gives them some kind of information. The speaker gives the audience information in two ways:
* **Explicit information** is what the speaker states directly.
* **Implicit information** is what the speaker does not state directly because he expects his audience to be able to learn it from what he says.
Deleted example because it does not fit definition of being in one clause.
><u>Unless</u> these men stay in the ship, you <u>cannot</u> be saved. (Acts 27:31 ULB)
Paul was telling them that they could be saved only if the men who were trying to leave the ship stayed in the ship.
Many of the Translation Topics have links to other parts of the Translation Manual. However only the topics that are addressed in either the Translation Notes or the Translation Words in this Translation Helps volume are included in this volume. Because of that, some of the links to other parts of the Translation Manual do not work. If you want to read those other parts of the Translation Manual, you can see them on Bible in Every Language at (https://door43.org/u/WycliffeAssociates/en_ta/). The links that do not work are black, and those that work are some other color.
## How to use the Translation Topics
You can find topics in the Table of Contents at the beginning of this Translation Helps manual, or you can click on the links to topics in the Translation Notes or Translation Words.
Many of the topics have the following format.
* Description - Use this to learn about the topic.
* Reasons This is a Translation Issue - Use this to understand the translation issue.
* Examples from the Bible - Use this to understand the topic better.
* Translation Strategies - Use this to get ideas for how to translate a passage if the way it is communicated in the Unlocked Literal Bible would not be helpful in your language.
* Examples of Translation Strategies Applied - Use this to see ways each of the strategies might be applied to a passage in the Bible. The bold text is the ULB and the text below it is an exmple of the strategy applied. Sometimes there is also some explanation with an example.
A box next to the description tells what question the page answers. It may also have links to other pages to read in order to understand the topic better. These links will not work if their pages are not also in this Translation Helps manual.
## Contributors to the Translation Topics
- Christine Jarka, MSEd in Instructional Design
- Henry Whitney, BA in Education
- James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
The Translation Manual is an open sourced manual on Bible translation. It teaches the basics of translation theory and a process for doing Bible translation, it provides practical helps for dealing with various translation issues, and it provides instruction and processes for checking translations.
The Translation Manual is intended to empower anyone, anywhere to equip themselves for createing high-quality translations of biblical content into their own language. The manual is designed to be highly flexible. It can be used in a systematic, in-advance approach or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
The Translation Manual is written primarily for mother-tongue Bible translators who have had little or no prior training in translation. The English version of the manual is primarily for people who speak English as a second language. Because of this we have tried to keep the writing style easy to understand.
### Contributors
- Susan Quigley, MA in Linguistics
- Henry Whitney, BA in Education
- Tabitha Price, BA in Education
- James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
The Translation Manual is written primarily for mother-tongue Bible translators who have had little or no prior training in translation. The English version of the manual is primarily for people who speak English as a second language. Because of this we have tried to keep the writing style easy to understand. **(Not sure whether or not to include this. It seems we could say the same thing for all the helps.)**
## How to use the Translation Manual
The translation
## Contributors to the Translation Manual
- Christine Jarka, MSEd in Instructional Design
- Henry Whitney, BA in Education
- James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages
"Translation Topics" is a part of the the Wycliffe Associates Translation Manual. It deals with translation issues that arise because of grammar, discourse, figures of speech, and ideas that maybe unknown to speakers of the target language. It also deals with issues that are particularly relevant to Bible translation.
The complete Translation Manual is available at BibleInEveryLanguage.org. The topics that are included in this set of Translation Resources are ones that are addressed in either the Translation Notes or the Translation Words for this book of the Bible.
Many of the topics include examples from the Bible, strategies for dealing with the issues, and examples of how those strategies might be applied.
To read or print the Wycliffe Associates Translation Manual, see the Translation Manual project on Bible in Every Language (https://door43.org/u/WycliffeAssociates/en_ta/).
## 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.
@ -25,3 +24,4 @@ The licensor cannot revoke these freedoms as long as you follow the license term
You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
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.
Translation Manual is intended to enable anyone, anywhere to equip themselves so that they will be able to make high-quality translations of biblical content into their own language. Translation Manual is designed to be highly flexible. It can be used in a systematic, in-advance approach or it can be used for just-in-time learning (or both, as needed). It is modular in structure.
## Downloading
Translation Manual was developed by the [Door43 World Missions Community](https://door43.org) in conjunction with [Wycliffe Associates](http://www.wycliffeassociates.org/). The entire project is made
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 Translation Manual to use, go here: https://unfoldingword.org/academy/. It is also included in [tS](http://ufw.io/ts) and [tC](http://ufw.io/tc).
If you want to 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 Translation Manual is a collaborative work between several organzations. We seek those that would like to contribute to the work. Presently there is an Oversight Team that is responsible for the maintenance of the content. The members of this team represent various organizations and are experienced Biblical Scholars, Linguists and Bible Translators.
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 Translation Manual please fork a copy of the repository, make your changes and then submit a Pull Request to the repository.
The Oversight Team will then review the pull request and then decide on the merging of the content into the master repository.
* `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 Translation Manual
__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.
See the [LICENSE](https://git.door43.org/unfoldingWord/en_ta/src/branch/master/LICENSE.md) file for licensing information.
@ -8,4 +8,5 @@ As you read the new translation, ask yourself these questions. These are questio
1. Does the translation use too many words that were borrowed from another language, or are these words acceptable to the language community?
1. Did the writer use an appropriate form of the language acceptable to the wider language community? (Is the writer familiar with the dialects of your language found throughout the area? Did the writer use a form of the language that all of the language community understands well, or did he use a form that is used in only a small area?
If there is a place where the translation uses language in the wrong style, make a note of that so that you can discuss it with the translation team.
If there is a place where the translation uses language in the wrong style, make a note of that so that you can discuss it with the translation team.
@ -17,7 +17,7 @@ The people doing the checking should follow these steps:
1. Each of the checkers should read the translation (or listen to the recording) by himself, comparing it to the original Bible passage or story in the language of wider communication. It can be helpful for the translator to read the translation out loud to the checker while the checker follows along looking at the source Bible or Bibles. As the checker reads (or listens to) the translation and compares it to the source, he should keep in mind these general questions:
* Does the translation add anything to the original meaning? (The original meaning also includes [Implicit Information](../../translate/figs-explicit/01.md).)
* Does the translation add anything to the original meaning? (The original meaning also includes [Implicit Information](../../jit/figs-explicit/01.md).)
* Is there any part of the meaning that is left out of the translation?
* Has the translation changed the meaning in any way?
@ -40,5 +40,5 @@ These questions can also be helpful for finding anything that might be inaccurat
* Were the people introduced in each story doing the same things as those mentioned in the source language translation? (Was it easy to see who was doing the events of the new translation when it was compared to the source language?)
* Are there translationWords used in the new translation that do not match your understanding of the words in the source version? Think about things like this: How do your people talk about a priest (one who sacrifices to God) or a temple (the sacrifice place of the Jews) without using a word borrowed from the source language?
* Are the phrases used in the new translation helpful in understanding the more difficult phrases of the source translation? (Are the phrases of the new translation put together in a way that brings better understanding and still fit with the meaning of the source language translation?)
* Another way to determine if the text is accurate is to ask comprehension questions about the translation, such as, "who did what, when, where, how, and why." There are questions that have already been prepared to help with this. (To view the translationQuestions go to http://ufw.io/tq/.) The answers to those questions should be the same as the answers to those questions about the source language translation. If they are not, there is a problem in the translation.
* Another way to determine if the text is accurate is to ask comprehension questions about the translation, such as, "who did what, when, where, how, and why." There are questions that have already been prepared to help with this. (To view the translationQuestions go to https://door43.org/u/WycliffeAssociates/en_tq.) The answers to those questions should be the same as the answers to those questions about the source language translation. If they are not, there is a problem in the translation.
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."
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."
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."
@ -7,4 +7,5 @@ As you read the translation, ask yourself these questions about the way words ar
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.
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.
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.
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.
@ -25,4 +25,5 @@ Please also answer the following questions. The answers to these questions will
<br>
<br>
The community leaders might want to add their own information to this or make a summary statement about how acceptable this translation is to the local community. This can be included as part of the Level Two Community Check Evaluation information. The wider church leadership will have access to this information, and it will help them validate the translation as approved by the local Christian community when they do the Level Two Church Check and also Level Three Checking.
The community leaders might want to add their own information to this or make a summary statement about how acceptable this translation is to the local community. This can be included as part of the Level Two Community Check Evaluation information. The wider church leadership will have access to this information, and it will help them validate the translation as approved by the local Christian community when they do the Level Two Church Check and also Level Three Checking.
@ -7,4 +7,5 @@ The purpose of this section is to make sure that the translation is complete. In
1. Does the translation include all the verses of the book that was translated? (When you look at the verse numbering of the source language translation, are all of the verses included in the target language translation?) Sometimes there are differences in verse numbering between translations. For example, in some translations some verses are grouped together or sometimes certain verses are put in footnotes. Even though there may be these kinds of differences between the source translation and the target translation, the target translation is still considered to be complete.
1. Are there places in the translation where something seems to be left out, or there seems to be a different message than is found in the source language translation? (The wording and the order can be different, but the language that the translator used should give the same message as the source language translation.)
If there is a place where the translation is not complete, make a note of that so that you can discuss it with the translation team.
If there is a place where the translation is not complete, make a note of that so that you can discuss it with the translation team.
The translation team's goal is to produce a translation that is accurate, natural, clear, and accepted by the church. This goal will likely require the partnership of different people, resources, and tools to accomplish. For this reason, the checkers play a very important role in helping the translation team accomplish their goal.
#### Accurate
The checkers who are pastors, church leaders, and leaders of church networks will help the translation team produce a translation that is accurate. They will do this by comparing the translation with the source language and, when possible, also with the original languages of the Bible. They are also encouraged to use the translation tools created specifically for checking and available at bibleineverylanguage.org.
#### Clear
The checkers who are members of the language community will help the translation team produce a translation that is clear. They will do this by listening to (or reading) the translation and pointing out (to the translators) the places where the translation is confusing or does not make sense to them. The translation team will work with these checkers to edit the work for clarity during checking level 2.
#### Natural
In the same way, checkers who are members of the language community will help the translation team produce a translation that is natural. The translataion team will work with them to edit for naturalness during checkign level two. (Translation notes, available at bibleineverylanguage.org is a tool that provides suggestions for handling meaning naturally in difficult passages.)
#### Church-approved
The checkers who are members of a church in the language community will help the translation team produce a translation that is approved and accepted by the church in that community. They will do this by working together with members and leaders of other churches from the language community, using the tools available at bibleineverylanguage.org as well as their own resources and other translations to carefully check the content of the newly translated scripture. When members and leaders that represent the churches of a language community work together and agree that the translation is good, then it will be accepted and used by the churches in that community.
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.
@ -5,7 +5,7 @@ After you, the translation team, have performed the checks listed under Level On
For this check you will read a section of the translation to members of the language community. Before you read the translation, tell the people listening that you want them to stop you if they hear something that is not natural in their language. (For more information on how to check a translation for naturalness, see [Natural Translation](../natural/01.md).)
There are a set of questions and answers for each *Open Bible Story* and for each chapter of the Bible that you can use to test the translation to make sure that it is communicating clearly. (See http://ufw.io/tq/ for the questions.)
There are a set of questions and answers for each *Open Bible Story* and for each chapter of the Bible that you can use to test the translation to make sure that it is communicating clearly. (See https://door43.org/u/WycliffeAssociates/en_tq for the questions.)
### Proper Documentation for Level Three Affirmation
### Documentation for Level Three Affirmation
I, as a representative of the *<u>fill in name of church network or Bible translation organization</u>* Church Network or Bible translation organization serving the *<u>fill in the name of the language community</u>* language community, approve of the translation, and affirm the following:
I, as a representative of the *<u>fill in name of church network or Bible translation organization</u>* Church Network or Bible translation organization serving the *<u>fill in the name of the language community</u>* language community, affirm the quality of the translation, and affirm the following:
1. The translation conforms to the Statement of Faith and Translation Guidelines.
1. The translation is accurate and clear in the target language.
1. The translation uses an acceptable style of the language.
1. The community approves of the translation.
1. The community affirms the quality of the translation.
If any problems remain unresolved after meeting with the translation team a second time, please make note of them here.
@ -14,4 +14,5 @@ Signed: *<u>sign here</u>*
Position: *<u>fill in your position here</u>*
For Gateway Languages, you will need to follow the [Source Text Process](../../process/source-text-process/01.md) so that your translation can become a source text.
For Gateway Languages, you will need to follow the [Source Text Process](../../process/source-text-process/01.md) so that your translation can become a source text.
@ -5,9 +5,9 @@ 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).
Also keep in mind that the translators may have included information that the original audience would have understood from the original message, but that the original author did not state explicitly. When this information is necessary for the target audience to understand the text, it is good to include it explicitly. For more about this, see [Implicit and Explicit Information](../../jit/figs-explicit/01.md).
1. Does the translation conform to the Statement of Faith and Translation Guidelines?
1. Did the translation team show a good understanding of the source language as well as the target language and culture?
@ -28,9 +28,10 @@ If you answer "yes" to any of the questions in this second group, please explain
1. Are there any doctrinal errors in the translation?
1. Did you find any areas of the translation that seem to contradict the national language translation or the important matters of faith found in your Christian community?
1. Did the translation team add extra information or ideas that were not part of the message in the source text? (Remember, the original message also includes [Implicit Information](../../translate/figs-explicit/01.md).)
1. Did the translation team add extra information or ideas that were not part of the message in the source text? (Remember, the original message also includes [Implicit Information](../../jit/figs-explicit/01.md).)
1. Did the translation team leave out information or ideas that were part of the message in the source text?
If there were problems with the translation, make plans to meet with the translation team and resolve these problems. After you meet with them, the translation team may need to check their revised translation with the community leaders to make sure that it still communicates well, and then meet with you again.
When you are ready to approve the translation, go here: [Level 3 Approval](../level3-approval/01.md).
When you are ready to approve the translation, go here: [Level 3 Approval](../level3-approval/01.md).
@ -9,4 +9,5 @@ To check a translation for naturalness, it is not helpful to compare it to the s
To check a translation for naturalness, you or another member of the language community must read it out loud. You can read it to one other person who speaks the target language or to a group of people. Before you start reading, tell the people listening that you want them to stop you when they hear something that does not sound like the way someone from your language community would say it. When someone stops you, then you can discuss together how someone would say that same thing in a more natural way.
It is helpful to think about a situation in your village in which people would talk about the same kind of thing that the translation is talking about. Imagine people that you know talking about that thing, and then say it out loud in that way. If others agree that that is a good and natural way to say it, then write it that way in the translation.
It is helpful to think about a situation in your village in which people would talk about the same kind of thing that the translation is talking about. Imagine people that you know talking about that thing, and then say it out loud in that way. If others agree that that is a good and natural way to say it, then write it that way in the translation.
@ -113,4 +113,5 @@ This section can be strengthened through doing more accuracy checking. (See [Acc
**no | yes** Church leaders from at least two different church networks have reviewed the translation of this chapter and agree that it is accurate. *(This addresses the final aspect of Level 2, the Church check).*
**no | yes** The leadership or their delegates of at least two different church networks have reviewed the translation of this chapter and endorse it as a faithful translation of this chapter of the Bible in this language. *(This addresses Level 3.)*
**no | yes** The leadership or their delegates of at least two different church networks have reviewed the translation of this chapter and endorse it as a faithful translation of this chapter of the Bible in this language. *(This addresses Level 3.)*
@ -21,8 +21,9 @@ 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
The back translation should use the sentence structure that is natural for the language of wider communication, not the structure that is used in the target language. This means that the back translation should use the word order that is natural for the language of wider communication, not the word order that is used in the target language. The back translation should also use the way of relating phrases to each other and the way of indicating logical relations, such as cause or purpose, that are natural for the language of wider communication. This will make the back translation easier to read and understand for the translation checker. This will also speed up the process of checking the back translation.
The back translation should use the sentence structure that is natural for the language of wider communication, not the structure that is used in the target language. This means that the back translation should use the word order that is natural for the language of wider communication, not the word order that is used in the target language. The back translation should also use the way of relating phrases to each other and the way of indicating logical relations, such as cause or purpose, that are natural for the language of wider communication. This will make the back translation easier to read and understand for the translation checker. This will also speed up the process of checking the back translation.
@ -17,4 +17,5 @@ Third, when the back translation is written, the translation checker can also pr
Even if there is not time for the checker to send his questions to the translation team before their meeting, they will still be able to review more material at the meeting than they would have been able to review otherwise because the checker has already read the back translation and has already prepared his questions. Because he has had this previous preparation time, he and the translation team can use their meeting time to discuss only the problem areas of the translation rather than reading through the entire translation at a slow pace, as is required when making an oral back translation.
Fourth, the written back translation relieves the strain on the translation checker from having to concentrate for many hours at a time on hearing and understanding an oral translation as it is spoken to him. If the checker and translation team are meeting in a noisy environment, the difficulty of making sure that he hears every word correctly can be quite exhausting for the checker. The mental strain of concentration increases the likelihood that the checker will miss some problems with the result that they remain uncorrected in the biblical text. For these reasons, we recommend the use of a written back translation whenever possible.
Fourth, the written back translation relieves the strain on the translation checker from having to concentrate for many hours at a time on hearing and understanding an oral translation as it is spoken to him. If the checker and translation team are meeting in a noisy environment, the difficulty of making sure that he hears every word correctly can be quite exhausting for the checker. The mental strain of concentration increases the likelihood that the checker will miss some problems with the result that they remain uncorrected in the biblical text. For these reasons, we recommend the use of a written back translation whenever possible.
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.
The back translation can also be very useful in improving the target language translation even before the checker uses it to check the translation. When the translation team reads the back translation, they can see how the back translator has understood their translation. Sometimes, the back translator has understood their translation in a different way than they intended to communicate. In those cases, they can change their translation so that it communicates more clearly the meaning that they intended. When the translation team is able to use the back translation in this way before they give it to the checker, they can make many improvements to their translation. When they do this, the checker can do his checking much more rapidly, because the translation team was able to correct many of the problems in the translation before meeting with the checker.
The back translation can also be very useful in improving the target language translation even before the checker uses it to check the translation. When the translation team reads the back translation, they can see how the back translator has understood their translation. Sometimes, the back translator has understood their translation in a different way than they intended to communicate. In those cases, they can change their translation so that it communicates more clearly the meaning that they intended. When the translation team is able to use the back translation in this way before they give it to the checker, they can make many improvements to their translation. When they do this, the checker can do his checking much more rapidly, because the translation team was able to correct many of the problems in the translation before meeting with the checker.
@ -7,4 +7,5 @@ An interlinear back translation is one in which the back translator puts a trans
### Free Back Translation
A free back translation is one in which the back translator makes a translation in the language of wider communication in a separate space from the target language translation. The disadvantage of this method is that the back translation is not related as closely to the target language translation. The back translator can overcome this disadvantage when back translating the Bible, however, by including the verse numbers with the back translation. By referring to the verse numbers in both translations, the translation checker can keep track of which part of the back translation represents which part of the target language translation. The advantage of this method is that the back translation can use the grammar and word order of the language of wider communication, and so it is much easier for the translation checker to read and understand. Even while using the grammar and word order of the language of wider communication, however, the back translator should remember to translate the words in a literal way. We recommend that the back translator use the method of free back translation.
A free back translation is one in which the back translator makes a translation in the language of wider communication in a separate space from the target language translation. The disadvantage of this method is that the back translation is not related as closely to the target language translation. The back translator can overcome this disadvantage when back translating the Bible, however, by including the verse numbers with the back translation. By referring to the verse numbers in both translations, the translation checker can keep track of which part of the back translation represents which part of the target language translation. The advantage of this method is that the back translation can use the grammar and word order of the language of wider communication, and so it is much easier for the translation checker to read and understand. Even while using the grammar and word order of the language of wider communication, however, the back translator should remember to translate the words in a literal way. We recommend that the back translator use the method of free back translation.
A back translation is a translation of the biblical text from the local target language back into the language of wider communication. It is called a "back translation" because it is a translation in the opposite direction than what was done to create the local target language translation.
A back translation is not done in a completely normal style, however, because it does not have naturalness as a goal in the language of the translation (in this case, the language of wider communication). Instead, its goal is to represent the words and expressions of the local language translation in a literal way, while also using the grammar and word order of the language of wider communication. In this way, the translation checker can most clearly see the meaning of the words in the target language text, and can also understand the back translation well and read it more quickly and easily.
A back translation is not done in a completely normal style, however, because it does not have naturalness as a goal in the language of the translation (in this case, the language of wider communication). Instead, its goal is to represent the words and expressions of the local language translation in a literal way, while also using the grammar and word order of the language of wider communication. In this way, the translation checker can most clearly see the meaning of the words in the target language text, and can also understand the back translation well and read it more quickly and easily.
We have seen where the translation team will do a lot of checking of their own translation. Those checks bring their work up to checking Level One.
For Level Two and Level Three, the translation team needs to take their work to members of the language community and to the church leaders. This is necessary because the translation team is very close to and involved in their work; thus they occasionally miss mistakes that others can see more easily. Other speakers of the language can suggest better ways of saying things that the translation team may not have thought of. Sometimes the translation team makes the translation sound strange because they are following the words of the source language too closely. Other speakers of the language can help them fix that. Also, the translation team may lack some of the expertise or knowledge of the Bible that others have, and so there may be some mistakes that others can correct for them. For these reasons, people that are not part of the translation team need to check the translation.
In this manual, you will find guidelines for level two and level three checks, which each take the translated portions out into the wider community for further review.
1. 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
@ -41,4 +41,5 @@ Some questions will need to be set aside for later, after the checking session.
### Key Words
Make sure that the translation team is keeping a list of the translationWords (important terms) from the Bible passages that they are translating, along with the term in the target language that they have decided to use for each of these important terms. You and the translation team will probably need to add to this list and modify the terms from the target language as you progress through the translation of the Bible. Use the list of translationWords to alert you when there are Key Words in the passage that you are translating. Whenever there is a Key Word in the Bible, make sure that the translation uses the term or phrase that has been chosen for that Key Word, and also make sure that it makes sense each time. If it does not make sense, then you will need to discuss why it makes sense in some places but not in others. Then you may need to modify or change the chosen term, or decide to use more than one term in the target language to fit different ways that the Key Word is used. One useful way to do this is to keep track of each important term on a spreadsheet, with columns for the source language term, the target language term, alternative terms and the Bible passages where you are using each term. We hope that this feature will be in future versions of translationStudio.
Make sure that the translation team is keeping a list of the translationWords (important terms) from the Bible passages that they are translating, along with the term in the target language that they have decided to use for each of these important terms. You and the translation team will probably need to add to this list and modify the terms from the target language as you progress through the translation of the Bible. Use the list of translationWords to alert you when there are Key Words in the passage that you are translating. Whenever there is a Key Word in the Bible, make sure that the translation uses the term or phrase that has been chosen for that Key Word, and also make sure that it makes sense each time. If it does not make sense, then you will need to discuss why it makes sense in some places but not in others. Then you may need to modify or change the chosen term, or decide to use more than one term in the target language to fit different ways that the Key Word is used. One useful way to do this is to keep track of each important term on a spreadsheet, with columns for the source language term, the target language term, alternative terms and the Bible passages where you are using each term. We hope that this feature will be in future versions of translationStudio.
1. 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).)
1. Check for anything that appears to be added, that was not a part of the meaning of the source text. (Remember, the original meaning also includes [Implicit Information](../../jit/figs-explicit/01.md).)
1. Check for anything that appears to be missing, that was a part of the meaning of the source text but was not included in the translation.
1. Check for any meaning that appears to be different than the meaning of the source text.
@ -17,4 +16,5 @@
1. Discuss the words about the spirit world and how they are understood in the target culture. Make sure that the ones used in the translation communicate the right thing.
1. Check anything that you think might be especially difficult to understand or translate in the passage.
After checking all of these things and making corrections, have the translation team read the passage out loud again to each other or to other members of their community to make sure that everything still flows in a natural way and uses the right connectors. If a correction made something sound unnatural, they will need to make additional adjustments to the translation. This process of testing and revision should repeat until the translation communicates clearly and naturally in the target language.
After checking all of these things and making corrections, have the translation team read the passage out loud again to each other or to other members of their community to make sure that everything still flows in a natural way and uses the right connectors. If a correction made something sound unnatural, they will need to make additional adjustments to the translation. This process of testing and revision should repeat until the translation communicates clearly and naturally in the target language.
@ -3,21 +3,21 @@ The unfoldingWord project exists because we want to see **unrestricted biblical
Jesus commanded his disciples to make disciples of EVERY people group:
>"Jesus came to them and spoke to them and said, 'All authority has been given to me in heaven and on earth. Go therefore and make disciples of all the nations. Baptize them into the name of the Father, of the Son, and of the Holy Spirit. Teach them to obey all the things that I have commanded you. And see, I am with you always, even to the end of the world.'" (Matthew 28:18-20 ULT)
>"Jesus came to them and spoke to them and said, 'All authority has been given to me in heaven and on earth. Go therefore and make disciples of all the nations. Baptize them into the name of the Father, of the Son, and of the Holy Spirit. Teach them to obey all the things that I have commanded you. And see, I am with you always, even to the end of the world.'" (Matthew 28:18-20 ULB)
We have the promise that people from EVERY language will be in heaven:
>"After these things I saw, and behold, there was a great crowd, which no one was able to number, out of every nation, tribe, people, and language, standing before the throne and before the Lamb." (Revelation 7:9 ULT)
>After these things I saw, and behold, there was a great crowd, which no one was able to number, out of every nation, tribe, people, and language, standing before the throne and before the Lamb. (Revelation 7:9 ULB)
Understanding the Word of God in one's heart language is important:
>"So faith comes from hearing, and hearing by the word of Christ." (Romans 10:17 ULT)
>So faith comes from hearing, and hearing by the word of Christ. (Romans 10:17 ULB)
### How Do We Do This?
How do we accomplish the goal of **unrestricted biblical content in every language**?
* [unfoldingWord Project](https://unfoldingword.bible/) - By working with other like-minded organizations
* [unfoldingWord Network](https://unfoldingword.org/network/) - By partnering with other like-minded organizations
* [Statement of Faith](../statement-of-faith/01.md) - By working with those who have the same beliefs
* [Translation Guidelines](../translation-guidelines/01.md) - By using a common translation theory
* [Open License](../open-license/01.md) - By releasing everything we create under an open license
@ -28,9 +28,9 @@ How do we accomplish the goal of **unrestricted biblical content in every langua
* **Content** - We create and make available for translation free and unrestricted biblical content. See http://ufw.io/content/ for a complete list of resources and translations. Here are a few samples:
* **Open Bible Stories** - a chronological mini-Bible comprising 50 key stories of the Bible, from Creation to Revelation, for evangelism and discipleship, in print, audio, and video (see http://ufw.io/stories/).
* **the Bible** - the only inspired, inerrant, sufficient, authoritative Word of God made available under an open license for unrestricted translation, use, and distribution (see http://ufw.io/bible/).
* **translationNotes** - linguistic, cultural, and exegetical helps for translators. They exist for Open Bible Stories and the Bible (see http://ufw.io/tn/).
* **translationQuestions** - questions for each chunk of text that translators and checkers can ask to help ensure that their translation is understood correctly. Available for Open Bible Stories and the Bible (see http://ufw.io/tq/).
* **translationWords** - a list of important Biblical terms with a short explanation, cross references, and translation aids. Useful for Open Bible Stories and the Bible (see http://ufw.io/tw/).
* **Translation Notes** - linguistic, cultural, and exegetical helps for translators. They exist for Open Bible Stories and the Bible (see http://ufw.io/tn/).
* **Translation Questions** - questions for each chunk of text that translators and checkers can ask to help ensure that their translation is understood correctly. Available for Open Bible Stories and the Bible (see http://ufw.io/tq/).
* **Translation Words** - a list of important Biblical terms with a short explanation, cross references, and translation aids. Useful for Open Bible Stories and the Bible (see http://ufw.io/tw/).
* **Tools** - We create translation, checking, and distribution tools that are free and open-licensed. See http://ufw.io/tools/ for a complete list of tools. Here are a few samples:
* **Door43** - an online translation platform where people can collaborate on translation and checking, also the content management system for unfoldingWord (see https://door43.org/).
@ -41,4 +41,3 @@ How do we accomplish the goal of **unrestricted biblical content in every langua
* **Training** - We create resources to train mother tongue translation teams. translationAcademy (this resource) is our primary training tool. We also have audio recording and training resources. See http://ufw.io/training/ for a complete list of training materials.
See in Reader
SusanQuigley
Tabitha Price
chrisjarka
Henry Whitney
Tom Warren
John Hutchins
David Statezni
Ed Davis
Perry J Oakes
Jesse Griffin