diff --git a/archive/intro/translation-guidelines/01.md b/archive/intro/translation-guidelines/01.md new file mode 100644 index 0000000..9973665 --- /dev/null +++ b/archive/intro/translation-guidelines/01.md @@ -0,0 +1,12 @@ + +The following statement on the principles and procedures used in translation is subscribed to by all contributors to the Bible In Every Language website (see https://bibleineverylanguage.org). + +**All translation activities are carried out according to these common guidelines:** + +1. **Accurate** (see [Accurate Translations](../../translate/guidelines-accurate/01.md)) + +1. **Clear** — (see [Clear Translations](../../translate/guidelines-clear/01.md)) + +1. **Natural** — (see [Natural Translations](../../translate/guidelines-natural/01.md)) + + diff --git a/intro/translation-guidelines/sub-title.md b/archive/intro/translation-guidelines/sub-title.md similarity index 100% rename from intro/translation-guidelines/sub-title.md rename to archive/intro/translation-guidelines/sub-title.md diff --git a/intro/translation-guidelines/title.md b/archive/intro/translation-guidelines/title.md similarity index 100% rename from intro/translation-guidelines/title.md rename to archive/intro/translation-guidelines/title.md diff --git a/checking/authority-level1/01.md b/checking/authority-level1/01.md index cc7b5bf..52daeb8 100644 --- a/checking/authority-level1/01.md +++ b/checking/authority-level1/01.md @@ -1,7 +1,6 @@ ### Affirmation by Translation Team - -The intent of this level is to affirm the agreement of the translation team with standard Christian doctrine, as well as with the guidelines for ensuring the accuracy of the translation itself. Publishing content at this level makes it available to members of the language community and provides an open invitation (implied or direct) to them to suggest improvements to the translation. +The intent of this level is to affirm that the translators have taken steps to ensure the accuracy of their translation and that the translation is in agreement with standard Christian doctrine. Publishing content at this level makes it available to members of the language community and provides an open invitation (implied or direct) to them to suggest improvements to the translation. To achieve this level, the translation team asserts that the [Statement of Faith](../../intro/statement-of-faith/01.md) is an accurate reflection of their own beliefs and that the translated content is also in harmony with it. diff --git a/checking/authority-level2/01.md b/checking/authority-level2/01.md index c39951f..e0624c5 100644 --- a/checking/authority-level2/01.md +++ b/checking/authority-level2/01.md @@ -8,7 +8,7 @@ The intent of this level is two-fold: At this level, the model implements the concept of a "testimony of two or three witnesses" in the checking process. -To achieve this level, the translation team will submit the translation to members of the language community that will use the translation. The language community will review the translation for **clarity** and **naturalness**. The team will also work with church leaders from the language community to review the translation for **accuracy** by checking it against the source texts, the exegetical resources, the [Statement of Faith](../../intro/statement-of-faith/01.md), and the [Translation Guidelines](../../intro/translation-guidelines/01.md). +To achieve this level, the translation team will submit the translation to members of the language community that will use the translation. The language community will review the translation for **clarity** and **naturalness**. The team will also work with church leaders from the language community to review the translation for **accuracy** by checking it against the source texts, the exegetical resources, and the [Statement of Faith](../../intro/statement-of-faith/01.md). The translation team will edit the translation based on these reviews so that the language community affirms that it is natural and clear, and the church leaders affirm that it is accurate. diff --git a/checking/level3/01.md b/checking/level3/01.md index 4619c5d..a0e5f82 100644 --- a/checking/level3/01.md +++ b/checking/level3/01.md @@ -8,7 +8,7 @@ Level Three is completed when the translation has been thoroughly checked and va Here are some specific steps that can be followed for this check. However, the most important aspect of this check is to consider the authentic assessment rubric created by the translation team as the guide. -1. Does the translation conform to the Statement of Faith and Translation Guidelines? +1. Does the translation conform to the [Statement of Faith](../../intro/statement-of-faith/01.md) and the [Qualities of a Good Translation](../../translate/guidelines-intro/01.md)? 2. Did the translation team show a good understanding of the source language as well as the target language and culture? 3. Does the language community affirm that the translation speaks in a clear and natural way in their language? 4. Is the style that the translators followed appropriate for the community? diff --git a/intro/guidelines-church-approved/01.md b/intro/guidelines-church-approved/01.md new file mode 100644 index 0000000..6457de2 --- /dev/null +++ b/intro/guidelines-church-approved/01.md @@ -0,0 +1,18 @@ +The goal of the translation of biblical content is to produce a high-quality translation that is used and loved by the church. High-quality translations must be accurate, clear, and natural (see [Qualities of a Good Translation](../translate/guidelines-intro/01.md)). But for a translation to be used and loved by the church, it must be church-affirmed. + +Creating a church-affirmed translation is all about the process of translation, checking, and distribution. The more church networks that are involved in these processes, the more likely they will affirm the translation. + +As many church networks as possible should be contacted and encouraged to become a part of the translation and even to send some of their people to be a part of the translation team. They should be consulted and asked for their input into the translation project, its goals, and its process. + +If the church cannot actively lead the translation and coordinate all the efforts, it is necessary that whoever is leading the translation be affirmed by the church networks, preferably before they even start. + +### Church Affirmation and the Checking Levels + +Wycliffe Associates has developed three levels of translation checks to be done by three different groups of people. The goal of each of these checks is to assign an affirmation level to the translation. The affirmation level shows how broadly the church affirms the translation. + +* Level 1 states that the church-affirmed translation team affirms the quality the translation. +* Level 2 states that the pastors and lay-people of local churches affirm the quality of the translation. +* Level 3 states that leaders of multiple church networks affirm the quality of the translation. + +At each checking level, the people leading the translation should encourage participation and input from the church networks. These steps will encourage local church ownership of the translation among as many church networks as possible. With this affirmation, there should be nothing hindering the translation from being used to strengthen and encourage the church. + diff --git a/intro/guidelines-church-approved/sub-title.md b/intro/guidelines-church-approved/sub-title.md new file mode 100644 index 0000000..1e38562 --- /dev/null +++ b/intro/guidelines-church-approved/sub-title.md @@ -0,0 +1,2 @@ +What is church affirmation? + diff --git a/intro/guidelines-church-approved/title.md b/intro/guidelines-church-approved/title.md new file mode 100644 index 0000000..5f507cd --- /dev/null +++ b/intro/guidelines-church-approved/title.md @@ -0,0 +1,2 @@ +Church Affirmation + diff --git a/translate/guidelines-collaborative/01.md b/intro/guidelines-collaborative/01.md similarity index 100% rename from translate/guidelines-collaborative/01.md rename to intro/guidelines-collaborative/01.md diff --git a/translate/guidelines-collaborative/sub-title.md b/intro/guidelines-collaborative/sub-title.md similarity index 100% rename from translate/guidelines-collaborative/sub-title.md rename to intro/guidelines-collaborative/sub-title.md diff --git a/intro/guidelines-collaborative/title.md b/intro/guidelines-collaborative/title.md new file mode 100644 index 0000000..5aaf0fa --- /dev/null +++ b/intro/guidelines-collaborative/title.md @@ -0,0 +1,2 @@ +Collaboration + diff --git a/translate/guidelines-ongoing/01.md b/intro/guidelines-ongoing/01.md similarity index 100% rename from translate/guidelines-ongoing/01.md rename to intro/guidelines-ongoing/01.md diff --git a/intro/guidelines-ongoing/sub-title.md b/intro/guidelines-ongoing/sub-title.md new file mode 100644 index 0000000..78d7d09 --- /dev/null +++ b/intro/guidelines-ongoing/sub-title.md @@ -0,0 +1,2 @@ +What is ongoing translation? + diff --git a/intro/guidelines-ongoing/title.md b/intro/guidelines-ongoing/title.md new file mode 100644 index 0000000..1e2ee81 --- /dev/null +++ b/intro/guidelines-ongoing/title.md @@ -0,0 +1,2 @@ +Ongoing Translation + diff --git a/intro/statement-of-faith/01.md b/intro/statement-of-faith/01.md index 48d1e5a..53e7e33 100644 --- a/intro/statement-of-faith/01.md +++ b/intro/statement-of-faith/01.md @@ -15,3 +15,6 @@ We believe: Peripheral beliefs are those beliefs based on Scripture where sincere believers may have disagreements in their interpretation. These include areas such as modes of baptism, the rapture, second coming of Christ, the Lord’s Supper and church practices. On peripheral beliefs, we can agreeably accept differences. +### Divine Familial Terms + +The divine familial terms are the words "Father" and "Son" when they refer to God the Father and God the Son. God is divine, and these terms show their family relationship to each other. Whenever the words "Father" and "Son" are used in the Bible to refer to the relationship between God the Father and God the Son (or between God the Father and Jesus Christ), they should be translated with the literal, ordinary words that people use to show the relationship between a man and his own son. (See: [Translating Son and Father](../jit/guidelines-sonofgodprinciples/01.md) and [Son of God and God the Father](../jit/guidelines-sonofgod/01.md).) All contributors to the Bible In Every Language website (see https://bibleineverylanguage.org) agree to do this. \ No newline at end of file diff --git a/intro/statement-of-faith/sub-title.md b/intro/statement-of-faith/sub-title.md index 9733424..4cba880 100644 --- a/intro/statement-of-faith/sub-title.md +++ b/intro/statement-of-faith/sub-title.md @@ -1,2 +1,2 @@ -What do we believe? +What do we believe, and what are divine familial terms? diff --git a/intro/statement-of-faith/title.md b/intro/statement-of-faith/title.md index c34648c..609270e 100644 --- a/intro/statement-of-faith/title.md +++ b/intro/statement-of-faith/title.md @@ -1,2 +1,2 @@ -Statement of Faith +Statement of Faith and Divine Familial Terms diff --git a/intro/ta-intro/01.md b/intro/ta-intro/01.md index 11d0dd8..41134e4 100644 --- a/intro/ta-intro/01.md +++ b/intro/ta-intro/01.md @@ -1,7 +1,7 @@ The Translation Manual contains the following sections: -* [Translating with Wycliffe Associates Resources](../../intro/wa/01.md) - This section introduces how Bible translation is done with Wycliffe Associates. Among other things, it describes the Gateway Languages Strategy and tells about translation tools and resources to support that strategy. +* [Church Owned Bible Translation](../../intro/wa/01.md) - This section introduces how Bible translation is done with Wycliffe Associates. Among other things, it describes the Gateway Languages Strategy and tells about translation tools and resources to support that strategy. * [Translation Theory and Practices](../../translate/translate-manual/01.md) - This explains the basics of translation theory and provides simple explanations of standard practices. * [Translation Topics](../../jit/figs-intro/01.md) - These are practical translation helps, specifically targeting potential challenges, that are also linked from the Translation Notes. * [Checking](../../checking/intro-checking/01.md) - This explains the steps of checking that should begin as soon as a draft is completed, and continue throughout the remainder of the project. It also suggests who should be involved and provides best practices for affirming quality. diff --git a/intro/toc.yaml b/intro/toc.yaml index bace451..a6dfe67 100644 --- a/intro/toc.yaml +++ b/intro/toc.yaml @@ -1,19 +1,25 @@ -title: "Translating with Wycliffe Associates Resources" +title: "Church Owned Bible Translation" sections: - title: "Translation Manual Sections" link: ta-intro - - title: "Translating with Wycliffe Associates Resources" + - title: "Church Owned Bible Translation" link: wa - title: "Why We Translate the Bible" link: translate-why - - title: "Statement of Faith" + - title: "Statement of Faith and Divine Familial Terms" link: statement-of-faith - - title: "Translation Guidelines" - link: translation-guidelines + - title: "Church Affirmation" + link: guidelines-church-approved + + - title: "Collaboration" + link: guidelines-collaborative + + - title: "Ongoing Translation" + link: guidelines-ongoing - title: "Open License" link: open-license diff --git a/intro/translate-why/01.md b/intro/translate-why/01.md index ce22700..6f1f477 100644 --- a/intro/translate-why/01.md +++ b/intro/translate-why/01.md @@ -1,5 +1,5 @@ -The purpose of the translation manual is to empower you to translate the Bible. Translating God's Word into your language to help your people grow as disciples of Jesus is an important task. You must be committed to this task, take your responsibility seriously, and pray that the Lord will help you. +Translating God's Word into your language to help your people grow as disciples of Jesus is an important task. You must be committed to this task, take your responsibility seriously, and pray that the Lord will help you. God has spoken to us in the Bible. He inspired the writers of the Bible to write his Word using the Hebrew, Aramaic and Greek languages. There were about 40 different authors writing from around 1400 B.C. to A.D. 100. These documents were written in the Middle East, North Africa and Europe. By recording his Word in those languages, God ensured that the people at those times and in those places could understand it. diff --git a/intro/translation-guidelines/01.md b/intro/translation-guidelines/01.md deleted file mode 100644 index 7c9a542..0000000 --- a/intro/translation-guidelines/01.md +++ /dev/null @@ -1,28 +0,0 @@ - -The following statement on the principles and procedures used in translation is subscribed to by all contributors to the Bible In Every Language website (see https://bibleineverylanguage.org). - -**All translation activities are carried out according to these common guidelines:** - -1. **Accurate** — Translate accurately, without changing 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. Translators can achieve accuracy by recognizing the authority of the original language texts, and researching Biblical language tools to clarify difficulties. (see [Create Accurate Translations](../../translate/guidelines-accurate/01.md) and [Create Authoritative Translations](../../translate/guidelines-authoritative/01.md)) -1. **Faithful** — Avoid theological or other bias in your translation. Use key terms that are faithful to the vocabulary of the original biblical languages. **Use equivalent common language terms for the biblical words that describe the relationship between God the Father and God the Son.** These may be clarified, as needed, in footnotes or other supplemental resources. (see [Create Faithful Translations](../../translate/guidelines-faithful/01.md)) -1. **Historical** — Communicate historical events and facts accurately, providing additional information as needed in order to accurately communicate the intended message to people who do not share the same context and culture as the original recipients of the original content. (see [Create Historical Translations](../../translate/guidelines-historical/01.md)) -1. **Clear and Natural** — Use whatever language structures are necessary to achieve the highest level of comprehension, complying with common form and flow in the target language. (see [Create Clear Translations](../../translate/guidelines-clear/01.md) and [Create Natural Translations](../../translate/guidelines-natural/01.md)) - -We believe that a translation has the highest likelihood of being good quality when after applying the guidelines above, the following are completed: -1. It is tested and approved by believers of the language community and their church leaders. -2. Ongoing revisions and improvements are made. - -### Identifying and Managing Translation Quality - -The quality of a translation generally refers to the fidelity of the translation to the meaning of the original, and the degree to which the translation is understandable and effective for the speakers of the receptor language. The strategy we suggest involves checking the forms and communicative quality of the translation with the language community, and checking the fidelity of the translation with the church in that people group. - -The specific steps involved may vary significantly, depending on the language and context of the translation project. Generally, we consider a good translation to be one that has been reviewed by the speakers of the language community and also by the leadership of the church in the language group so that it is: - -1. **Accurate, Clear, Natural, and Equal** — Faithful to the intended meaning of the original, as determined by the church in that people group and in alignment with the Church global and historical, and consequently: -1. **Affirmed by the Church** - Endorsed and used by the church. (see [Create Church-Affirmed Translations](../../translate/guidelines-church-approved/01.md)) - -We also recommend that the translation work be: - -1. **Collaborative** — Where possible, work together with other believers who speak your language to translate, check, and distribute the translated content, ensuring that it is of the highest quality and available to as many people as possible. (see [Create Collaborative Translations](../../translate/guidelines-collaborative/01.md)) -1. **Ongoing** — Translation work is never completely finished. Leaders should encourage those who are skilled with the language to suggest better ways to say things when they notice that improvements can be made. Any errors in the translation should also be corrected as soon as they are discovered. If the translation team is unable to continue oversight of the project, we recommend that church leaders form a translation committee to manage edits, revisions, new translations, and distribution. The translation committee can oversee these suggestions and edits. This committee will decide when a complete revision should be done and will also be responsible to determine when a translation has been revised enough that new paper copies should be made available to the community. - diff --git a/intro/wa/01.md b/intro/wa/01.md index a68809b..93e4b6f 100644 --- a/intro/wa/01.md +++ b/intro/wa/01.md @@ -1,8 +1,11 @@ -This section introduces how Bible translation is done with Wycliffe Associates. It has the following modules: +This section introduces Church Owned Bible Translation. It has the following modules: * [Why We Translate the Bible](../../intro/translate-why/01.md) -* [Statement of Faith](../../intro/statement-of-faith/01.md) -* [Open License](../../intro/open-license/01.md) +* [Statement of Faith and Divine Familial Terms](../../intro/statement-of-faith/01.md) +- [Church Affirmation](../../intro/guidelines-church-approved/01.md) +- [Collaboration](../../intro/guidelines-collaborative/01.md) +- [Ongoing Translation](../../intro/guidelines-ongoing/01.md) \>\>\>\>\>\>\> +- [Open License](../../intro/open-license/01.md) * [Gateway Languages Strategy](../../intro/gl-strategy/01.md) * [WA Bible Translation Tools and Resources](../../intro/finding-answers/01.md) * [MAST Foundation and Philosophy](../../intro/mast-intro/01.md) diff --git a/intro/wa/sub-title.md b/intro/wa/sub-title.md index 2a9490c..c760970 100644 --- a/intro/wa/sub-title.md +++ b/intro/wa/sub-title.md @@ -1 +1 @@ -What are the modules that describe how to translate the Bible using the Wycliffe Associates resources? \ No newline at end of file +What are the modules that show how Wycliffe Associates promotes Church Owned Bible Translation? \ No newline at end of file diff --git a/intro/wa/title.md b/intro/wa/title.md index 03a6306..6cc582e 100644 --- a/intro/wa/title.md +++ b/intro/wa/title.md @@ -1 +1 @@ -Translating with Wycliffe Associates Resources \ No newline at end of file +Church Owned Bible Translation Training \ No newline at end of file diff --git a/jit/guidelines-sonofgodprinciples/01.md b/jit/guidelines-sonofgodprinciples/01.md index 75e2998..8dc48b8 100644 --- a/jit/guidelines-sonofgodprinciples/01.md +++ b/jit/guidelines-sonofgodprinciples/01.md @@ -1,5 +1,5 @@ -Wycliffe Associates supports Bible translations that represent the concepts "Father" and "Son" when they refer to God. +Wycliffe Associates is committed to serving and supporting translations that comply with common language usage of "Father" and "Son" when referring to God. (see: [Statement of Faith and Divine Familial Terms](../../intro/statement-of-faith/01.md)) ### Biblical Witness diff --git a/translate/guidelines-accurate/01.md b/translate/guidelines-accurate/01.md index 50c662d..3194ce3 100644 --- a/translate/guidelines-accurate/01.md +++ b/translate/guidelines-accurate/01.md @@ -1,7 +1,17 @@ -### Accurate Translations +An **accurate** translation of the Bible communicates the same message as the original. -To create an **accurate** translation of the Bible means that the translation communicates the same message as the source. When you engage in the first four steps of MAST you are first gaining a simple understanding of the text, and second transfering it into natural wording in your language. These steps are designed to be moved through chronologically to produce a rough draft of the text. As a translator you are already working to express the meaning as accurately as possible, while focusing on putting it into natural wording. Because accuracy to the original is essential for the translation to be considered of high quality, the checking steps are designed to check and improve accuracy. Additionaly several resources, including Translation Words and Translation Questions, have been developed to help with testing the accuracy of the translation. +#### Aspects of an Accurate Translation + +The following are ways in which a translation needs to be accurate. It needs to be: +* [Authoritative](../guidelines-authoritative/01.md) - It considers the biblical texts in the original languages as the highest authority for the meaning of biblical content. +* [Historical](../guidelines-historical/01.md) - It communicates historical events and facts accurately. +* [Faithful](../guidelines-faithful/01.md) - It accurately represents the full message of Scripture as intended for the original audience in the original context +* [Equal](../guidelines-equal/01.md) - It communicates any expressive meaning from the source language in an equal way in the target language. + +#### Using the MAST Steps and the Translation Resources for Accuracy + +When you engage in the first four steps of MAST you are first gaining a simple understanding of the text, and second transferring it into natural wording in your language. These steps are designed to be moved through sequentially to produce a rough draft of the text. As a translator you are already working to express the meaning as accurately as possible, while focusing on putting it into natural wording. Because accuracy to the original is essential for the translation to be considered of high quality, the checking steps are designed to check and improve accuracy. Additionally several resources, including Translation Words and Translation Questions, have been developed to help with testing the accuracy of the translation. #### Discover the Meaning @@ -11,7 +21,7 @@ In step one of the MAST process you will read through the entire chapter in the Part of affirming accuracy is comparing your blind draft to the ULB source text. When you do this during self-edit, you should make changes to your draft to include any information you missed, or to delete information you may have added. Additionally, you are welcome to use other resources, such as the Translation Notes or Translation Questions to make sure you accurately understood the passage and wrote a valid translation of it. -The final three steps of MAST, peer-edit, keyword check, and verse-by-verse check, all provide opportunities for checking accuracy. The use of all available resources, such as Translation Notes, Translation Questions, and Translation Words during these steps will help you to be confident in the accuracy of your translaton. +The final three steps of MAST, peer-edit, keyword check, and verse-by-verse check, all provide opportunities for checking accuracy. The use of all available resources, such as Translation Notes, Translation Questions, and Translation Words during these steps will help you to be confident in the accuracy of your translation. #### The Message of the Writer diff --git a/translate/guidelines-accurate/title.md b/translate/guidelines-accurate/title.md index 2264bfd..32f4c56 100644 --- a/translate/guidelines-accurate/title.md +++ b/translate/guidelines-accurate/title.md @@ -1,2 +1,2 @@ -Create Accurate Translations +Accurate Translations diff --git a/translate/guidelines-authoritative/title.md b/translate/guidelines-authoritative/title.md index 29e4344..e63f47f 100644 --- a/translate/guidelines-authoritative/title.md +++ b/translate/guidelines-authoritative/title.md @@ -1,2 +1,2 @@ -Create Authoritative Translations +Authoritative Translations diff --git a/translate/guidelines-church-approved/01.md b/translate/guidelines-church-approved/01.md deleted file mode 100644 index 4f1c92c..0000000 --- a/translate/guidelines-church-approved/01.md +++ /dev/null @@ -1,27 +0,0 @@ - -### Church-Affirmed Translations - -The first three qualities of a good translation are **Clear** (see [Create Clear Translations](../guidelines-clear/01.md)), **Natural** (see [Create Natural Translations](../guidelines-natural/01.md)), and **Accurate** (see [Create Accurate Translations](../guidelines-accurate/01.md)). All three of these directly affect the words and phrases that are used in the translation. If a translation is not one of these three, simply changing or reordering the words that were used can often fix the problem. The fourth quality, church-affirmed, has less to do with the words used and more to do with the process that is used. - -### The Goal of Translation - -The goal of the translation of biblical content is not only to produce a high-quality translation, but to produce a high-quality translation that is used and loved by the church. High-quality translations must be clear, natural, and accurate. But for a translation to be used and loved by the church, it must be church-affirmed. - -### How to Create a Church-Affirmed Translation - -Creating a church-affirmed translation is all about the process of translation, checking, and distribution. The more church networks that are involved in these processes, the more likely they will affirm the translation. - -As many church networks as possible should be contacted and encouraged to become a part of the translation and even to send some of their people to be a part of the translation team. They should be consulted and asked for their input into the translation project, its goals, and its process. - -If the church cannot actively lead the translation and coordinate all the efforts, it is necessary that whoever is leading the translation be affirmed by the church networks, preferably before they even start. - -### Church Affirmation and the Checking Levels - -The need for church-affirmation of a translation is clearly reflected in the Checking Levels. In fact, the Checking Levels are largely a measurement of how broadly the church affirms the translation. - -* Level 1 states that the church-affirmed translation team has affirmation the translation. -* Level 2 states that the pastors and lay-people of local churches affirm the translation. -* Level 3 states that leaders of multiple church networks affirm the translation. - -At each level, the people leading the translation should encourage participation and input from the church networks. These steps will encourage local church ownership of the translation among as many church networks as possible. With this affirmation, there should be nothing hindering the translation from being used to strengthen and encourage the church. - diff --git a/translate/guidelines-church-approved/sub-title.md b/translate/guidelines-church-approved/sub-title.md deleted file mode 100644 index 18c04ba..0000000 --- a/translate/guidelines-church-approved/sub-title.md +++ /dev/null @@ -1,2 +0,0 @@ -How do we create church-affirmed translations? - diff --git a/translate/guidelines-church-approved/title.md b/translate/guidelines-church-approved/title.md deleted file mode 100644 index 07ab533..0000000 --- a/translate/guidelines-church-approved/title.md +++ /dev/null @@ -1,2 +0,0 @@ -Create Church-Affirmed Translations - diff --git a/translate/guidelines-clear/01.md b/translate/guidelines-clear/01.md index 7cd7149..9a33b13 100644 --- a/translate/guidelines-clear/01.md +++ b/translate/guidelines-clear/01.md @@ -1,7 +1,4 @@ - -### Clear Translations - -A clear translation will use whatever language structures are needed to help readers easily read and understand it. This includes putting the text into a different form or arrangement and using as many or as few terms as necessary to communicate the original meaning as clearly as possible. +A **clear** translation will use whatever language structures are needed to help readers easily read and understand it. This includes putting the text into a different form or arrangement and using as many or as few terms as necessary to communicate the original meaning as clearly as possible. Step four in the MAST process is the "blind draft." During this step the translator writes in his own words what he remembers of the chunk he has just consumed and verbalized. By doing this step without looking at the source text, the translator will use natural wording. When he is done with this step he will check his own work, during step five, "self-edit." This step will help him to make sure the translation is clear. @@ -14,5 +11,5 @@ As a translator edits his blind draft, he should ask these questions to make sur * Am I separating paragraphs? * Have I used the right language and form for the type of writing this is? -There are other parts to the "self-edit" step including a comparison with the source text to confirm accuracy. See self-edit for an explanation of the whole process of step 5. +There are other parts to the "self-edit" step including a comparison with the source text to confirm accuracy. See [Self-Edit](../../checking/self-edit/01.md) for an explanation of the whole process of step 5. diff --git a/translate/guidelines-clear/title.md b/translate/guidelines-clear/title.md index e91d371..a4f4e5f 100644 --- a/translate/guidelines-clear/title.md +++ b/translate/guidelines-clear/title.md @@ -1,2 +1,2 @@ -Create Clear Translations +Clear Translations diff --git a/translate/guidelines-collaborative/title.md b/translate/guidelines-collaborative/title.md deleted file mode 100644 index 2e8eba0..0000000 --- a/translate/guidelines-collaborative/title.md +++ /dev/null @@ -1,2 +0,0 @@ -Create Collaborative Translations - diff --git a/translate/guidelines-equal/01.md b/translate/guidelines-equal/01.md index 19c10d7..df58622 100644 --- a/translate/guidelines-equal/01.md +++ b/translate/guidelines-equal/01.md @@ -72,5 +72,5 @@ your loyalty reaches to the clouds. (ULB) This verse of poetry repeats a similar idea in two lines, which is good Hebrew poetic style. Also, there are no verbs in the Hebrew original, so the ULB translation supplies the word "reaches" in both lines. Poetry in your language may have different things that mark it as poetry. When you are translating poetry, try to use the forms of your language that communicate to the reader that this is poetry, and that communicate the same emotions that the source poem is trying to communicate. -**Remember:** Communicate the feelings and attitudes of the original text. Translate them into forms that communicate in a similar way in your language. Consider how that meaning can best be **Accurately**, **Clearly**, **Equally**, and **Naturally Expressed** in the Target Language. +**Remember:** Communicate the feelings and attitudes of the original text. Translate them into forms that communicate in a similar way in your language. This is part of making an accurate translation diff --git a/translate/guidelines-equal/title.md b/translate/guidelines-equal/title.md index cf6f052..9056288 100644 --- a/translate/guidelines-equal/title.md +++ b/translate/guidelines-equal/title.md @@ -1,2 +1,2 @@ -Create Equal Translations +Equal Translations diff --git a/translate/guidelines-faithful/01.md b/translate/guidelines-faithful/01.md index 8a2d6d7..69d17d4 100644 --- a/translate/guidelines-faithful/01.md +++ b/translate/guidelines-faithful/01.md @@ -1,7 +1,5 @@ -### Faithful Translations - -A faithful translation of Scripture is one that accurately represents the full message of Scripture as intended for the original audience in the original context. This means the translation has nothing added, misconstrued, or deleted from the original message. (However, the message of a Bible passage includes implied information. See [Assumed Knowledge and Implicit Information](../jit/figs-explicit/01.md).) +A **faithful** translation of Scripture is one that accurately represents the full message of Scripture as intended for the original audience in the original context. This means the translation has nothing added, misconstrued, or deleted from the original message. (However, the message of a Bible passage includes implied information. See [Assumed Knowledge and Implicit Information](../jit/figs-explicit/01.md).) The translators should consider these key issues to create a faithful translaton: diff --git a/translate/guidelines-faithful/title.md b/translate/guidelines-faithful/title.md index 935056f..1427a88 100644 --- a/translate/guidelines-faithful/title.md +++ b/translate/guidelines-faithful/title.md @@ -1,2 +1,2 @@ -Create Faithful Translations +Faithful Translations diff --git a/translate/guidelines-historical/title.md b/translate/guidelines-historical/title.md index 2e49f70..fe2ebc2 100644 --- a/translate/guidelines-historical/title.md +++ b/translate/guidelines-historical/title.md @@ -1,2 +1,2 @@ -Create Historical Translations +Historical Translations diff --git a/translate/guidelines-intro/01.md b/translate/guidelines-intro/01.md index 63ccfb5..4976b42 100644 --- a/translate/guidelines-intro/01.md +++ b/translate/guidelines-intro/01.md @@ -1,28 +1,16 @@ -### Four Main Qualities +### Three Main Qualities -There are four main qualities of a good translation. It must be: - -* Clear - see [Create Clear Translations](../guidelines-clear/01.md) -* Natural - see [Create Natural Translations](../guidelines-natural/01.md) -* Accurate - see [Create Accurate Translations](../guidelines-accurate/01.md) -* Church-Affirmed - see [Create Church-Affirmed Translations](../guidelines-church-approved/01.md) - -We can think of each of these qualities as a leg of a four-legged stool. Each one is necessary. If one is missing, the stool will not stand well. Likewise, each of these qualities must be present in a translation in order for it to be useful and faithful to the church. - -#### Clear - -Use whatever language structures are necessary to achieve the highest level of comprehension. This includes simplifying concepts, rearranging the form of a text, and using as many or as few terms as necessary to communicate the original meaning as accurately as possible. To learn how to make Clear Translations, see [Create Clear Translations](../guidelines-clear/01.md). - -#### Natural - -Use language forms that are effective and that reflect the way your language is used in corresponding contexts. To learn how to make Natural Translations, see [Create Natural Translations](../guidelines-natural/01.md). +There are three main qualities of a good translation. It must be accurate, clear, and natural. We can think of each of these qualities as a leg of a three-legged stool. Each one is necessary. If one is missing, the stool will not stand. Likewise, each of these qualities must be present in a translation in order for it to be useful and faithful to the church. #### Accurate -Translate accurately, without detracting from, changing, or adding to the meaning of the original text as it would have been understood by the original audience. Translate with the meaning of the text in mind and communicate accurately the implicit information, unknown concepts, and figures of speech. To learn how to make Accurate Translations, see [Create Accurate Translations](../guidelines-accurate/01.md). +Translate accurately, without detracting from, changing, or adding to the meaning of the original text as it would have been understood by the original audience. One should remember that they are translating the very words of God. Therefore, a translation that is not accurate should not be considered to be Scripture. While absolute accuracy is not possible, a translation is the Word of God only to the extent that it accurately translates the meaning of the biblical text in its original languages. To learn how to make Accurate Translations, see [Accurate Translations](../guidelines-accurate/01.md). -#### Church-Affirmed +#### Clear -If a translation is clear, natural and accurate, but the church does not affirm it or accept it, then it does not achieve the final goal of edifying the church. It is important that the church be involved in the translation, checking, and distribution of the translation. To learn how to make church-affirmed translations, see [Create Church-Affirmed Translations](../guidelines-church-approved/01.md). +Use whatever language structures are necessary to achieve the highest level of comprehension while remaining faithful to the original meaning of the biblical text. Sometimes this involves using a different form to communicate the original meaning accurately. However, the translator should seek to make the minimal amount of changes necessary in order to make the text clear. To learn how to make Clear Translations, see [Clear Translations](../guidelines-clear/01.md). +#### Natural + +Translate in way that reflects how your language is used in corresponding contexts and that maintains the same effect on the target audience. To learn how to make Natural Translations, see [Natural Translations](../guidelines-natural/01.md). diff --git a/translate/guidelines-natural/01.md b/translate/guidelines-natural/01.md index 3baf0dc..b8d7742 100644 --- a/translate/guidelines-natural/01.md +++ b/translate/guidelines-natural/01.md @@ -1,14 +1,9 @@ -### Natural Translations - -To translate the Bible so that it is **natural** means that: - -The translation sounds like it was written by a member of the target group—not by a foreigner. Here are some ideas for making a natural translation: - +A **natural** translation is one that sounds like it was written by a member of the target group—not by a foreigner. Here are some ideas for making a natural translation. #### Write the Way Your People Talk -As you read the passage or chapter of the Bible ask yourself, "what kind of message is this?" This will help you to think of how to translate it naturally into the way that kind of message would be given in your language. +As you read the passage or chapter of the Bible, ask yourself, "What kind of message is this?" This will help you to think of how to translate it naturally into the way that kind of message would be given in your language. For example, if the passage is a poem, such as in the Psalms, then translate it in the form that your people will recognize as a poem. Or if the passage is an exhortation about the right way to live, such as in the New Testament letters, then translate it in a form that people in your language exhort each other. diff --git a/translate/guidelines-natural/title.md b/translate/guidelines-natural/title.md index 88fc0b8..bfe1aee 100644 --- a/translate/guidelines-natural/title.md +++ b/translate/guidelines-natural/title.md @@ -1,2 +1,2 @@ -Create Natural Translations +Natural Translations diff --git a/translate/guidelines-ongoing/sub-title.md b/translate/guidelines-ongoing/sub-title.md deleted file mode 100644 index f40009a..0000000 --- a/translate/guidelines-ongoing/sub-title.md +++ /dev/null @@ -1,2 +0,0 @@ -What are ongoing translations? - diff --git a/translate/guidelines-ongoing/title.md b/translate/guidelines-ongoing/title.md deleted file mode 100644 index 1026a65..0000000 --- a/translate/guidelines-ongoing/title.md +++ /dev/null @@ -1,2 +0,0 @@ -Create Ongoing Translations - diff --git a/translate/toc.yaml b/translate/toc.yaml index 440e048..a061598 100644 --- a/translate/toc.yaml +++ b/translate/toc.yaml @@ -12,26 +12,21 @@ sections: - title: "The Qualities of a Good Translation" link: guidelines-intro sections: - - title: "Create Clear Translations" - link: guidelines-clear - - title: "Create Natural Translations" - link: guidelines-natural - title: "Create Accurate Translations" link: guidelines-accurate - - title: "Create Church-Affirmed Translations" - link: guidelines-church-approved - - title: "Create Faithful Translations" - link: guidelines-faithful - - title: "Create Authoritative Translations" - link: guidelines-authoritative - - title: "Create Historical Translations" - link: guidelines-historical - - title: "Create Equal Translations" - link: guidelines-equal - - title: "Create Collaborative Translations" - link: guidelines-collaborative - - title: "Create Ongoing Translations" - link: guidelines-ongoing + sections: + - title: "Authoritative Translations" + link: guidelines-authoritative + - title: "Historical Translations" + link: guidelines-historical + - title: "Faithful Translations" + link: guidelines-faithful + - title: "Equal Translations" + link: guidelines-equal + - title: "Clear Translations" + link: guidelines-clear + - title: "Natural Translations" + link: guidelines-natural - title: "Before Translating" sections: - title: "Choosing a Translation Team" diff --git a/translate/translate-source-text/01.md b/translate/translate-source-text/01.md index 539288e..fbdb5ba 100644 --- a/translate/translate-source-text/01.md +++ b/translate/translate-source-text/01.md @@ -4,7 +4,7 @@ When choosing a source text, there are a number of factors that must be considered: * **[Statement of Faith](../../intro/statement-of-faith/01.md)** - Is the text in line with the Statement of Faith? -* **[Translation Guidelines](../../intro/translation-guidelines/01.md)** - Is the text in line with the Translation Guidelines? +* **[Accuracy](../../translate/guidelines-accurate/01.md)** - Is the text accurate? * **Language** - Is the text in a suitable language that translators and checkers understand well? * **[Copyrights, Licensing, and Source Texts](../translate-source-licensing/01.md)** - Is the text released under a license that gives sufficient legal freedom? * **[The Original and Source Languages](../translate-original/01.md)** - Does the translation team understand the difference between source languages and original languages?