See in Reader
Changing tS to BTT Writer
This commit is contained in:
parent
29c6ab2e2b
commit
6cbf2105f4
|
|
@ -7,7 +7,7 @@
|
|||
* You may choose a word with an added descriptor.
|
||||
* You may choose the common use word from the local Christian community.
|
||||
* You may choose a simple equivalent from every-day language use.
|
||||
* Use the list of words and definitions in the Translation Words resource available on bibleineverylanguage.org and translationStudio to help you to make a list of these words and to understand what they mean. Your own list may include additional words, but be careful not to include too many words. If the list is too detailed, checking becomes tedious. Additionally, checking every (or almost every word) can push the translated material away from natural flow in the target language. Remember, key words are ones of significance, packed with essential meaning and are often difficult to directly translate.
|
||||
* Use the list of words and definitions in the Translation Words resource available on bibleineverylanguage.org and BTT Writer to help you to make a list of these words and to understand what they mean. Your own list may include additional words, but be careful not to include too many words. If the list is too detailed, checking becomes tedious. Additionally, checking every (or almost every word) can push the translated material away from natural flow in the target language. Remember, key words are ones of significance, packed with essential meaning and are often difficult to directly translate.
|
||||
* It is best if you can create a chart so that you can list the source word or phrase in one column and the target word or phrase in another column. Further columns could list equivalent terms in other languages and the references where these terms occur in the Bible. It is ideal if everyone translating Bible books that use these terms has access to the chart so that you can all use the same words or phrases in your translation.
|
||||
* Each time the key word occurs in the source text, make sure that the term you have chosen for the translation still makes sense in that context. If it does not, discuss the problem with others on the translation team and try to find a solution together. You may need to use a different term, or you may need to use more than one term for the different contexts, or you may need to find another way to communicate the key word that includes all of the meanings, such as using a longer phrase.
|
||||
* When you have decided that you need to use different target language words or phrases to translate one source language key word in different contexts, then make a new line on the chart for each different way that you are translating the source word. Repeat the source term in the source column, and put the new translation in the next column, under the first translation. If possible, share this chart with everyone on the translation team so that they can choose the right translation for the source word in the context that they are translating.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
|
||||
* If you have followed the first for steps of the MAST process, then you made your first draft of a passage by consuming the source text, verbalizing what you consumed, breaking it down into workable chunks, and then writing it down while you were not looking at the source text. After you have translated a passage in this way, do a self-edit by looking again at the source text and comparing it to your translation. Make sure that your draft includes all the parts of the message of the source text and does not leave out anything. If some part of the message is missing, put it in your translation at the point where it fits best in your language. Also make sure you haven't included any extra information.
|
||||
* If possible, 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.
|
||||
* If possible use the Translation Notes and Translation Questions as well as other tools available in translationstudio and Bibleineverylanguage.org to check your work.
|
||||
* If possible use the Translation Notes and Translation Questions as well as other tools available in BTT Writes and Bibleineverylanguage.org to check your work.
|
||||
* 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.
|
||||
When you have completed these steps, you are ready to have a peer edit your work.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Order the information in a way that will be clear to your readers.
|
|||
|
||||
1. If you put information from one verse before information from an earlier verse, put the first and last verse numbers at the beginning with a hyphen between them.
|
||||
|
||||
See how to mark verses in the [translationStudio APP](http://help.door43.org/en/knowledgebase/13-translationstudio-android/docs/24-marking-verses-in-translationstudio).
|
||||
See how to mark verses in the [BTT Writer APP](https://btt-writer.readthedocs.io/en/latest/).
|
||||
|
||||
### Examples of Translation Strategy Applied
|
||||
|
||||
|
|
|
|||
|
|
@ -22,11 +22,11 @@ To read more about USFM notation, please read http://paratext.org/about/usfm .
|
|||
|
||||
#### How To Do a Bible Translation in USFM
|
||||
|
||||
Most people do not know how to write using USFM markers. This is one of the reasons why translationStudio was created. When you do a translation in translationStudio, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from translationStudio, what is being uploaded is already formatted in USFM.
|
||||
Most people do not know how to write using USFM markers. This is one of the reasons why BTT Writer was created. When you do a translation in BTT Writer, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from BTT Writer, what is being uploaded is already formatted in USFM.
|
||||
|
||||
#### Converting a Translation to USFM
|
||||
|
||||
Though it is strongly encouraged to only do a translation using USFM markers, sometimes a translation is done without using USFM. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into translationStudio, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in translationStudio or some other program that uses USFM markers.
|
||||
Though it is strongly encouraged to only do a translation using USFM markers, sometimes a translation is done without using USFM. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into BTT Writer, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in BTT Writer or some other program that uses USFM markers.
|
||||
|
||||
### Conclusion
|
||||
|
||||
|
|
|
|||
|
|
@ -24,11 +24,11 @@ INSERT IMAGE of John 1:1-2 with the chapter number/
|
|||
|
||||
#### How To Do a Bible Translation in USFM
|
||||
|
||||
Most people do not know how to write using USFM markers. This is one of the reasons why translationStudio was created. When you do a translation in translationStudio, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from translationStudio, what is being uploaded is already formatted in USFM.
|
||||
Most people do not know how to write using USFM markers. This is one of the reasons why BTT Writer was created. When you do a translation in BTT Writer, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from BTT Writer, what is being uploaded is already formatted in USFM.
|
||||
|
||||
#### Converting a Translation to USFM
|
||||
|
||||
Though it is strongly encouraged to only do a translation using USFM markers, sometimes a translation is done without using USFM. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into translationStudio, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in translationStudio or some other program that uses USFM markers.
|
||||
Though it is strongly encouraged to only do a translation using USFM markers, sometimes a translation is done without using USFM. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into BTT Writer, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in BTT Writer or some other program that uses USFM markers.
|
||||
|
||||
### Conclusion
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
Bible translations should be **ongoing**. Share the translation with others to see if they understand the meaning of the message. Improve your translation with their input. Revising a translation to increase understanding and accuracy is always a good idea. Whenever someone has a good idea for making the translation better, you should edit the translation to incorporate that change. When you use translationStudio or other electronic text editors, you can keep this process of revision and improvement ongoing.
|
||||
Bible translations should be **ongoing**. Share the translation with others to see if they understand the meaning of the message. Improve your translation with their input. Revising a translation to increase understanding and accuracy is always a good idea. Whenever someone has a good idea for making the translation better, you should edit the translation to incorporate that change. When you use BTT Writer or other electronic text editors, you can keep this process of revision and improvement ongoing.
|
||||
|
||||
* Reviewers are needed who can read the translation and point to text that needs revision.
|
||||
* Have people read the translation or listen to a recording of the translation. This will help you know if the translation has the same impact in your community that it had among the original audience (for example: giving comfort, encouragement, or guidance).
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ In some versions this is the last verse of Daniel 5. In other versions this is t
|
|||
|
||||
### Translation Strategies
|
||||
|
||||
1. If the people who speak your language have another Bible that they use, number the chapters and verses the way it does. Read the instructions on how to mark verses in the [translationStudio APP](http://help.door43.org/en/knowledgebase/13-translationstudio-android/docs/24-marking-verses-in-translationstudio).
|
||||
1. If the people who speak your language have another Bible that they use, number the chapters and verses the way it does. Read the instructions on how to mark verses in the [BTT Writer APP](https://btt-writer.readthedocs.io/en/latest/).
|
||||
|
||||
### Examples of Translation Strategies Applied
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue