forked from WycliffeAssociates/en_tm
See in Reader
Resolve merge conflict with Tabitha branch
This commit is contained in:
parent
4c3ac44f11
commit
4ba3900ea1
|
|
@ -1,4 +1,4 @@
|
|||
# English Translation Manual
|
||||
# English translationAcademy
|
||||
|
||||
## Overview
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
|
@ -1,8 +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.
|
||||
|
|
@ -1 +1 @@
|
|||
What is the Checking Manual?
|
||||
What is Authentic Assessment and how does it apply to quality assurance?
|
||||
|
|
@ -1 +1 @@
|
|||
Introduction to the Checking Manual
|
||||
Introduction to Authentic Assessment in checking Scripture
|
||||
|
|
@ -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 network (see https://unfoldingword.org ), 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.*
|
||||
|
|
|
|||
|
|
@ -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.org ) 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.
|
||||
|
|
@ -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.
|
||||
|
|
@ -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)).
|
||||
|
|
@ -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.
|
||||
|
|
@ -1,13 +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)
|
||||
* **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
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Finding Answers
|
||||
Hot to Get Answers
|
||||
|
|
@ -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.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,15 @@
|
|||
#### Statement of Faith
|
||||
Found at [Bible In Every Language](https://bibleineverylanguage.org/statement-of-faith/)
|
||||
|
||||
*The official version of this document is found at http://ufw.io/faith/.*
|
||||
* We believe in the divine inspiration and consequent authority of the whole canonical Scriptures
|
||||
* We believe in the doctrine of the Trinity
|
||||
* We believe in the fall of man, his consequent moral depravity and his need of regeneration
|
||||
* We believe in the atonement through the substitutionary death of Christ
|
||||
* We believe in the doctrine of justification by faith
|
||||
* We believe in the resurrection of the body, in the case of the just and the unjust
|
||||
* We believe in the eternal life of the saved and the eternal punishment of the lost
|
||||
|
||||
*The following statement of faith is subscribed to by all member organizations of and contributors to the [unfoldingWord](https://unfoldingword.org/) project. It is in agreement with these historical creeds: [Apostles’ Creed](https://git.door43.org/Door43/en_creeds/src/master/content/apostles.md), [Nicene Creed](https://git.door43.org/Door43/en_creeds/src/master/content/nicene.md), and [Athanasian Creed](https://git.door43.org/Door43/en_creeds/src/master/content/athanasian.md); and also the [Lausanne Covenant](http://www.lausanne.org/en/documents/lausanne-covenant.html).*
|
||||
*The following statement of faith is subscribed to by all member organizations of and contributors to the [unfoldingWord](https://unfoldingword.org/) project. It is in agreement with the [Lausanne Covenant](http://www.lausanne.org/en/documents/lausanne-covenant.html).*
|
||||
|
||||
We believe that Christian belief can and should be divided into **essential beliefs** and **peripheral beliefs** (Romans 14).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
The 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. 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 contains the following sections:
|
||||
translationAcademy contains the following sections:
|
||||
|
||||
* [Introduction](../ta-intro/01.md) - introduces translationAcademy and the unfoldingWord project
|
||||
* [Translation Tips and Practices](../../translate/translate/01.md) - explains the basics of translation theory and practical translation helps
|
||||
* [Learning Topics](../../translate/translate-manual/01.md) - these are practical translation helps that are also linked from the translationNotes
|
||||
* [Checking](../../checking/intro-check/01.md) - explains the basics of checking theory and best practices
|
||||
* [Translation Manual](../../translate/translate/01.md) - explains the basics of translation theory and practical translation helps
|
||||
* [Just In Time Topics](../../translate/translate-manual/01.md) - these are practical translation helps that are also linked from the translationNotes
|
||||
* [Checking Manual](../../checking/intro-check/01.md) - explains the basics of checking theory and best practices
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
What is the Translation Manual?
|
||||
What is translationAcademy?
|
||||
|
|
@ -1 +1 @@
|
|||
Introduction
|
||||
Introduction to the Translation Manual
|
||||
|
|
@ -1,6 +1,4 @@
|
|||
|
||||
*The official version of this document is found at http://ufw.io/guidelines/.*
|
||||
|
||||
*The following statement on the principles and procedures used in translation is subscribed to by all member organizations of and contributors to the unfoldingWord project (see https://unfoldingword.org). All translation activities are carried out according to these common guidelines.*
|
||||
|
||||
1. **Accurate** — Translate accurately, without detracting from, changing, or adding to the meaning of the original text. Translated content should faithfully communicate as precisely as possible the meaning of the original text as it would have been understood by the original audience. (see [Create Accurate Translations](../../translate/guidelines-accurate/01.md))
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ dublin_core:
|
|||
contributor:
|
||||
- 'Susan Quigley, MA in Linguistics'
|
||||
- 'Henry Whitney, BA Linguistics'
|
||||
- 'Tabitha Price'
|
||||
- 'James N. Pohlig, M.Div., MA in Linguistics, D. Litt. in Biblical Languages'
|
||||
- 'Bev Staley'
|
||||
- 'Carol Brinneman'
|
||||
|
|
@ -22,7 +23,7 @@ dublin_core:
|
|||
identifier: 'en'
|
||||
title: 'English'
|
||||
direction: 'ltr'
|
||||
modified: '2017-11-30'
|
||||
modified: '2019-01-30'
|
||||
publisher: 'unfoldingWord'
|
||||
relation:
|
||||
- 'en/ulb'
|
||||
|
|
@ -38,7 +39,7 @@ dublin_core:
|
|||
subject: ''
|
||||
title: 'Translation Manual'
|
||||
type: 'man'
|
||||
version: '9'
|
||||
version: '022019'
|
||||
|
||||
checking:
|
||||
checking_entity:
|
||||
|
|
@ -52,7 +53,7 @@ projects:
|
|||
identifier: 'intro'
|
||||
path: './intro'
|
||||
sort: 0
|
||||
title: 'Introduction'
|
||||
title: 'Introduction to Translation Manual'
|
||||
versification:
|
||||
-
|
||||
categories:
|
||||
|
|
@ -60,15 +61,15 @@ projects:
|
|||
identifier: 'translate'
|
||||
path: './translate'
|
||||
sort: 1
|
||||
title: 'Translation Tips and Practice'
|
||||
title: 'Translation Manual'
|
||||
versification:
|
||||
-
|
||||
categories:
|
||||
- 'ta'
|
||||
identifier: 'just-in-time'
|
||||
path: './jit'
|
||||
identifier: 'JIT'
|
||||
path: './translate'
|
||||
sort: 2
|
||||
title: 'Learning Topics'
|
||||
title: 'Just In Time Topics'
|
||||
versification:
|
||||
-
|
||||
categories:
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ title: "Table of Contents"
|
|||
sections:
|
||||
- title: "Introduction"
|
||||
sections:
|
||||
- title: "Introduction"
|
||||
- title: "Introduction to the Translation Manual"
|
||||
link: translate-manual
|
||||
- title: "Terms to Know"
|
||||
link: translate-terms
|
||||
|
|
@ -148,7 +148,7 @@ sections:
|
|||
link: resources-words
|
||||
- title: "Using translationQuestions"
|
||||
link: resources-questions
|
||||
- title: "Learning Topics"
|
||||
- title: "Just-in-Time Learning Modules"
|
||||
sections:
|
||||
- title: "Figures of Speech"
|
||||
sections:
|
||||
|
|
|
|||
|
|
@ -1,6 +1,4 @@
|
|||
|
||||
### What Does the Translation Manual Teach?
|
||||
|
||||
This manual teaches translation theory and how to make a good translation for Other Languages (OLs). Some of the principles of translation in this manual also apply to Gateway Language translation. For specific instruction on how to translate the set of translation tools for Gateway Languages, however, please see the Gateway Language Manual. It will be very helpful to study many of these modules before starting any type of translation project. Other modules, such as the ones about grammar, are only needed for "just-in-time" learning.
|
||||
|
||||
Some highlights in the Translation Manual:
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Introduction to Translation Manual
|
||||
What Does the Translation Manual Teach?
|
||||
Loading…
Reference in New Issue