See in Reader
Perry'sEdits3Q2019Process (#205)
This commit is contained in:
Perry J Oakes
Gogs
parent
2c95b9bddd
commit
eacb4c5943
|
|
@ -1,7 +1,7 @@
|
|||
|
||||
### Publishing Overview
|
||||
|
||||
Once a work has been uploaded to Door43, it is automatically available online under your user account. This is referred to as self-publishing. You will have access to a web version of your project at http://door43.org/u/user_name/project_name (where user_name is your username and project_name is your translation project). The translationStudio app will give you the correct link when you upload. You can also browse all works on http://door43.org.
|
||||
Once a work has been uploaded to Door43, it is automatically available online under your user account. This is referred to as self-publishing. You will have access to a web version of your project at http://door43.org/u/user_name/project_name (where user_name is your username and project_name is your translation project). Both translationStudio and translationCore will give you the correct link when you upload. You can also browse all works on http://door43.org.
|
||||
|
||||
From your Door43 project page you can:
|
||||
|
||||
|
|
@ -9,4 +9,7 @@ From your Door43 project page you can:
|
|||
* Download documents of your project (like a PDF)
|
||||
* Get the links to the source files (USFM or Markdown) for your project
|
||||
* Interact with others about your project
|
||||
* Continue to edit and improve your project and keep track of all changes
|
||||
|
||||
For more about distributing your project to others, see [Distribution](../intro-share/01.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,15 +1,21 @@
|
|||
|
||||
### Distribution Overview
|
||||
|
||||
Content is worthless unless it is disseminated and used. One advantage of using the Door43 translation and publishing platform is that it provides multiple, simple ways of distributing content.
|
||||
Biblical content is worthless unless it is distributed and used. One advantage of using the Door43 translation and publishing platform is that it provides multiple, simple ways of distributing content. On Door43:
|
||||
|
||||
* You can safely store your translation
|
||||
* People can see your translation
|
||||
* People can leave comments and suggestions to improve your translation
|
||||
* People can download your translation to read, print, and share with others
|
||||
|
||||
### Open License
|
||||
|
||||
The biggest factor that encourages distribution of content is the [Open License](../../intro/open-license/01.md) that is used for all content on Door43. This license gives everybody the freedom they need to:
|
||||
The biggest factor that enables distribution of content is the [Open License](../../intro/open-license/01.md) that is used for all content on Door43. This license gives everybody the freedom they need to:
|
||||
|
||||
* **Share** — copy and redistribute the material in any medium or format
|
||||
* **Adapt** — remix, transform, and build upon the material
|
||||
|
||||
for any purpose, even commercially.
|
||||
for any purpose, even commercial, without cost. "Freely you have received; freely give." (Matthew 10:8)
|
||||
|
||||
For ways to share your translations both online and offline, see [Sharing Content](../share-content/01.md).
|
||||
|
||||
Under the terms of the license.
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
|
||||
### Recommended Platform
|
||||
|
||||
The recommended platform for doing translation in the Door43 ecosystem is translationStudio (http://ufw.io/ts/). This is where the translation and checking teams will do their work. You may set up translationStudio on Android, Windows, Mac, or Linux devices, (see [Setting up translationStudio](../setup-ts/01.md) for more information).
|
||||
The recommended platform for drafting Bible translations in the Door43 ecosystem is translationStudio (http://ufw.io/ts/) and the recommended platform for checking Bible translations is translationCore (http://ufw.io/tc/). You may set up translationStudio on Android, Windows, Mac, or Linux devices (see [Setting up translationStudio](../setup-ts/01.md) for more information). You may set up translationCore on Windows, Mac, or Linux devices. These platforms are free to download and use. They import and export Bible books in USFM format.
|
||||
|
||||
### Other Options
|
||||
|
||||
If using translationStudio is not an option for your team, then you may consider using other online or offline tools. Note that it will be your responsibility to get the content into USFM or Markdown format if you do not use translationStudio (see [File Formats](../../translate/file-formats/01.md) for more information).
|
||||
If using translationStudio is not an option for your team, then you may consider using other online or offline tools. Note that it will be your responsibility to get the content into USFM format if you do not use translationStudio but do want to use other Bible translation software (see [File Formats](../../translate/file-formats/01.md) for more information).
|
||||
|
|
@ -1,4 +1,9 @@
|
|||
|
||||
### Before Checking
|
||||
|
||||
It is recommended that you consult the [Checking Manual](../../checking/intro-check/01.md) frequently as you check this content. Before you start checking, we recommend that you start working your way through the Checking Manual until you understand what is required at each level. As you work through the checking process, you will need to consult the Checking Manual frequently.
|
||||
It is recommended that you consult the [Checking Manual](../../checking/intro-check/01.md) frequently as you check your translation. Before you start checking, we recommend that you start working your way through the Checking Manual until you understand what is required for each check. As you work through the checking process, you will need to consult the Checking Manual frequently.
|
||||
|
||||
Some information that the translation team should know before you start checking:
|
||||
|
||||
* [Goal of Checking](../../checking/goal-checking/01.md) - What is the purpose of checking?
|
||||
* [Introduction to Translation Checking](../../checking/intro-checking/01.md) - Why do we need a team to check the translation?
|
||||
|
|
|
|||
|
|
@ -1,18 +1,20 @@
|
|||
|
||||
### What to Know Before Translation
|
||||
|
||||
It is recommended that you consult the [Translation Manual](../../translate/translate-manual/01.md) frequently as you translate this content. Before you start translating, we recommend that you start working your way through the Translation Manual at least until you know the difference between a literal translation and a meaning-based translation. Much of the rest of the Translation Manual can be used as a “just-in-time” learning resource.
|
||||
It is recommended that you consult the [Translation Manual](../../translate/translate-manual/01.md) frequently as you translate. Before you start translating, we recommend that you start working your way through the Translation Manual at least until you know the difference between a literal translation and a meaning-based translation. Much of the rest of the Translation Manual can be used as a “just-in-time” learning resource.
|
||||
|
||||
Some important subjects that must be learned before starting a translation project:
|
||||
Some important subjects that everyone on the translation team must learn before starting a translation project:
|
||||
|
||||
* [The Qualities of a Good Translation](../../translate/guidelines-intro/01.md) - The definition of a good translation
|
||||
* [The Translation Process](../../translate/translate-process/01.md) - How a good translation is made
|
||||
* [Form and Meaning](../../translate/translate-fandm/01.md) - The difference between form and meaning
|
||||
* [Meaning-Based Translations](../../translate/translate-dynamic/01.md) - How to make a meaning-based translation
|
||||
|
||||
Some other important topics as you get started include:
|
||||
Some other important topics as you get started also include:
|
||||
|
||||
* [Choosing What to Translate](../../translate/translation-difficulty/01.md) - Suggestions for where to start translating
|
||||
* [First Draft](../../translate/first-draft/01.md) - How to make a first draft
|
||||
* [Help with Translating](../../translate/translate-help/01.md) - Using translation helps
|
||||
|
||||
When you have [Set Up a Translation Team](../setup-team/01.md) and want to make a [First Draft](../../translate/first-draft/01.md) of your translation, use [translationStudio](../setup-ts/01.md). We recommend that you follow this [Translation Process](../translation-overview/01.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -5,4 +5,6 @@ Welcome to Bible translation! We are pleased that you desire to translate God's
|
|||
|
||||
### Getting Started
|
||||
|
||||
Translation is a very complex task that takes commitment, organization, and planning. There are many required steps to take a translation from an idea to a completed, checked, distributed, and in-use translation. The information in this Process Manual will help you to know all of the necessary steps in the translation process.
|
||||
Translation is a very complex task that takes commitment, organization, and planning. There are many required steps to take a translation from an idea to a completed, checked, distributed, and in-use translation. The information in this Process Manual will help you to know all of the necessary steps in the translation process.
|
||||
|
||||
Translating the Bible requires many skills, so one of the first things that you need to think about is how to [choose a team](../setup-team/01.md) that can do this work.
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
|
||||
### Purpose of Checking Levels
|
||||
|
||||
The purpose of the Checking Levels (see [Checking Manual](../../checking/intro-check/01.md)) is primarily to help ensure that the translation has been made in accordance with the [Statement of Faith](../../intro/statement-of-faith/01.md) and the [Translation Guidelines](../../intro/translation-guidelines/01.md). Another reason is to increase the input and ownership of the community that will be using it.
|
||||
|
||||
#### Checking Level 1
|
||||
|
||||
Checking Level 1 is done primarily by the translation team, with some input from the language community. See [Checking Level One - Affirmation by Translation Team](../../checking/level1/01.md). After completing the Level 1 Check, you are encouraged to upload to Door43 (see [Introduction to Publishing](../intro-publishing/01.md)) and continue on to Checking Level 2 (see below).
|
||||
|
||||
#### Checking Level 2
|
||||
|
||||
Checking Level 2 is done to verify that representative groups from the local language community agree that the translation is a good one (see [Checking Level Two - Affirmation by Community](../../checking/level2/01.md)). It is done with a language community check (see [Language Community Check](../../checking/language-community-check/01.md)) and a church leader check (see [Church Leader Check](../../checking/church-leader-check/01.md)). After completing the Level 2 Check, you are encouraged to upload to Door43 (see [Introduction to Publishing](../intro-publishing/01.md)) and continue on to Checking Level 3 (see below), if you so desire.
|
||||
|
||||
#### Checking Level 3
|
||||
|
||||
Checking Level 3 is done when leaders of at least two church networks agree that the translation is a good one (see [Checking Level Three - Affirmation by Church Leadership](../../checking/level3/01.md)). Be sure you work through the Level 3 Checking Questions (see [Questions for Checking on Level Three](../../checking/level3-questions/01.md)) while you complete this checking level. After completing the Level 3 Check, you are encouraged to upload to Door43 (see [Introduction to Publishing](../intro-publishing/01.md)). This is the highest checking level. Gateway Languages should also complete the [Source Text Process](../source-text-process/01.md)
|
||||
|
|
@ -1 +0,0 @@
|
|||
How do I check a translation?
|
||||
|
|
@ -1 +0,0 @@
|
|||
How to Check
|
||||
|
|
@ -0,0 +1,24 @@
|
|||
### How to Get translationCore
|
||||
|
||||
translationCore is open-source and open-licensed software that is free to use for checking Bible translations. The latest version of translationCore for desktop or laptop computers (Windows, Mac, or Linux) is available from http://translationcore.com/. To install the program, click on “Download” to get the latest release. Note that you may also copy the installation file to other computers to share translationCore with others without using the internet.
|
||||
|
||||
### How to Set Up translationCore
|
||||
|
||||
#### Log In
|
||||
To start, you will need to log in with a user name. If your translation is on Door43, use your Door43 user name. If you do not want to use the internet, then you can enter any name that you want to use, either real or a pseudonym.
|
||||
|
||||
#### Choose a Project
|
||||
If you logged in with your Door43 user name, translationCore will know which translations belong to you and will make them available to download into translationCore. You can choose which translation project you want to check from the list of your projects in Door43. You may also load translations that are on your computer without using the internet.
|
||||
|
||||
#### Choose a Tool
|
||||
translationCore contains three checking tools:
|
||||
|
||||
* [translationWords Tool](../../checking/important-term-check/01.md)
|
||||
* [translationNotes Tool](../../checking/trans-note-check/01.md)
|
||||
* [Alignment Tool](../../checking/alignment-tool/01.md)
|
||||
|
||||
Instructions for using each tool can be found by clicking on the name of the tool above.
|
||||
|
||||
### After Using translationCore
|
||||
|
||||
At any point, you may upload your work to [Door43](https://git.door43.org) by returning to the project list and clicking on the three-dot menu next to the project that you want to upload and choosing Upload to Door43. You can also export your project to a file on your computer. Once uploaded, Door43 will keep your work in a repository under your user name and you can access your work there (see [Publishing](../intro-publishing/01.md)).
|
||||
|
|
@ -0,0 +1 @@
|
|||
How do I set up translationCore?
|
||||
|
|
@ -0,0 +1 @@
|
|||
Setting Up translationCore
|
||||
|
|
@ -16,10 +16,14 @@ As you begin selecting a translation and checking team, there are many different
|
|||
|
||||
There are many decisions the translation team will have to make, many of them right at the beginning of the project. Included are the following:
|
||||
|
||||
* [Choosing What to Translate](../../translate/translation-difficulty/01.md) - Choosing what to translate first is another decision to be made
|
||||
* [Choosing a Source Text](../../translate/translate-source-text/01.md) - Choosing a good source text is very important
|
||||
* [Copyrights, Licensing, and Source Texts](../../translate/translate-source-licensing/01.md) - Copyright issues must be considered when choosing a source text
|
||||
* [Source Texts and Version Numbers](../../translate/translate-source-version/01.md) - Translating from the latest version of a source text is best
|
||||
* [Alphabet/Orthography](../../translate/translate-alphabet/01.md) - Many languages have alphabet decisions that need to be made
|
||||
* [Decisions for Writing Your Language](../../translate/writing-decisions/01.md) - Writing style, punctuation, translating names, spelling, and other decisions have to be made
|
||||
* [Translation Style](../../translate/choose-style/01.md) - The translation committee needs to agree on the style of the translation in the sense of how much they want it to imitate the form of the source, how much borrowing of words is allowed, and other topics. See also this section on making the translation [Acceptable](../../checking/acceptable/01.md).
|
||||
* [Choosing What to Translate](../../translate/translation-difficulty/01.md) - Books should be chosen based on the needs of the church and the difficulty of translation
|
||||
|
||||
After the translation committee makes these decisions, it is good to write them down in a document that everyone involved in the translation can read. This will help everyone to make similar translation decisions and will avoid further arguments about these things.
|
||||
|
||||
After choosing the translation team, it will be time to start giving them [Translation Training](../pretranslation-training/01.md).
|
||||
|
|
@ -1,21 +1,21 @@
|
|||
|
||||
### Installing tS for Mobile
|
||||
|
||||
The mobile (Android) edition of translationStudio is available from the [Google Play Store](https://play.google.com/store/apps/details?id=com.translationstudio.androidapp ) or via direct download from http://ufw.io/ts/. If you install from the Play Store, then you will be notified by the Play Store when a new version is available. Note that you may also side load the installation apk to other devices to share the app.
|
||||
The mobile (Android) edition of translationStudio is available from the [Google Play Store](https://play.google.com/store/apps/details?id=com.translationstudio.androidapp ) or via direct download from http://ufw.io/ts/. If you install from the Play Store, then you will be notified by the Play Store when a new version is available. Note that you may also copy the installation file (apk) to other devices to share translationStudio with others without using the internet.
|
||||
|
||||
### Installing tS for Desktop
|
||||
|
||||
The latest version of translationStudio for desktop or laptop computers (Windows, Mac, or Linux) is available from http://ufw.io/ts/. To install the program, navigate to the “Desktop” section and download the latest release. Note that you may also copy the installation file to other computers to share the app.
|
||||
The latest version of translationStudio for desktop or laptop computers (Windows, Mac, or Linux) is available from http://ufw.io/ts/. To install the program, navigate to the “Desktop” section and download the latest release. Note that you may also copy the installation file to other computers to share translationStudio with others without using the internet.
|
||||
|
||||
### Using tS
|
||||
|
||||
Once installed, both editions of translationStudio are designed to work similarly. You *do not* need an internet connection to use translationStudio! First-time use of translationStudio will require an agreement to the [Statement of Faith](../../intro/statement-of-faith/01.md), the [Translation Guidelines](../../intro/translation-guidelines/01.md), and the [Open License](../../intro/open-license/01.md).
|
||||
|
||||
After the first-use screen, you will be brought to the Home screen where you can create a new project. Once your project is created, you may start translating right away. There are translationHelps built right into the app which you are encouraged to use to gain a better understanding of the source text. Note that your work is automatically saved. You may also choose to back up, share, or upload your work at various intervals (use the menu to access these functions).
|
||||
After the first-use screen, you will be brought to the Home screen where you can create a new project. You will need to give the project a name (usually a book of the Bible), identify the project type (usually Bible or Open Bible Stories), and identify the target language. Once your project is created, you can start translating. Make sure that you understand the [Principles of Good Translation](../pretranslation-training/01.md) and know how to use the [Translation Helps](../../translate/translate-help/01.md) that are built into translationStudio. These will help you to gain a better understanding of the source text and how to translate it. Note that your work is automatically saved. You may also choose to back up, share, or upload your work at various intervals (use the menu to access these functions). For guidelines on how to start translating, see [Translation Overview](../translation-overview/01.md) and [Making a First Draft](../../translate/first-draft/01.md).
|
||||
|
||||
### After Using tS
|
||||
|
||||
1. We strongly recommend that your translation be checked (see [Training Before Checking Begins](../prechecking-training/01.md)).
|
||||
1. Once the checking is complete (to any level), you may upload your work from the app (Menu → Upload).
|
||||
1. Once uploaded, you can see your work online on Door43 (see [Publishing](../intro-publishing/01.md))
|
||||
1. Make sure that you have a translation team that can help you check your work (see [Training Before Checking Begins](../prechecking-training/01.md)).
|
||||
1. At any point, you may upload your work to [Door43](https://git.door43.org) by clicking on the three-dot menu and choosing Upload/Export. You will need to create a user name on Door43.
|
||||
1. Once uploaded, Door43 will keep your work in a repository under your user name and you can access your work there (see [Publishing](../intro-publishing/01.md)).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
|
||||
### Sharing Content from tS
|
||||
### Sharing Content from tS and tC
|
||||
|
||||
Sharing content that is in translationStudio is easy. For offine sharing, use the Backup feature from the tS menu. For online sharing, use the Upload feature from the tS menu.
|
||||
Sharing content that is in translationStudio is easy. For offine sharing, use the Backup feature from the tS menu. For online sharing, use the Upload feature from the tS menu. In translationCore, use the three-dot menu on the Projects page. For offline sharing, use either Export to USFM or Export to CSV. For online sharing, use Upload to Door43.
|
||||
|
||||
### Sharing Content on Door43
|
||||
|
||||
If you upload your work from translationStudio, then it automatically appears on the Internet on Door43. All of your uploaded content will appear under your user account. For example, if your username is *test_user* then you may find all your work at http://door43.org/u/test_user/. You can share your work with others online by giving them the link to the projects you have uploaded.
|
||||
If you upload your work from translationStudio or translationCore, then it automatically appears on the Internet on Door43. All of your uploaded content will appear under your user account. For example, if your username is *test_user* then you may find all your work at http://door43.org/u/test_user/. You can share your work with others online by giving them the link to the projects you have uploaded.
|
||||
|
||||
### Sharing Content Offline
|
||||
|
||||
|
|
|
|||
|
|
@ -1,33 +0,0 @@
|
|||
|
||||
### Source Text Process
|
||||
|
||||
Source text publishing is required for all Gateway Languages so that they can be used as source texts by Other Languages. Note that this process only applies to Gateway Languages.
|
||||
|
||||
#### Prerequisites
|
||||
|
||||
Before a Gateway Language translation can become a source text, the following prerequisites must all be met:
|
||||
|
||||
* **Whole Resource** - The whole resource must be translated and checked to the required level. Parts of resources (e.g. half of the Open Bible Stories, only a few chapters of a book of the Bible) cannot be published.
|
||||
* **Checking** - A translation must have reached the appropriate checking level. For Bible translations, that means [Checking Level Three - Affirmation by Church Leadership](../../checking/level3/01.md).
|
||||
* **On Door43** - Door43 must have the version that will be published. If the work was done on multiple devices, then it may need to be merged together. Get the help of a Content Tech to make merging easier (either email <help@door43.org> or use the #content-techs channel on Slack).
|
||||
* **Agreements** - Everyone involved in the translation and checking must have agreed to the [Statement of Faith](../../intro/statement-of-faith/01.md), the [Translation Guidelines](../../intro/translation-guidelines/01.md), and the [Open License](../../intro/open-license/01.md). This can be done by either creating Door43 accounts or by physically signing the documents and digitizing them (scanning or photos). See http://ufw.io/forms for downloadable agreement forms.
|
||||
|
||||
|
||||
#### Source Text Request Form
|
||||
|
||||
Once you have the prerequisites, you may fill out the source text request form at http://ufw.io/pub/. A few notes about the form:
|
||||
|
||||
* You must have a Door43 account to create a request.
|
||||
* You must include the names or pseudonyms of everyone involved. You must also include their Door43 usernames if you are not attaching signed license agreements for them.
|
||||
* Note that the information you enter will be public and will become a part of the front matter of the source text.
|
||||
|
||||
After your form has been submitted, you will be contacted if anything is missing. Once the request has been approved, it will go into the publishing queue where a developer will work to make the translation a source text. You may also be contacted by the developer if there are any issues encounted during the publishing process. You will be notified when the process is completed and you may review a PDF of the work.
|
||||
|
||||
### Finishing the Source Text Process
|
||||
|
||||
After the source text publishing process is completed, your work will then be available:
|
||||
|
||||
* Online on the unfoldingWord website
|
||||
* As a PDF, downloadable from unfoldingWord
|
||||
* In translationStudio as a source text for Other Languages to use (may require a tS update first)
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
How do I make my Gateway Language translation a source text?
|
||||
|
|
@ -1 +0,0 @@
|
|||
Source Text Process
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
### OL Translation Process
|
||||
|
||||
For "Other Languages" (OLs, languages other than Gateway Languages), which are most of the languages of the world, the following is the process of translation that unfoldingWord recommends and supports with translation resources and tools.
|
||||
|
||||
After [Setting up a Translation Committee](../setup-team/01.md) and training translators in [Translation Principles](../pretranslation-training/01.md) and how to use [translationStudio](../setup-ts/01.md), we recommend that you follow this process:
|
||||
|
||||
1. Using translationStudio, make a [First Draft](../../translate/first-draft/01.md) translation of a story from Open Bible Stories (OBS).
|
||||
2. Check the translation with a [Partner](../../checking/peer-check/01.md) on your translation team.
|
||||
3. Check the translation with the [Full Translation Team](../../checking/team-oral-chunk-check/01.md).
|
||||
4. Check the translation using the [translationNotes](../../checking/trans-note-check/01.md) and [translationWords](../../checking/important-term-check/01.md).
|
||||
5. Check the translation with the [Language Community](../../checking/language-community-check/01.md).
|
||||
6. Check the translation with [Pastors from the Language Community](../../checking/church-leader-check/01.md).
|
||||
7. Check the translation with [Leaders of Church Networks](../../checking/level3/01.md).
|
||||
8. [Publish](../intro-publishing/01.md) the translation on Door43, in print, and in audio, as desired.
|
||||
|
||||
Repeat these steps with each story of Open Bible Stories, until you have finished all fifty.
|
||||
|
||||
After finishing Open Bible Stories, you will have gained enough skill and experience to start translating the Bible. We recommend that you start with a book that is [Difficulty Level 2](../../translate/translation-difficulty/01.md). Then follow this process:
|
||||
|
||||
1. Using translationStudio, make a [First Draft](../../translate/first-draft/01.md) translation of a book of the Bible.
|
||||
2. Check the translation with a [Partner](../../checking/peer-check/01.md) on your translation team.
|
||||
3. Check the translation with the [Full Translation Team](../../checking/team-oral-chunk-check/01.md).
|
||||
4. Check the translation using the [translationNotes](../../checking/trans-note-check/01.md) and [translationWords](../../checking/important-term-check/01.md) tools in [translationCore](../setup-tc/01.md).
|
||||
5. Check the translation with the [Language Community](../../checking/language-community-check/01.md).
|
||||
6. Check the translation with [Pastors from the Language Community](../../checking/church-leader-check/01.md).
|
||||
7. Align the translation with the original languages using the [Aligning Tool](../../checking/alignment-tool/01.md) in [translationCore](../setup-tc/01.md).
|
||||
8. Check the translation with [Leaders of Church Networks](../../checking/level3/01.md).
|
||||
9. [Publish](../intro-publishing/01.md) the translation on Door43, in print, and in audio, as desired.
|
||||
|
||||
Repeat these steps with each Bible book.
|
||||
|
||||
Plan to have someone from the translation team continue to maintain the translation on [Door43](http://git.door43.org), editing it to correct errors and improve it according to suggestions from the church community. The translation can easily be downloaded and reprinted as often as desired.
|
||||
|
|
@ -0,0 +1 @@
|
|||
What is the process for translation that unfoldingWord recommends?
|
||||
|
|
@ -0,0 +1 @@
|
|||
unfoldingWord Translation Process
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
### Choose the Translation Style
|
||||
|
||||
Before beginning a translation of the Bible, the translation committee needs to discuss and agree on the style that they want the translation to have. The following topics should be included in the discussion.
|
||||
|
||||
1. **Form** – Should the translation follow the form of the source language so that people who are used to hearing and reading the Bible in the source language will feel more comfortable with it, or should the translation follow the form of the target language, and be easier to understand? We recommend that, in most cases, it is better if the translation follows the form of the target language so that people can understand it better. This means that it will be harder to compare with the source language Bible because it will put things in a different order and use different kinds of expressions that are clear and natural in the target language. But when a Bible is clear and natural, many people will want to read it and hear it, not just the people who have been part of the church for many years.
|
||||
|
||||
2. **Borrowing** – Should the translation borrow many words from the source language, or should the translators find ways to express these things using target language words? People who have been part of the church for many years may be used to hearing many biblical concepts expressed with source language words. If these words are widely understood outside of the church, then it may be fine to use them in the translation. But if people outside of the church do not understand these words, it would be better to find ways to express these things using target language words.
|
||||
|
||||
3. **Old Words** - Should the translation use words that only the old people know, or should it use words that everyone knows? Sometimes there is a good target language word for something, but the young people do not use it or know it. The translation committee can decide if they should use this word and teach it to the young people, or use a word borrowed from the source language, or express the same concept using a phrase or description using target language words that everyone knows.
|
||||
|
||||
4. **Register** – If the target language has different registers or levels of the language, which one should the translation use? For example, if people of high status use one form of the target language and people of low status use a different form, which one should the translation use? Or if the target language has different words for “you” or uses different words to address a government official in contrast with someone who is a close family member, which should the translation use to address God? Thinking about the topic of **Audience** may also help to decide these questions.
|
||||
|
||||
5. **Audience** - The translation committee should discuss who is the audience for this translation. Is it primarily educated people, so they should use a style that uses long sentences and many borrowed words? Is it primarily for young people, or old people, for men or women? Or is it for everyone? In that case, it should use simple language so that everyone can understand it. For more on this topic, see also [Aim](../translate-aim/01.md).
|
||||
|
||||
6. **Footnotes** – Should the translation put explanations of difficult things in footnotes? If so, should it use many footnotes, or only for certain topics or especially difficult things? Will people understand what they are and how they work, or will they be confused by them? Instead of footnotes, would it be better to put short explanations in the text of the Bible translation? Or should the translation not include any extra explanations at all?
|
||||
|
||||
7. **Headings** – Should the translation use section headings that summarize what each section is talking about? These can be very helpful for finding different topics. If so, what style of headings should be used? See [Headings](../../checking/headings/01.md) for examples.
|
||||
|
|
@ -0,0 +1 @@
|
|||
What are the topics that we need to discuss in order to choose a translation style?
|
||||
|
|
@ -0,0 +1 @@
|
|||
Choosing a Translation Style
|
||||
|
|
@ -15,6 +15,8 @@ This committee can also choose the pastors and other leaders who will check the
|
|||
|
||||
When it comes time, this committee can also make decisions about the format of the translation, how it will be distributed, and they can encourage the churches to use the translated Scriptures.
|
||||
|
||||
This committee should also plan for the maintenance of the translation after it has been translated and distributed. They may want to appoint someone to review the comments and suggestions for improvement that will come from the churches that use the translation. Door43 provides a place for people to access the translation and also to leave these kinds of comments.
|
||||
|
||||
#### Translators
|
||||
|
||||
These are the people who will do the work of making the translation drafts. They will be appointed by the Translation Committee. They need to be people who are native speakers of the target language, who can read the source language (the Gateway Language) very well, and who are respected in the community for their Christian character. For more details about these things, see [Translator Qualifications](../qualifications/01.md).
|
||||
|
|
|
|||
|
|
@ -10,16 +10,17 @@ Follow these steps in order to get started:
|
|||
1. **Pray.** Pray that God would help you to understand the passage that you are translating and that he would help you to find the best way to communicate that passage in your language.
|
||||
1. **Read.**
|
||||
* If you are translating Open Bible Stories, read the entire story before starting to translate it. If you are translating the Bible, read the entire chapter before you start to translate any part of it. This way you will understand how the part you are translating fits into the larger context, and you will translate it better.
|
||||
* Read the passage that you plan to translate in as many different translations as you have. If you are using translationStudio, it contains at least two Bible texts, the unfoldingWord Literal Text (ULT) and the unfoldingWord Simplified Text (UST). The ULT will help you to see the form of the original text, and the UST will help you to understand the meaning of the original text. Think about how to communicate the meaning in the form that people would use in your language.
|
||||
* Read the passage that you plan to translate in as many different translations as you have. In [translationStudio](../../process/setup-ts/01.md), the first mode is the reading mode. Access this mode by clicking on the top symbol on the left side. You can choose up to three translations to show in this mode. We recommend that two of these be the unfoldingWord Literal Text (ULT) and the unfoldingWord Simplified Text (UST). The ULT will help you to see the form of the original text, and the UST will help you to understand the meaning of the original text. Think about how to communicate the meaning in the form that people would use in your language.
|
||||
* Read any Bible helps or commentaries that you have that talk about that passage.
|
||||
* Read the translationNotes for the passage that you plan to translate.
|
||||
* Read the definitions of important terms in the list called “translationWords” for each highlighted word in the passage that you plan to translate.
|
||||
* Read the translationNotes for the passage that you plan to translate. To do this, click on the third icon down on the left side of translationStudio. Click on the tab that says, "Notes." Then click on each of the phrases in blue and read the explanation for each phrase.
|
||||
* Read the definitions of the translationWords (the important words) in the passage. To do this, click on the tab that says, "Words." Then click on each of the words in blue and read the explanation for each of these important words. Under each explanation there is also a section called "Translation Suggestions." Here you will find ideas for how to translate these words.
|
||||
1. **Talk.** Discuss the passage, the translationNotes, and the translationWords with others in the translation team. Help each other to understand what they mean. If there are parts that you still do not understand, ask pastors or other church leaders for help.
|
||||
2. **Translate.** When you understand well what the passage is saying, say the first chunk (1-3 verses) out loud in your language in the way that someone from your language community would say it. If possible, say it to another member of the translation team. Let the translation team member correct it until it sounds good in your language. Do not follow the order of words from the source text if it is more natural for your language to use a different order. To help with this, say the whole chunk of text without looking at the source text. This will help you to say these things in a way that is natural for your language, rather than in a way that was natural for the source language but that is not the best way to say it in your language. Still without looking at the source text, type your translation of the chunk into translationStudio (or record it). When you type (or write) from your memory without looking at the source text, your translation will be more natural.
|
||||
1. **Check**. Since you typed or recorded your translation of a chunk without looking at the source text, you might have left out a few things. Now is the time to add those things to your translation.
|
||||
* Look again at the source text and carefully compare it to your translation. Make sure that it says all of the parts of the message of the source text and does not leave out anything. If some part of the message was missing, put it in your translation at the point where it fits best in your language. It does not need to be in the same order as the source as long as it sounds natural and gives the same meaning.
|
||||
2. **Translate.** When you understand well what the passage is saying, say the first chunk (1-3 verses) out loud in your language in the way that someone from your language community would say it. If possible, say it to another member of the translation team. Let the translation team member correct it until it sounds good in your language. Do not follow [the order of words](../translate-wforw/01.md) from the source text if it is more [natural](../guidelines-natural/01.md) for your language to use a different order. To help with this, say the whole chunk of text without looking at the source text. This will help you to say these things in a way that is natural for your language, rather than in a way that was natural for the source language but that is not the best way to say it in your language. Still without looking at the source text, type your translation of the chunk into [translationStudio](../../process/setup-ts/01.md) (or record it). To do this, click on the second icon down on the left side. The chunk that you are working on will appear, covering the space where you will type the translation. When you are ready to type, click on the right edge of the space that is mostly covered by the source text of the passage. The blank space will then cover the source text. Type you translation of the chunk here in this space from your memory. When you type (or write) from your memory without looking at the source text, your translation will be more natural. Now repeat this step for the rest of the chunks of this passage.
|
||||
1. **Check**. Since you typed or recorded your translation of these chunks without looking at the source text, you might have left out a few things. Now is the time to add those things to your translation. Click on the third icon down on the left side of translationStudio again. In that mode:
|
||||
* Look again at the source text and carefully compare it to your translation. Make sure that it says all of the parts of the message of the source text and does not leave out anything. If some part of the message was missing, put it in your translation at the point where it fits best in your language. It does not need to be in the same order as the source as long as it sounds natural and gives the same meaning. To do this in translationStudio, click on the pencil icon on the top right above your translation.
|
||||
* If you are translating the Bible, compare your translation with other translations of the same Bible passage. If one of those makes you think of a better way to say something, then revise your translation in that way. If one of those helps you to understand something better than you did before, then change your translation so that it communicates the meaning better.
|
||||
* After these steps, read your translation out loud to yourself. Fix anything that does not sound like it is the way that someone from your community would say it. Sometimes parts of sentences need to be put in a different order.
|
||||
* In translationStudio, exit editing mode by clicking the check mark icon at the top right of your translation. Now it is time to move the verse numbers where they should be in your translation. Drag each number onto the word that will begin that verse. If your translation has reordered the parts of the chunk or combined verses, you can leave some verse numbers together to indicate that what follows includes content from both of those verses.
|
||||
|
||||
Now translate the next chunk of the passage in the same way (step 8) and check it in the same way (step 9). When you finish the passage or chapter, it is ready for the [Oral Partner Check](../../checking/peer-check/01.md). To translate the next passage or chapter, start again at step 5.
|
||||
When you finish the passage or chapter, it is ready for the [Oral Partner Check](../../checking/peer-check/01.md). To translate the next passage or chapter, start again at step 5.
|
||||
|
||||
Loading…
Reference in New Issue