DCS-Mirror
/
unfoldingWord_en_glm
mirror of https://git.door43.org/unfoldingWord/en_glm
2
0
Fork 0
Files Issues Releases Wiki Activity See in Reader

Several editing updates (#9)

This commit is contained in:
Jesse Griffin 2018-06-08 15:04:18 +00:00 committed by Gogs
parent a51315163d
commit 030839329c
7 changed files with 318 additions and 267 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

88
docs/gl_alignment.rst Normal file
View File

@ -0,0 +1,88 @@
:github_url: https://git.door43.org/unfoldingWord/en_glm/src/branch/master/docs/gl_alignment.rst
.. _glalignment:
Gateway Language Alignment
==========================
.. note:: This module answers the question, "How do I align my GL translation in tC?"
The purpose of the aligning tool in translationCore (tC) is to create highlighting that will appear for the :abbr:`OL (Other Language)` translator who will use the :abbr:`GL (Gateway Language)` text as a source text for an :abbr:`OL (Other Language)` translation. This highlighting will show the user of the :abbr:`GL (Gateway Language)` text how that :abbr:`GL (Gateway Language)` text represents the meaning of the original biblical language text.
When the :abbr:`OL (Other Language)` translator uses the :abbr:`tW (translationWords)` or :abbr:`tN (translationNotes)` tools in :abbr:`tC (translationCore)`, the aligned :abbr:`GL (Gateway Language)` text will allow :abbr:`tC (translationCore)` to highlight the word or phrase that the :abbr:`tC (translationCore)` check is talking about in both the original biblical language and the :abbr:`GL (Gateway Language)`. This will help the :abbr:`OL (Other Language)` translator to see how the biblical language expressed that meaning, how the :abbr:`GL (Gateway Language)` expressed that meaning, and how he might express that same meaning in the target language.
So as you align the :abbr:`GL (Gateway Language)` text with the original language text, your job is to match as accurately as possible the words of the :abbr:`GL (Gateway Language)` text to the words of the original text that express the same meaning.
.. seealso:: Always check to make sure you are using the latest version of tC, which is available from http://translationcore.com. Please also read the `Release Notes <https://github.com/unfoldingWord-dev/translationCore/releases/latest>`_ for the most up to date instructions.
General Aligning Instructions
-----------------------------
In the :abbr:`tC (translationCore)` Word Alignment tool, the :abbr:`GL (Gateway Language)` chapters and verses are listed down the left side. When you click on a verse to open it, the words of that verse appear in a vertical list, ordered from top to bottom, just to the right of the list of chapters and verses. Each word is in a separate box.
The words of the original language (Greek, Hebrew, or Aramaic) text for that verse are also in separate boxes in a field to the right of the :abbr:`GL (Gateway Language)` word list. There is a space under each of the source word boxes outlined with a dotted line.
To align the :abbr:`GL (Gateway Language)` text:
#. Click and drag each word box of the :abbr:`GL (Gateway Language)` text into the space under the word box of the source text that the :abbr:`GL (Gateway Language)` word corresponds to.
#. Drop the :abbr:`GL (Gateway Language)` word by releasing the mouse button.
When the :abbr:`GL (Gateway Language)` word is over a word box of the original, the dotted outline will turn blue to let you know that the word will drop there. If you make a mistake or decide that the :abbr:`GL (Gateway Language)` word belongs somewhere else, simply drag it again to where it belongs. :abbr:`GL (Gateway Language)` words can also be dragged back to the list.
When the same :abbr:`GL (Gateway Language)` word occurs more than once in a verse, each instance of the word will have a small superscript number after it. This number will help you to align each repeated :abbr:`GL (Gateway Language)` word to the correct original word in the correct order.
Merge and Unmerge Notes
^^^^^^^^^^^^^^^^^^^^^^^
:abbr:`tC (translationCore)` supports one-to-one, one-to-many, many-to-one, and many-to-many alignments. That means that one or more :abbr:`GL (Gateway Language)` words can be aligned to one or more original language words, as necessary to get the most accurate alignment of the **meaning** conveyed by the two languages.
* To align multiple :abbr:`GL (Gateway Language)` words to a single original language word, simply drag and drop the :abbr:`GL (Gateway Language)` words onto the box below the desired original language word.
* When it is desired to align :abbr:`GL (Gateway Language)` word(s) to a combination of original language words, first drag one of the combination original language words into the same box as the other original language word. Multiple original language words can be merged together in this fashion.
* To unmerge previously merged original language words, drag the rightmost original language word slightly to the right. A small new alignment box will appear, and the unmerged word can be dropped into that box.
* The leftmost original language word can also be unmerged by dragging and dropping it into the original language word box immediately to its left.
* Any :abbr:`GL (Gateway Language)` words that were aligned with that original language word return to the word list.
* The original language words should remain in the proper order. If the merge contains 3 or more original language words, unmerge the rightmost original language word first. Un-merging the center word(s) first may result in the original language words becoming out of order. When that happens, unmerge the remaining words in that box to properly return the original language words to their original order.
Alignment Philosophy
--------------------
Because each :abbr:`GL (Gateway Language)` will have different requirements for sentence structure and the amount of exclipit information that must be provided there is often not a one-to-one correspondence of the original language word and the :abbr:`GL (Gateway Language)` word. In these cases, the :abbr:`GL (Gateway Language)` words that are provided should be aligned with the original language word that implies them.
For English, we follow these principles, but your :abbr:`GL (Gateway Language)` may need a different list to support full alignment.
* Align indefinite articles to their “head word.” For example, both “a” and “servant” should align to *doulos* in Titus 1:1.
* Definite articles that English supplies should also be aligned to their “head word.” For example, both “the” and “faith” should align to *pistin* in Titus 1:1.
* Original language definite articles that English does not use need to be combined with their original language head word. For example, *ton* and *logon* need to be combined, then “word” aligned with that combination in Titus 1:3.
* Implicit verbs in the original language that are translated explicitly in the target language should be aligned with the predicate. For example, “he should be” that is supplied in English should be aligned to *philoxenon* along with “hospitable” in Titus 1:8.
* Words with apostrophes will be split and show up as two words in the word panel. This allows for proper alignment of the two parts of meaning. In most cases in English these are used to represent possession and will be aligned to a single original language word in the genitive case. For example, both “God” and “s” will align to *theou* in Titus 1:1.
* Often the original language and :abbr:`GL (Gateway Language)` part of speech won’t match. That is inevitable. Often an original language word will be translated as a :abbr:`GL (Gateway Language)` phrase. For example, the three words “does not lie” in English all align with the single word *apseudes* in Titus 1:2.
Alignment Philosophy for the ULT
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The :abbr:`ULT (unfoldingWord Literal Text)` is intended to be a fairly literal translation of the original, so that it reproduces the structure of the original language when that is also understandable in the :abbr:`GL (Gateway Language)`. Ideally, then, there would be one :abbr:`GL (Gateway Language)` word aligned with each original language word. Of course, this is not possible, because languages work very differently from each other.
Therefore, we expect that you must align words or phrases in the :abbr:`GL (Gateway Language)` with words or phrases in the original language that differ in the number of words, order of words, and parts of speech, as described above. Always, however, you should align the :abbr:`GL (Gateway Language)` words to the original language words whose meaning they express, in whatever combination is necessary to produce the most accurate alignment of the meaning.
After aligning a verse, there may be words in the :abbr:`GL (Gateway Language)` text that are left over and seem to be extra. If those words are truly necessary for the :abbr:`GL (Gateway Language)` text to make sense, then find the original word or words that they help to express and align them there. But if those words do not express a meaning found in the original text, then it may be that those words should be deleted from the :abbr:`GL (Gateway Language)` translation.
Sometimes, in the process of aligning a verse, you will find:
* A original language word that is not represented in the :abbr:`GL (Gateway Language)` translation.
* A mistake in the :abbr:`GL (Gateway Language)` translation.
* Words in the :abbr:`GL (Gateway Language)` translation that do not represent anything in the original text.
* A better or more literal way to express something in the :abbr:`GL (Gateway Language)` translation.
In the above cases, if you are an authorized editor, you will want to edit the :abbr:`GL (Gateway Language)` translation so that it is more accurate to the original.
If you notice places where the :abbr:`ULT (unfoldingWord Literal Text)` is wrong or potentially wrong, create an issue for it at https://git.door43.org/Door43/en_ult/issues and we’ll address it in the next release. In the meantime, align the text as well as possible.
Alignment Philosophy for the UST
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The :abbr:`UST (unfoldingWord Simplified Text)` is intended to be, above all, a clear translation. Therefore, it adds words and phrases to explain the meaning of the original for the reader. These words and phrases should be aligned with the word or words that they are explaining. For example, in Titus 1:1, the phrase, “I am a servant” must be aligned with the single word, *doulos*.
Sometimes, for the sake of clarity, the :abbr:`GL (Gateway Language)` of the :abbr:`UST (unfoldingWord Simplified Text)` will repeat things that are only mentioned once in the original. This often happens with subjects or objects of sentences. For example, in Titus 2:9 the English :abbr:`UST (unfoldingWord Simplified Text)` refers to “their masters” twice, although the original language only has *idiois despotais* once. In these cases, You should align each occurrence of the repeated reference with the same original language words, so that the highlighting will show that each of these represents the meaning conveyed by those same words of the original.
Some of the words and sentences of the :abbr:`UST (unfoldingWord Simplified Text)` do not directly represent the meaning of the original words. This is information that is only implied by the original words, but included in the :abbr:`UST (unfoldingWord Simplified Text)` because it is necessary for understanding the meaning of the original. For example, in Titus 1:1, the sentence, “I, Paul, write this letter to you, Titus” includes information that is not there in the original words, such as the fact that what the reader is about to read is a letter, and that it is written to someone named Titus. This information, however, makes the text more clear and understandable. For the aligning, then, all of this explanation must be aligned with the single word that it is explaining, Paulos.
If you notice places where the :abbr:`UST (unfoldingWord Simplified Text)` is wrong or potentially wrong, create an issue for it at https://git.door43.org/Door43/en_ust/issues and we’ll address it in the next release. In the meantime, align the text as well as possible.

174
docs/gl_checking.rst
View File

@ -1,9 +1,9 @@
:github_url: https://git.door43.org/Door43/en_glm/src/branch/master/docs/gl_checking.rst
:github_url: https://git.door43.org/unfoldingWord/en_glm/src/branch/master/docs/gl_checking.rst
.. _glchecking:
Checking Gateway Language Materials
===================================
Gateway Language Checking
=========================
.. _glchecking-checkingulb:
@ -14,21 +14,23 @@ Checking the ULT
In order to understand this topic, it would be good to read: :ref:`gltranslation-transulb`, :ref:`gltranslation-adaptulb` missing dependencies: ["vol2_steps", "vol2_things_to_check"]
When checking the ULT, remember that the ULT needs to retain the original grammatical forms (as far as possible), the idioms, and the figures of speech of the original so that the OL translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a Gateway Language (GL) translation of the ULT, then the OL translator will never see them and the Notes about them will not make sense. When you are checking the GL translation of the ULT, you must only compare it to the English ULT. Do not refer to any other version of the Bible when checking the ULT. The GL translation of the ULT may not be as smooth and clear as the Gateway Language Bible that you are used to, because it is showing the OL translator the forms of the original biblical languages. Please do not try to make the ULT sound like your favorite translation of the Bible in your language.
When checking the :abbr:`ULT (unfoldingWord Literal Text)`, remember that the :abbr:`ULT (unfoldingWord Literal Text)` needs to retain the original grammatical forms (as far as possible), the idioms, and the figures of speech of the original so that the :abbr:`OL (Other Language)` translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)`, then the :abbr:`OL (Other Language)` translator will never see them and the notes about them will not make sense.
When you are checking the :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)`, you must only compare it to the English :abbr:`ULT (unfoldingWord Literal Text)`. Do not refer to any other version of the Bible when checking the :abbr:`ULT (unfoldingWord Literal Text)`. The :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)` may not be as smooth and clear as the :abbr:`GL (Gateway Language)` Bible that you are used to, because it is showing the :abbr:`OL (Other Language)` translator the forms of the original biblical languages. Please do not try to make the :abbr:`ULT (unfoldingWord Literal Text)` sound like your favorite translation of the Bible in your language.
What Should Be Checked in the ULT?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In addition to the things mentioned in `Types of Things to Check <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md>`_, the ULT needs to be checked in these areas:
In addition to the things mentioned in `Types of Things to Check <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md>`_, the :abbr:`ULT (unfoldingWord Literal Text)` needs to be checked in these areas:
#. **Idioms** - If there is an idiom in the source ULT, then that same idiom should be in the target ULT. If the idiom does not make sense in the target language, make sure that there is a Note that explains its meaning. If there is not a note for it, then write one in the Gateway Language translationNotes that explains its meaning.
#. **Figures of Speech** - If there is a figure of speech in the source ULT, then that same figure of speech should be in the target ULT. If the figure of speech does not make sense in the target language, make sure that there is a Note that explains its meaning. If there is not a note for it, then write one in the Gateway Language translationNotes that explains its meaning.
#. **Grammatical Forms** - Check to see if the grammatical forms, that is, the order of words in the sentence or the way that the words are arranged, is the same in the target Gateway Language ULT as they are in the English source ULT. If the words are arranged differently, ask yourself if they could be arranged the same as the words in the English ULT and still make good sense, or if it is necessary for them to be arranged in a different way in the Gateway Language ULT. If they would still make good sense in a way that an Other Language translator would understand, then put them in the same arrangement as in the English. If they are in a different arrangement because that is what makes sense in the target Gateway Language, then leave them in the different arrangement.
#. **Idioms** - If there is an idiom in the source :abbr:`ULT (unfoldingWord Literal Text)`, then that same idiom should be in the target :abbr:`ULT (unfoldingWord Literal Text)`. If the idiom does not make sense in the target language, make sure that there is a note that explains its meaning. If there is not a note for it, then write one in the :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)` that explains its meaning.
#. **Figures of Speech** - If there is a figure of speech in the source :abbr:`ULT (unfoldingWord Literal Text)`, then that same figure of speech should be in the target :abbr:`ULT (unfoldingWord Literal Text)`. If the figure of speech does not make sense in the target language, make sure that there is a note that explains its meaning. If there is not a note for it, then write one in the :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)` that explains its meaning.
#. **Grammatical Forms** - Check to see if the grammatical forms, that is, the order of words in the sentence or the way that the words are arranged, is the same in the target :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` as they are in the English source :abbr:`ULT (unfoldingWord Literal Text)`. If the words are arranged differently, ask yourself if they could be arranged the same as the words in the English :abbr:`ULT (unfoldingWord Literal Text)` and still make good sense, or if it is necessary for them to be arranged in a different way in the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`. If they would still make good sense in a way that an Other Language translator would understand, then put them in the same arrangement as in the English. If they are in a different arrangement because that is what makes sense in the target :abbr:`GL (Gateway Language)`, then leave them in the different arrangement.
What Should Not Be Checked in the ULT?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is not necessary to check the ULT for naturalness with speakers of the Gateway Language. The ULT will not be natural in some cases, because it is designed to retain the forms of the biblical languages, as far as the Gateway Language allows.
It is not necessary to check the :abbr:`ULT (unfoldingWord Literal Text)` for naturalness with speakers of the :abbr:`GL (Gateway Language)`. The :abbr:`ULT (unfoldingWord Literal Text)` will not be natural in some cases, because it is designed to retain the forms of the biblical languages, as far as the :abbr:`GL (Gateway Language)` allows.
.. seealso:: :ref:`gltranslation-transtn`, :ref:`glchecking-checkingtn`, :ref:`glchecking-checkingudb`
@ -41,27 +43,29 @@ Checking the UST
In order to understand this topic, it would be good to read: :ref:`gltranslation-transudb` missing dependencies: ["vol2_steps", "vol2_things_to_check"]
When checking the UST, remember that the UST does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the UST is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible. When you are checking the GL translation of the UST, you must only compare it to the English UST. Do not refer to any other version of the Bible when checking the UST. The GL translation of the UST may not be as smooth and natural as the Gateway Language Bible that you are used to, because it does not use many of the forms of expression that make a language sound natural. These forms of expression are different for every language. So please do not try to make the UST sound like your favorite translation of the Bible in your language.
When checking the :abbr:`UST (unfoldingWord Simplified Text)`, remember that the :abbr:`UST (unfoldingWord Simplified Text)` does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the :abbr:`UST (unfoldingWord Simplified Text)` is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible.
When you are checking the :abbr:`GL (Gateway Language)` translation of the :abbr:`UST (unfoldingWord Simplified Text)`, you must only compare it to the English :abbr:`UST (unfoldingWord Simplified Text)`. Do not refer to any other version of the Bible when checking the :abbr:`UST (unfoldingWord Simplified Text)`. The :abbr:`GL (Gateway Language)` translation of the :abbr:`UST (unfoldingWord Simplified Text)` may not be as smooth and natural as the :abbr:`GL (Gateway Language)` Bible that you are used to, because it does not use many of the forms of expression that make a language sound natural. These forms of expression are different for every language. So please do not try to make the :abbr:`UST (unfoldingWord Simplified Text)` sound like your favorite translation of the Bible in your language.
What Should Be Checked in the UST?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In addition to the things mentioned in `Types of Things to Check <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md>`_, the UST needs to be checked in these areas. For definitions and examples of these things, see `Translating the UST <https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_udb.md>`_:
In addition to the things mentioned in `Types of Things to Check <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md>`_, the :abbr:`UST (unfoldingWord Simplified Text)` needs to be checked in these areas. For definitions and examples of these things, see `Translating the UST <https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_udb.md>`_:
#. **Sentence length** - If you see any long or complex sentences in the Gateway Language UST, see how you might break them up into shorter sentences.
#. **Passive voice** - If you see this construction in the Gateway Language UST, check to see what it was in the English source UST and change it so that it is active.
#. **Abstract Nouns** - If you see one of these in the Gateway Language UST, check to see what it was in the English source UST and change it back to an action or description word.
#. **Events out of order** - Make sure that the events in the Gateway UST are in the order that they occurred. Also make sure that the logical flow of arguments, such as occur in many of the New Testament letters, is in a natural order that makes sense in the GL.
#. **Figures of speech and idioms** - Make sure that the GL UST does not contain any figures of speech or idioms. Instead, it should use only plain, clear language.
#. **Sentence length** - If you see any long or complex sentences in the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)`, see how you might break them up into shorter sentences.
#. **Passive voice** - If you see this construction in the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)`, check to see what it was in the English source :abbr:`UST (unfoldingWord Simplified Text)` and change it so that it is active.
#. **Abstract Nouns** - If you see one of these in the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)`, check to see what it was in the English source :abbr:`UST (unfoldingWord Simplified Text)` and change it back to an action or description word.
#. **Events out of order** - Make sure that the events in the Gateway :abbr:`UST (unfoldingWord Simplified Text)` are in the order that they occurred. Also make sure that the logical flow of arguments, such as occur in many of the New Testament letters, is in a natural order that makes sense in the :abbr:`GL (Gateway Language)`.
#. **Figures of speech and idioms** - Make sure that the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)` does not contain any figures of speech or idioms. Instead, it should use only plain, clear language.
If you see any of these forms in the English UST, email <help@door43.org> to let them know of the error.
If you see any of these forms in the English :abbr:`UST (unfoldingWord Simplified Text)`, email <help@door43.org> to let them know of the error.
It is also useful to check the UST for clarity with speakers of the Gateway Language, but do not confuse clarity with naturalness (see below). You can read a passage from the UST to a speaker of the Gateway Language, and ask if the meaning is clear. If they say, "Yes," that is enough. If they also say, "But I would say it differently," that is fine. We expect that they would say it differently. But the UST needs to say it in a plain way. As long as the meaning of the GL UST is clear, it is a successful translation.
It is also useful to check the :abbr:`UST (unfoldingWord Simplified Text)` for clarity with speakers of the :abbr:`GL (Gateway Language)`, but do not confuse clarity with naturalness (see below). You can read a passage from the :abbr:`UST (unfoldingWord Simplified Text)` to a speaker of the :abbr:`GL (Gateway Language)`, and ask if the meaning is clear. If they say, "Yes," that is enough. If they also say, "But I would say it differently," that is fine. We expect that they would say it differently. But the :abbr:`UST (unfoldingWord Simplified Text)` needs to say it in a plain way. As long as the meaning of the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)` is clear, it is a successful translation.
What Should Not Be Checked in the UST?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is not necessary to check the UST for naturalness with speakers of the Gateway Language. The UST will very often not be completely natural, because it avoids some forms that languages naturally use, such as idioms and figures of speech. The UST avoids these because they are specific to individual languages, and do not translate well from one language to another.
It is not necessary to check the :abbr:`UST (unfoldingWord Simplified Text)` for naturalness with speakers of the :abbr:`GL (Gateway Language)`. The :abbr:`UST (unfoldingWord Simplified Text)` will very often not be completely natural, because it avoids some forms that languages naturally use, such as idioms and figures of speech. The :abbr:`UST (unfoldingWord Simplified Text)` avoids these because they are specific to individual languages, and do not translate well from one language to another.
.. seealso:: :ref:`gltranslation-transtn`, :ref:`glchecking-checkingtn`
@ -69,26 +73,26 @@ It is not necessary to check the UST for naturalness with speakers of the Gatewa
Checking translationNotes
-------------------------
.. note:: This module answers the question, "What are the guidelines for checking translationNotes?"
In order to understand this topic, it would be good to read: :ref:`gltranslation-transtn` missing dependencies: ["vol2_steps", "vol2_things_to_check"]
When checking translationNotes, remember that tN are very closely tied to the text of the ULT. The purpose of tN is to explain any phrases or sentences in the ULT that are hard to understand or hard to translate.
When checking :abbr:`tN (translationNotes)`, remember that :abbr:`tN (translationNotes)` are very closely tied to the text of the :abbr:`ULT (unfoldingWord Literal Text)`. The purpose of :abbr:`tN (translationNotes)` is to explain any phrases or sentences in the :abbr:`ULT (unfoldingWord Literal Text)` that are hard to understand or hard to translate.
What Should Be Checked?
^^^^^^^^^^^^^^^^^^^^^^^
In addition to the things mentioned in `Types of Things to Check <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md>`_, tN need to be checked in these areas.
In addition to the things mentioned in `Types of Things to Check <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_things_to_check.md>`_, :abbr:`tN (translationNotes)` need to be checked in these areas.
#. Although the GL tN are a translation of the English tN it is important that the phrase in each Note that reproduces the phrase from the ULT is exactly the same as it is in the GL ULT. So you must check the meaning of the Note in the English tN and make sure that the GL tN has the same meaning. Then you must also check the wording of the phrase that comes from the GL ULT and make sure that the words are exactly the same.
#. In the same way, make sure that any quotations of the UST have the exact wording of the GL UST.
#. Check that the GL tN makes sense with the GL ULT. It is possible that the GL translator made a good translation of the English tN but when the Note is read with the new GL ULT, it might not explain the GL ULT in the right way, or it might not make sense with the GL ULT. In that case, you will need to discuss the problem with the translator. Then you will need to decide how to change the Note so that it explains the GL ULT in a way that will be helpful to the OL translator.
#. Check that all references to the UST make sense with the GL UST.
#. If the GL translator has decided that a Note does not apply to the GL ULT and has deleted the note from the GL tN, check to make sure that the Note was not needed.
#. If the GL translator has written a new Note, check to make sure that it was needed, and that it makes sense with the GL ULT.
#. Although the :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)` are a translation of the English :abbr:`tN (translationNotes)` it is important that the phrase in each note that reproduces the phrase from the :abbr:`ULT (unfoldingWord Literal Text)` is exactly the same as it is in the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`. So you must check the meaning of the note in the English :abbr:`tN (translationNotes)` and make sure that the :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)` has the same meaning. Then you must also check the wording of the phrase that comes from the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` and make sure that the words are exactly the same.
#. In the same way, make sure that any quotations of the :abbr:`UST (unfoldingWord Simplified Text)` have the exact wording of the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)`.
#. Check that the :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)` makes sense with the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`. It is possible that the :abbr:`GL (Gateway Language)` translator made a good translation of the English :abbr:`tN (translationNotes)` but when the note is read with the new :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`, it might not explain the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` in the right way, or it might not make sense with the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`. In that case, you will need to discuss the problem with the translator. Then you will need to decide how to change the note so that it explains the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` in a way that will be helpful to the :abbr:`OL (Other Language)` translator.
#. Check that all references to the :abbr:`UST (unfoldingWord Simplified Text)` make sense with the :abbr:`GL (Gateway Language)` :abbr:`UST (unfoldingWord Simplified Text)`.
#. If the :abbr:`GL (Gateway Language)` translator has decided that a note does not apply to the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` and has deleted the note from the :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)`, check to make sure that the note was not needed.
#. If the :abbr:`GL (Gateway Language)` translator has written a new note, check to make sure that it was needed, and that it makes sense with the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`.
In order to check the tN for naturalness and clarity, you will need to have people read them together with the GL ULT and UST. Then ask them to mark anything that is not clear to them, or that they would say in a different way. Then give this feedback to the translator so that he can make those places clearer and more natural.
In order to check the :abbr:`tN (translationNotes)` for naturalness and clarity, you will need to have people read them together with the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` and :abbr:`UST (unfoldingWord Simplified Text)`. Then ask them to mark anything that is not clear to them, or that they would say in a different way. Then give this feedback to the translator so that he can make those places clearer and more natural.
.. seealso:: :ref:`gltranslation-transtn`, :ref:`glchecking-checkingulb`, :ref:`glchecking-checkingudb`
@ -96,7 +100,7 @@ In order to check the tN for naturalness and clarity, you will need to have peop
Finishing Checking
------------------
.. note:: This module answers the question, "How do I know when I have finished the checking for each level?"
In order to understand this topic, it would be good to read: :ref:`gltranslation-whatneedstrans` missing dependencies: ["vol2_steps", "vol2_things_to_check"]
@ -106,24 +110,24 @@ It can be difficult to know when you have sufficiently checked a text for errors
Checking Evaluation Lists
^^^^^^^^^^^^^^^^^^^^^^^^^
The following lists can help you to consider whether or not you have checked a GL resource sufficiently.
The following lists can help you to consider whether or not you have checked a :abbr:`GL (Gateway Language)` resource sufficiently.
Level One
"""""""""
Level one checking includes:
* Initial study of the related materials, including:
* The guidelines for translation of the specific materials in the Gateway Languages Manual
* The translationNotes
* The definitions of translationWords
* Reading each chapter connected to the translated materials in both ULT and UST
* Initial study of the related materials, including:
* The guidelines for translation of the specific materials in the Gateway Language Manual
* The :abbr:`tN (translationNotes)`
* The definitions of :abbr:`tW (translationWords)`
* Reading each chapter connected to the translated materials in both :abbr:`ULT (unfoldingWord Literal Text)` and :abbr:`UST (unfoldingWord Simplified Text)`
* Careful comparison with the source text, including:
* Individual self edit
* Peer edit
* Key word check as a team
* Accuracy check as a team
* Final editing, including everything learned from the earlier editing sessions, the translationNotes, and the definitions of translationWords
* Final editing, including everything learned from the earlier editing sessions, the :abbr:`tN (translationNotes)`, and the definitions of :abbr:`tW (translationWords)`.
Level Two
"""""""""
@ -132,104 +136,14 @@ In addition to the steps listed above for level one, all parts of the resource h
* The Translation conforms to the Statement of Faith (see http://ufw.io/faith/) and Translation Guidelines (see http://ufw.io/guidelines/).
* The Translation accurately communicates the content of the source document in the target language.
* The style of the Translation conforms to the guidelines set forth for translation of this resource in the Gateway Languages Manual.
* The style of the Translation conforms to the guidelines set forth for translation of this resource in the Gateway Language Manual.
* The translation team has edited the Translation to their satisfaction.
Level Three
"""""""""""
For level three, at least 2 more people need to have checked every part of the resource. These people must meet the following criteria: people who were not involved in the translation, were not part of the checking process of level two for that resource, and are bilingual in English. In addition, these people are leaders of different church networks or denominations who are either Bible scholars themselves or who can delegate the level 3 checking to trusted associates who are Bible scholars, able to compare the GL translations with the original biblical languages. They also need to affirm the same statements as in level two.
For level three, at least 2 more people need to have checked every part of the resource. These people must meet the following criteria: people who were not involved in the translation, were not part of the checking process of level two for that resource, and are bilingual in English. In addition, these people are leaders of different church networks or denominations who are either Bible scholars themselves or who can delegate the level 3 checking to trusted associates who are Bible scholars, able to compare the :abbr:`GL (Gateway Language)` translations with the original biblical languages. They also need to affirm the same statements as in level two.
Additional questions that can help you to evaluate if the translation has been sufficiently checked are in `Self-Assessment Rubric <https://git.door43.org/Door43/en-ta-checking-vol1/src/master/content/self_assessment.md>`_. Just be aware that the ULT and the UST are not intended to be completely natural in the Gateway Language.
Additional questions that can help you to evaluate if the translation has been sufficiently checked are in `Self-Assessment Rubric <https://git.door43.org/Door43/en-ta-checking-vol1/src/master/content/self_assessment.md>`_. Just be aware that the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)` are not intended to be completely natural in the :abbr:`GL (Gateway Language)`.
.. seealso:: missing: ["self_assessment", "intro_publishing", "source_text_process"]
Aligning Gateway Language Translations
======================================
The purpose of the aligning tool in translationCore (tC) is to create highlighting that will appear for the OL translator who will use the GL text as a source text for an OL translation. This highlighting will show the user of the GL text how that GL text represents the meaning of the original biblical language text. When the OL translator uses the translationWords or translationNotes tools in tC, the aligned GL text will allow tC to highlight the word or phrase that the tC check is talking about in both the original biblical language and the GL. This will help the OL translator to see how the biblical language expressed that meaning, how the GL expressed that meaning, and how he might express that same meaning in the target language.
So as you align the GL text with the original language text, your job is to match as accurately as possible the words of the GL text to the words of the original text that express the same meaning.
The functionality of tC will increase over time, so some of these comments will need to be updated as tC changes.
• In tC 0.9.x, Only the translationWords and the Alignment tools are available.
• No alignment data is currently exported in the Export to CSV function.
To Begin:
---------
• On the project list screen, if the Select button is disabled for the desired project, click the Home icon or the Go to Tools button to launch the project.
• Only the English ULT and the Greek BHP are opened by default in the scripture panel. Click on the + sign in the rightmost section of the scripture panel to add another language. Use the X and + controls in the scripture to close and open the sections to move the languages to different sections.
General aligning instructions:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
• The GL chapters and verses are listed down the left side. When you click on a verse to open it, the words of that verse appear in a vertical list, ordered from top to bottom, just to the right of the list of chapters and verses. Each word is in a separate box.
• The words of the original language text (Greek) for that verse are also in separate boxes in a field to the right of the GL word list. There is a space under each of the source word boxes outlined with a dotted line. Click and drag each word box of the GL text into the space under the word box of the source text that the GL word corresponds to. Drop it there. When the GL word is over a word box of the original, the dotted outline will turn blue to let you know that the word will drop there. If you make a mistake or decide that the GL word belongs somewhere else, simply drag it again to where it belongs. GL words can also be dragged back to the list.
• When the same GL word occurs more than once in a verse, each instance of the word will have a small superscript number after it. This number will help you to align each repeated GL word to the correct original word in the correct order.
Merge and un-merge instructions/constraints:
""""""""""""""""""""""""""""""""""""""""""""
• tC supports one-to-one, one-to-many, many-to-one, and many-to-many alignments. That means that one or more GL words can be aligned to one or more Greek words, as necessary to get the most accurate alignment of the meaning conveyed by the two languages.
• To align multiple GL words to a single Greek word, simple drag and drop the GL words onto the box below the desired Greek word.
• When it is desired to align GL word(s) to a combination of Greek words, first drag one of the combination Greek words into the same box as the other Greek word. Multiple Greek words can be merged together in this fashion.
• To un-merge previously merged Greek words, drag the rightmost Greek word slightly to the right. A small new alignment box will appear, and the un-merged word can be dropped into that box.
• The leftmost Greek word can also be un-merged by dragging and dropping it into the Greek word box immediately to its left.
Expected behavior when un-merging Greek words:
""""""""""""""""""""""""""""""""""""""""""""""
• Any GL words that were aligned with that Greek word return to the word list.
• The Greek words should remain in the proper order. If the merge contains 3 or more Greek words, un-merge the rightmost Greek word first. Un-merging the center word(s) first may result in the Greek words becoming out of order. When that happens, un-merge the remaining words in that box to properly return the Greek words to their original order.
Drag and drop alignment instructions/constraints (from and to the word list):
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
• Many languages use indefinite and definite articles differently than does Greek. For English, we must do the following:
• Align indefinite articles to their “head word.” For example, both “a” and “servant” should align to *doulos* in Titus 1:1.
• Definite articles that English supplies should also be aligned to their “head word.” For example, both “the” and “faith” should align to *pistin* in Titus 1:1.
• Greek definite articles that English does not use need to be combined with their Greek head word. For example, *ton* and *logon* need to be combined, then “word” aligned with that combination in Titus 1:3.
• Implicit verbs in Greek/Hebrew that are translated explicitly in the target language should be aligned with the predicate. For example, “he should be” that is supplied in English should be aligned to *philoxenon* along with “hospitable” in Titus 1:8.
• Words with apostrophes will be split and show up as 2 words in the word panel. This allows for proper alignment of the two parts of meaning. In most cases in English these are used to represent possession and will be aligned to a single Greek word in the genitive case. For example, both “God” and “s” will align to *theou* in Titus 1:1.
• Often the Greek and GL part of speech won’t match. That is inevitable. Often a Greek word will be translated as a GL phrase. For example, the three words “does not lie” in English all align with the single word *apseudes* in Titus 1:2.
Alignment instructions for the ULT
----------------------------------
• The ULT is intended to be a fairly literal translation of the original, so that it reproduces the structure of the original language when that is also understandable in the GL. Ideally, then, there would be one GL word aligned with each Greek or Hebrew word. Of course, this is not possible, because languages work very differently from each other. Therefore, we expect that you must align words or phrases in the GL with words or phrases in the Greek or Hebrew that differ in the number of words, order of words, and parts of speech, as described above. Always, however, you should align the GL words to the Greek or Hebrew words whose meaning they express, in whatever combination is necessary to produce the most accurate alignment of the meaning.
• After aligning a verse, there may be words in the GL text that are left over and seem to be extra. If those words are truly necessary for the GL text to make sense, then find the original word or words that they help to express and align them there. But if those words do not express a meaning found in the original text, then it may be that those words should be deleted from the GL text.
• Sometimes, in the process of aligning a verse, you will find:
• A Greek or Hebrew word that is not represented in the GL translation.
• A mistake in the GL translation.
• Words in the GL translation that do not represent anything in the original text.
• A better or more literal way to express something in the GL translation.
• In those cases, if you are an authorized editor using tC version 0.9.1 or above, you will want to edit the GL translation so that it is more accurate to the original.
• If you notice places where the ULT is wrong or potentially wrong, create an issue for it at https://git.door43.org/Door43/en_ult/issues and we’ll address it in the next release. In the meantime, align the text as well as possible.
Alignment instructions for the UST
----------------------------------
• The UST is intended to be, above all, a clear translation. Therefore, it adds words and phrases to explain the meaning of the original for the reader. These words and phrases should be aligned with the word or words that they are explaining. For example, in Titus 1:1, the sentence, “I am a servant” must be aligned with the single word, *doulos*.
• Be sure that the dotted outline of the word box where you want to drop the GL word turns blue before you drop it. That is the indication that tC gives you of where the word will drop. If you pay attention to this, you will avoid having the GL word drop in the wrong place.
• Sometimes, for the sake of clarity, the GL of the UST will repeat things that are only mentioned once in the original. This often happens with subjects or objects of sentences. For example, in Titus 2:9 the English UST refers to “their masters” twice, although the Greek only has *idiois despotais* once. In these cases, You should align each occurrence of the repeated reference with the same Greek words, so that the highlighting will show that each of these represents the meaning conveyed by those same words of the original.
• Some of the words and sentences of the UST do not directly represent the meaning of the original words. This is information that is only implied by the original words, but included in the UST because it is necessary for understanding the meaning of the original. For example, in Titus 1:1, the sentence, “I, Paul, write this letter to you, Titus” includes information that is not there in the original words, such as the fact that what the reader is about to read is a letter, and that it is written to someone named Titus. This information, however, makes the text more clear and understandable. For the aligning, then, all of this explanation must be aligned with the single word that it is explaining, Paulos.
• If you notice places where the UST is wrong or potentially wrong, create an issue for it at https://git.door43.org/Door43/en_ust/issues and we’ll address it in the next release. In the meantime, align the text as well as possible.
Alignment Anomalies
^^^^^^^^^^^^^^^^^^^
In tC 0.9.0:
""""""""""""
• Under certain circumstances both the GL and Greek words can get merged in the wrong order. Un-merge all of those words and re-merge them to correct the problem.
• We are unsure about the accuracy of the tokenization of the Hindi ULT
• If a GL word is accidentally dropped while it is still in the word list frame, both it and the word list get hidden. Click in the word list area to make them visible again.
• When moving from verse to verse, the target area is not automatically scrolled to the top. There may be Greek words hidden behind the scripture pane. Manually scroll to the top when that situation occurs.
• In some cases when attempting to merge Greek words, the potential target gets highlighted in blue even though the Greek word cannot be dropped there.
• The “verse complete” green checkmark will appear when all of the words from the word list have been aligned, even if all of the Greek words do not have corresponding GL words.
• Alignment data is NOT exported as part of either the USFM export or CSV export. Alignment projects can be shared only by uploading first to Door43 and then importing from there to a different machine.

307
docs/gl_translation.rst
View File

@ -1,4 +1,4 @@
:github_url: https://git.door43.org/Door43/en_glm/src/branch/master/docs/gl_translation.rst
:github_url: https://git.door43.org/unfoldingWord/en_glm/src/branch/master/docs/gl_translation.rst
.. _gltranslation:
@ -6,11 +6,15 @@ Gateway Language Translation
============================
Introduction
---------------------------
------------
.. note:: This module answers the question, "What is the Gateway Language Manual?"
The Gateway Language Manual is for the use of translators and checkers of the Gateway Language resources. It presents the guidelines for translating and checking all of the Gateway Language resources. Before translating or checking any of these resources, please read it carefully. It presents the unique properties of each of the resources, the purpose of each one, and how each one functions as part of a complete translation package for the use of Other Language (OL) translators. If you fail to understand the properties and purpose of the resource that you are translating or checking, it will not be able to fulfil its purpose and the translation package that you produce will be defective. But if you follow these guidelines and understand well how each resource functions, you will produce a set of translation resources that will allow the OL translators to create accurate, natural, and clear translations of the Bible in their own languages.
The Gateway Language Manual is for the use of translators and checkers of the Gateway Language (GL) resources. It presents the guidelines for translating and checking all of the :abbr:`GL (Gateway Language)` resources.
Before translating or checking any of these resources, please read the manual carefully. It presents the unique properties of each of the resources, the purpose of each one, and how each one functions as part of a complete translation package for the use of Other Language (OL) translators.
If you fail to understand the properties and purpose of the resource that you are translating or checking, it will not be able to fulfil its purpose and the translation package that you produce will be defective. But if you follow these guidelines and understand well how each resource functions, you will produce a set of translation resources that will allow the :abbr:`OL (Other Language)` translators to create accurate, natural, and clear translations of the Bible in their own languages.
.. _gltranslation-whatneedstrans:
@ -21,26 +25,26 @@ What Needs To Be Translated
The following materials must be translated into the gateway languages and checked to the levels stated.
* translationAcademy (tA)- Level 2
* Open Bible Stories (OBS) text - Level 3
* Open Bible Stories translationNotes (OBS-tN) - Level 3
* Open Bible Stories translationQuestions (OBS-tQ) - Level 2
* unfoldingWord Literal Text (ULT) Text - Level 3
* unfoldingWord Simplified Text (UST) Text - Level 3
* translationNotes (tN)- Level 3
* translationWords (tW)- Level 2
* translationQuestions (tQ) - Level 2
* `translationAcademy <https://unfoldingword.org/academy/>`_ (tA)- Level 2
* `Open Bible Stories <https://openbiblestories.com>`_ (OBS) text - Level 3
* `Open Bible Stories translationNotes <https://git.door43.org/unfoldingWord/en_obs-tn>`_ (OBS-tN) - Level 3
* `Open Bible Stories translationQuestions <https://git.door43.org/unfoldingWord/en_obs-tq>`_ (OBS-tQ) - Level 2
* `unfoldingWord Literal Text <https://unfoldingword.org/ult/>`_ (ULT) Text - Level 3
* `unfoldingWord Simplified Text <https://unfoldingword.org/ust/>`_ (UST) Text - Level 3
* `translationNotes <https://unfoldingword.org/tn/>`_ (tN)- Level 3
* `translationWords <https://unfoldingword.org/tw/>`_ (tW)- Level 2
* `translationQuestions <https://unfoldingword.org/tq/>`_ (tQ) - Level 2
We recommend that you translate the resources in the order as given in the list above. By translating translationAcademy first, the translators will gain knowledge of how to translate well, and also make that knowledge available in the Gateway Language for the rest of the translation team. Translating the OBS resources next will give the translation team valuable experience in translating as they work through a simplified presentation of biblical content. Then the translation team will be ready to start translating the two Bible texts and the related helps for those: tN, tQ, and tW.
We recommend that you translate the resources in the order given in the list above. By translating :abbr:`tA (translationAcademy)` first, the translators will gain knowledge of how to translate well, and also make that knowledge available in the :abbr:`GL (Gateway Language)` for the rest of the translation team. Translating the :abbr:`OBS (Open Bible Stories)` resources next will give the translation team valuable experience in translating as they work through a simplified presentation of biblical content. Then the translation team will be ready to start translating the two Bible texts and the related helps for those: :abbr:`tN (translationNotes)`, :abbr:`tQ (translationQuestions)`, and :abbr:`tW (translationWords)`.
It is important that you translate the text of the ULT and the UST before you translate tN and tQ. However, This could be done book-by-book or chapter-by-chapter. For example, you could translate all of the translation resources for each chapter of a Bible book together. In this case, for each chapter of text, you would translate the ULT and the UST of those verses, then tN, tW, and tQ for those same verses. Then you would move to the next chapter and translate each of the resources for that chapter, as well, in that order. (For information about which books of the Bible to translate first, see `Choosing What to Translate <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/translation_difficulty.md>`_.)
It is important that you translate the text of the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)` before you translate :abbr:`tN (translationNotes)` and :abbr:`tQ (translationQuestions)`. However, This could be done book-by-book or chapter-by-chapter. For example, you could translate all of the translation resources for each chapter of a Bible book together. In this case, for each chapter of text, you would translate the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)` of those verses, then :abbr:`tN (translationNotes)`, :abbr:`tW (translationWords)`, and :abbr:`tQ (translationQuestions)` for those same verses. Then you would move to the next chapter and translate each of the resources for that chapter. (For information about which books of the Bible to translate first, see `Choosing What to Translate <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/translation_difficulty.md>`_.)
Why Translate Two Bibles into the Gateway Languages?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Some people might ask this question, because adequate Bibles already exist in most of the Gateway languages. However, these are end-user Bibles, designed to be read and studied by people who speak those languages in their homes and churches. The Bibles that we are translating are not end-user Bibles. They are Bibles designed to be used in conjunction with each other and with the other translation helps as a set of tools that will allow speakers of other languages to use them to translate a Bible into their own languages. What they produce from these tools will be an end-user Bible.
Some people might ask this question, because adequate Bibles already exist in most of the Gateway languages. However, the existing translations are end-user Bibles, designed to be read and studied by people who speak those languages in their homes and churches. The Bibles that we are translating are not end-user Bibles. They are Bibles designed to be used in conjunction with each other and with the other translation helps as a set of tools that will allow speakers of other languages to use them to translate a Bible into their own languages. What they produce from these tools will be an end-user Bible.
To make an end-user Bible, it is always best to translate from more than one version, so that the translator does not fall into the habit of following the form of any one version too closely. Also, it is always possible to translate something in more than one way in a target language, and often the biblical language has more than one possible meaning. Looking at multiple versions that between them reveal these differences gives the translator a window into those things that a single version would not give. This benefit is maximized when the two (or more) source Bibles use very different styles, such as literal and dynamic. Having a literal version and a dynamic version side by side give the translator a "three-dimensional" view into the original text, allowing him to see both the form and the meaning at the same time. It is for this purpose that we are providing the ULT and the UST.
To make an end-user Bible, it is always best to translate from more than one version, so that the translator does not fall into the habit of following the form of any one version too closely. Also, it is always possible to translate something in more than one way in a target language, and often the biblical language has more than one possible meaning. Looking at multiple versions that between them reveal these differences gives the translator a window into those things that a single version would not give. This benefit is maximized when the two (or more) source Bibles use very different styles, such as literal and dynamic. Having a literal version and a dynamic version side by side give the translator a "three-dimensional" view into the original text, allowing him to see both the form and the meaning at the same time. It is for this purpose that we are providing the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)`.
.. seealso:: :ref:`gltranslation-transulb`, :ref:`gltranslation-transudb`
@ -56,22 +60,30 @@ Translating the ULT
Translation Theory for Translating the ULT
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The *unfoldingWord Literal Text* (ULT) is designed to be used in conjunction with the translationNotes and the *unfoldingWord Simplified Text* (UST) as a tool for Bible translation. Unlike the UST and unlike an end-user Bible, the ULT is designed to reflect the forms of the source languages, so that the Other Language (OL) translator can see what they are. By using the ULT, the OL translator can "look through" it to see how the original Bible expressed the biblical ideas. As you translate the ULT, therefore, you must try to retain the grammatical and syntactic structures of the original as far as the target language (Gateway Language) will allow. If the original structure does not make sense in the target language, then you will need to change it into a structure that does make sense. It does no good to make a translation that the OL translator using this tool will not be able to understand. But as far as the target language will allow, retain the structures of the original in your translation of the ULT.
The :abbr:`ULT (unfoldingWord Literal Text)` is designed to be used in conjunction with the :abbr:`tN (translationNotes)` and the :abbr:`UST (unfoldingWord Simplified Text)` as a tool for Bible translation. Unlike the :abbr:`UST (unfoldingWord Simplified Text)` and unlike an end-user Bible, the :abbr:`ULT (unfoldingWord Literal Text)` is designed to reflect the forms of the source languages, so that the :abbr:`OL (Other Language)` translator can see what they are. By using the :abbr:`ULT (unfoldingWord Literal Text)`, the :abbr:`OL (Other Language)` translator can "look through" it to see how the original Bible expressed the biblical ideas.
As you translate the :abbr:`ULT (unfoldingWord Literal Text)` you must try to retain the grammatical and syntactic structures of the original as far as the target language (:abbr:`GL (Gateway Language)`) will allow. If the original structure does not make sense in the target language, then you will need to change it into a structure that does make sense. It is not useful to make a translation that the :abbr:`OL (Other Language)` translator will not be able to understand. But as far as the target language will allow, retain the structures of the original in your translation of the :abbr:`ULT (unfoldingWord Literal Text)`.
What method should be used to translate the ULT?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
When translating the ULT, keep the English source open in front of you. This means that you should not use any methodology that includes a step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the ULT is a tool that must retain the original, biblical language structures in order to be useful to the translator. The best way to guard these structures is to translate with the English source ULT open in front of you so that you can be sure to keep these structures as they are in the English ULT, as far as the target language will allow.
When translating the :abbr:`ULT (unfoldingWord Literal Text)`, keep the English source open in front of you. This means that you should not use any methodology that includes a step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the :abbr:`ULT (unfoldingWord Literal Text)` is a tool that must retain the original, biblical language structures in order to be useful to the translator. The best way to guard these structures is to translate with the English source :abbr:`ULT (unfoldingWord Literal Text)` open in front of you so that you can be sure to keep these structures as they are in the English :abbr:`ULT (unfoldingWord Literal Text)`, as far as the target language will allow.
Does Translation of the ULT Require a Back Translation?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We expect that the people translating the ULT into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the ULT will usually not be necessary. The exception to this will be if the translation of the ULT is done by a secular translation company. In this case, a back translation into English may be necessary, done according to the guidelines set forth in `Back Translation <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md>`_ and following modules.
.. include:: /includes/glchurchcapacity.txt
.. include:: /includes/backtranslation.txt
What are the structures of the ULT that should be retained?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The translation of the ULT needs to retain the original grammatical forms (as far as is possible), the idioms, and the figures of speech of the original so that the OL translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a Gateway Language (GL) translation of the ULT, then the OL translator will never see them and the translationNotes about them will not make sense. Keep in mind that the ULT and the UST are only going to be translated into the GLs, because they are translation tools for the use of the OL translator. We want these tools to be as useful as possible. For the ULT, this means that it should retain structures that we would not always retain in an end-user Bible. The GL translator must understand that this translation will lack naturalness and sometimes also lack clarity because it is aiming at reproducing these original language structures and figures of speech that may not translate well into the GL. Wherever the ULT translation lacks clarity, however, there should also be a translationNote to explain the meaning of the structure for the OL translator. The translationNotes and the UST will provide the meaning wherever that meaning is in doubt in the ULT. In this way, the tools will work together to provide the OL translator with a full set of information about both the form and the meaning of the original Bible.
The translation of the :abbr:`ULT (unfoldingWord Literal Text)` needs to retain the original grammatical forms (as far as is possible), the idioms, and the figures of speech of the original so that the :abbr:`OL (Other Language)` translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)`, then the :abbr:`OL (Other Language)` translator will never see them and the :abbr:`tN (translationNotes)` about them will not make sense.
Keep in mind that the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)` are only going to be translated into the :abbr:`GLs (Gateway Languages)`, because they are translation tools for the use of the :abbr:`OL (Other Language)` translator. We want these tools to be as useful as possible.
For the :abbr:`ULT (unfoldingWord Literal Text)`, this means that it should retain structures that we would not always retain in an end-user Bible. The :abbr:`GL (Gateway Language)` translator must understand that this translation will lack naturalness and sometimes also lack clarity because it is aiming at reproducing these original language structures and figures of speech that may not translate well into the :abbr:`GL (Gateway Language)`. Wherever the :abbr:`ULT (unfoldingWord Literal Text)` translation lacks clarity, however, there should also be a note to explain the meaning of the structure for the :abbr:`OL (Other Language)` translator. The :abbr:`tN (translationNotes)` and the :abbr:`UST (unfoldingWord Simplified Text)` will provide the meaning wherever that meaning is in doubt in the :abbr:`ULT (unfoldingWord Literal Text)`. In this way, the tools will work together to provide the :abbr:`OL (Other Language)` translator with a full set of information about both the form and the meaning of the original Bible.
Examples
^^^^^^^^
@ -79,29 +91,29 @@ Examples
Grammatical Forms
"""""""""""""""""
The ULT of Luke 2:47 reproduces a grammatical form from the Greek source language that is also natural in English, but that might not be natural in other languages. When talking about the boy Jesus at the temple, it says, "All who heard him were amazed at his understanding and his answers." The nouns "understanding" and "answers" refer to events, not things, and so must be translated as verbs in many languages.
The :abbr:`ULT (unfoldingWord Literal Text)` of Luke 2:47 reproduces a grammatical form from the Greek source language that is also natural in English, but that might not be natural in other languages. When talking about the boy Jesus at the temple, it says, "All who heard him were amazed at his understanding and his answers." The nouns "understanding" and "answers" refer to events, not things, and so must be translated as verbs in many languages.
The UST of the same verse gives an example of how these nouns can be translated as verbs. It says, "All the people who heard what he said were amazed at how much he *understood* and how well he *answered* the questions that the teachers asked."
The :abbr:`UST (unfoldingWord Simplified Text)` of the same verse gives an example of how these nouns can be translated as verbs. It says, "All the people who heard what he said were amazed at how much he *understood* and how well he *answered* the questions that the teachers asked."
When translating the ULT, however, these nouns should be translated as nouns if that will make sense in the target language.
When translating the :abbr:`ULT (unfoldingWord Literal Text)`, however, these nouns should be translated as nouns if that will make sense in the target language.
Idioms
""""""
The ULT of Matthew 2:20 reproduces an idiom from the Greek source language. It refers to Herod and his soldiers who were trying to kill the child Jesus as, "those who sought the child's life." In some languages this is clear, and in others it is not.
The :abbr:`ULT (unfoldingWord Literal Text)` of Matthew 2:20 reproduces an idiom from the Greek source language. It refers to Herod and his soldiers who were trying to kill the child Jesus as, "those who sought the child's life." In some languages this is clear, and in others it is not.
The UST of the same verse tries to make the meaning clear by translating this idiom as, "the people who were trying to kill the child." Many GL Bibles do the same thing.
The :abbr:`UST (unfoldingWord Simplified Text)` of the same verse tries to make the meaning clear by translating this idiom as, "the people who were trying to kill the child." Many :abbr:`GL (Gateway Language)` Bibles do the same thing.
When translating the ULT, however, this idiom should be translated as it is, so that the Other Language translator can consider it and use it if it makes sense. The UST and the translationNotes will provide the meaning.
When translating the :abbr:`ULT (unfoldingWord Literal Text)`, however, this idiom should be translated as it is, so that the :abbr:`OL (Other Language)` translator can consider it and use it if it makes sense. The :abbr:`UST (unfoldingWord Simplified Text)` and the :abbr:`tN (translationNotes)` will provide the meaning.
Figures of Speech
"""""""""""""""""
The ULT of John 1:17 reproduces a figure of speech from the Greek source language. It says, "grace and truth came through Jesus Christ." (This figure of speech is called "personification;" see `Personification <https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_personification.md>`_.) This figure of speech talks as if grace and truth were like people who can come and go, and it talks as if Jesus Christ were like a doorway that they can come through. In some languages this makes sense, but in other languages it does not. The plain meaning is that Jesus Christ acted toward us with grace and taught us true things about God.
The :abbr:`ULT (unfoldingWord Literal Text)` of John 1:17 reproduces a figure of speech from the Greek source language. It says, "grace and truth came through Jesus Christ." (This figure of speech is called "personification;" see `Personification <https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_personification.md>`_.) This figure of speech talks as if grace and truth were like people who can come and go, and it talks as if Jesus Christ were like a doorway that they can come through. In some languages this makes sense, but in other languages it does not. The plain meaning is that Jesus Christ acted toward us with grace and taught us true things about God.
The UST of the same verse tries to make this plain meaning clear by translating it as, "Jesus Christ was kind to us far beyond what we deserved and taught us true things about God."
The :abbr:`UST (unfoldingWord Simplified Text)` of the same verse tries to make this plain meaning clear by translating it as, "Jesus Christ was kind to us far beyond what we deserved and taught us true things about God."
When translating the ULT, however, this figure of speech should be translated as it is, so that the Other Language translator can consider it and use it if it makes sense. If it does not, the UST provides an alternative way to translate it.
When translating the :abbr:`ULT (unfoldingWord Literal Text)`, however, this figure of speech should be translated as it is, so that the :abbr:`OL (Other Language)` translator can consider it and use it if it makes sense. If it does not, the :abbr:`UST (unfoldingWord Simplified Text)` provides an alternative way to translate it.
.. seealso:: :ref:`gltranslation-adaptulb`, :ref:`glchecking-checkingulb`, :ref:`gltranslation-transudb`
@ -120,147 +132,163 @@ Translating the UST
Translation Theory for Translating the UST
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The *unfoldingWord Simplified Text* (UST) is designed to be used in conjunction with the *unfoldingWord Literal Text* (ULT) and the translationNotes as a tool for Bible translation. Unlike the ULT and unlike an end-user Bible, the UST does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the UST is to show the plain meaning of all of those things wherever they occur in the ULT. Because the UST lacks these things, it is not a beautiful end-user Bible. An end-user Bible will use the figures of speech and idioms that speak naturally and beautifully in the target language, but the UST does not use them. As the Other Language translator uses both the UST and the ULT together as his translation source, he will be able to see the figures of speech, idioms, and other forms of the original Bible in the ULT and also see what their meaning is in the UST. Then he can use the figures of speech or other forms from the ULT that are clear and natural in his language. When the forms in the ULT are not clear or natural in his language, then he can choose other forms in his language that have the same meaning as the UST translation or the Notes. When translating the UST, please do not use idioms, figures of speech, or difficult grammatical forms in the Gateway Language translation. The purpose of the UST is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible.
The :abbr:`UST (unfoldingWord Simplified Text)` is designed to be used in conjunction with the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`tN (translationNotes)` as a tool for Bible translation. Unlike the :abbr:`ULT (unfoldingWord Literal Text)` and unlike an end-user Bible, the :abbr:`UST (unfoldingWord Simplified Text)` does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the :abbr:`UST (unfoldingWord Simplified Text)` is to show the plain meaning of all of those things wherever they occur in the :abbr:`ULT (unfoldingWord Literal Text)`. Because the :abbr:`UST (unfoldingWord Simplified Text)` lacks these things, it is not a beautiful end-user Bible. An end-user Bible will use the figures of speech and idioms that speak naturally and beautifully in the target language, but the :abbr:`UST (unfoldingWord Simplified Text)` does not use them.
The primary goal of the UST is to express the meaning of the Bible as clearly as possible. In order to do this, it follows these guidelines.
As the :abbr:`OL (Other Language)` translator uses both the :abbr:`UST (unfoldingWord Simplified Text)` and the :abbr:`ULT (unfoldingWord Literal Text)` together as his translation source, he will be able to see the figures of speech, idioms, and other forms of the original Bible in the :abbr:`ULT (unfoldingWord Literal Text)` and also see what their meaning is in the :abbr:`UST (unfoldingWord Simplified Text)`. Then he can use the figures of speech or other forms from the :abbr:`ULT (unfoldingWord Literal Text)` that are clear and natural in his language. When the forms in the :abbr:`ULT (unfoldingWord Literal Text)` are not clear or natural in his language, then he can choose other forms in his language that have the same meaning as the :abbr:`UST (unfoldingWord Simplified Text)` translation or the Notes. When translating the :abbr:`UST (unfoldingWord Simplified Text)`, please do not use idioms, figures of speech, or difficult grammatical forms in the :abbr:`GL (Gateway Language)` translation. The purpose of the :abbr:`UST (unfoldingWord Simplified Text)` is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible.
The UST must avoid:
1. Idioms
2. Figures of speech
3. Events out of order
4. Difficult or specialized grammar
a. Complex sentences
b. Passive voice
c. Abstract or verbal nouns
d. People speaking of themselves in third person
The UST must explicitly include:
1. Participants where these are unclear
2. Implied information that is necessary for understanding
The primary goal of the :abbr:`UST (unfoldingWord Simplified Text)` is to express the meaning of the Bible as clearly as possible. In order to do this, it follows these guidelines.
When translating the UST, please do not use those things that it must avoid in the Gateway Language translation. The purpose of the UST is to change all of those problematic forms into more universal ones to make them easier to translate. Also, be sure to include all of the named participants and the information that has been made explicit so that the meaning can be as clear as possible.
The :abbr:`UST (unfoldingWord Simplified Text)` must avoid:
1. Idioms
2. Figures of speech
3. Events out of order
4. Difficult or specialized grammar:
a. Complex sentences
b. Passive voice
c. Abstract or verbal nouns
d. People speaking of themselves in third person
The :abbr:`UST (unfoldingWord Simplified Text)` must explicitly include:
1. Participants where these are unclear
2. Implied information that is necessary for understanding
When translating the :abbr:`UST (unfoldingWord Simplified Text)`, please do not use those things that it must avoid in the :abbr:`GL (Gateway Language)` translation. The purpose of the :abbr:`UST (unfoldingWord Simplified Text)` is to change all of those problematic forms into more universal ones to make them easier to translate. Also, be sure to include all of the named participants and the information that has been made explicit so that the meaning can be as clear as possible.
What method should be used to translate the UST?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
When translating the UST, keep the English source open in front of you. This means that you should not use any methodology that includes a step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the UST is a tool that carefully avoids certain structures that can be difficult to translate in some languages, as explained above. If the translator is using blind drafting, he might accidentally replace the simple structures of the UST with structures that are natural in the target Gateway Language but unwanted in the UST, such as idioms and figures of speech from the target GL. In order to guard against replacing these structures, it is best to translate the UST with the English source text open to look at.
When translating the :abbr:`UST (unfoldingWord Simplified Text)`, keep the English source open in front of you. This means that you should not use any methodology that includes a step of blind drafting. The reason for this is that blind drafting is a method that translators use in order to produce natural target language translations. Through blind drafting, the translator replaces structures from the source language that would be unnatural in the target language with structures that are natural for that target language. But the :abbr:`UST (unfoldingWord Simplified Text)` is a tool that carefully avoids certain structures that can be difficult to translate in some languages, as explained above. If the translator is using blind drafting, he might accidentally replace the simple structures of the :abbr:`UST (unfoldingWord Simplified Text)` with structures that are natural in the target :abbr:`GL (Gateway Language)` but unwanted in the :abbr:`UST (unfoldingWord Simplified Text)`, such as idioms and figures of speech from the target :abbr:`GL (Gateway Language)`. In order to guard against replacing these structures, it is best to translate the :abbr:`UST (unfoldingWord Simplified Text)` with the English source text open to look at.
Does Translation of the UST Require a Back Translation?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We expect that the people translating the UST into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. For this reason, back translations of the UST will usually not be necessary. The exception to this will be if the translation of the UST is done by a secular translation company. In this case, a back translation into English may be necessary, done according to the guidelines set forth in `Back Translation <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md>`_ and following modules.
.. include:: /includes/glchurchcapacity.txt
.. include:: /includes/backtranslation.txt
Examples
^^^^^^^^
The following are examples of ways that the text of the Bible can be unclear for some languages and what the UST does to overcome those problems. When you translate the UST, make sure that your translation of the UST also avoids these problems.
The following are examples of ways that the text of the Bible can be unclear for some languages and what the :abbr:`UST (unfoldingWord Simplified Text)` does to overcome those problems. When you translate the :abbr:`UST (unfoldingWord Simplified Text)`, make sure that your translation of the :abbr:`UST (unfoldingWord Simplified Text)` also avoids these problems.
Passive Voice
"""""""""""""
Passive voice is a grammatical construction that is common in Greek and English but it is not used in many other languages, so it can be very confusing. For that reason, it is not used in the UST. In passive voice, the receiver of the action changes places with the actor. In English, the actor normally comes first in the sentence. But in passive voice, the receiver of the action comes first. Often, the actor is left unstated. In that case, the UST will fill in the actor. See "Missing Participants" below.
Passive voice is a grammatical construction that is common in Greek and English but it is not used in many other languages, so it can be very confusing. For that reason, it is not used in the :abbr:`UST (unfoldingWord Simplified Text)`. In passive voice, the receiver of the action changes places with the actor. In English, the actor normally comes first in the sentence. But in passive voice, the receiver of the action comes first. Often, the actor is left unstated. In that case, the :abbr:`UST (unfoldingWord Simplified Text)` will fill in the actor. See "Missing Participants" below.
For example, the ULT of Romans 2:24 says, "... the name of God is dishonored among the Gentiles because of you."
For example, the :abbr:`ULT (unfoldingWord Literal Text)` of Romans 2:24 says, "... the name of God is dishonored among the Gentiles because of you."
The action is "dishonor," the actors are "the Gentiles" (non-Jews), and the receiver of the action is "the name of God." The reason for the action is "because of you."
The UST rearranges the verse to put the actor and the receiver of the action in a more normal order. It says, "The non-Jews speak evil about God because of the evil actions of you Jews." This is more clear for many languages. When you translate the UST, make sure that you do not use any passive voice constructions.
The :abbr:`UST (unfoldingWord Simplified Text)` rearranges the verse to put the actor and the receiver of the action in a more normal order. It says, "The non-Jews speak evil about God because of the evil actions of you Jews." This is more clear for many languages. When you translate the :abbr:`UST (unfoldingWord Simplified Text)`, make sure that you do not use any passive voice constructions.
Abstract Nouns
""""""""""""""
The ULT of Romans 2:10 says, "But praise, honor, and peace will come to everyone who practices good..."
The :abbr:`ULT (unfoldingWord Literal Text)` of Romans 2:10 says, "But praise, honor, and peace will come to everyone who practices good..."
In this verse, the words "praise," "honor," "peace," and "good" are abstract nouns. That is, they are words that refer to things that we cannot see or touch. They are ideas. The ideas that these nouns express are closer to actions or descriptions than they are to things. In many languages, therefore, these ideas must be expressed by verbs or description words, not by nouns.
For this reason, the UST expresses these nouns as actions or descriptions. It says, "But God will praise, honor, and give a peaceful spirit to every person who habitually does good deeds."
For this reason, the :abbr:`UST (unfoldingWord Simplified Text)` expresses these nouns as actions or descriptions. It says, "But God will praise, honor, and give a peaceful spirit to every person who habitually does good deeds."
When translating the UST, avoid using abstract nouns. For more information on abstract nouns, see `Abstract Nouns <https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_abstractnouns.md>`_.
When translating the :abbr:`UST (unfoldingWord Simplified Text)`, avoid using abstract nouns. For more information on abstract nouns, see `Abstract Nouns <https://git.door43.org/Door43/en-ta-translate-vol2/src/master/content/figs_abstractnouns.md>`_.
Long, Complex Sentences
"""""""""""""""""""""""
The UST avoids using long or complex sentences. In many languages, long or complex sentences are unnatural and unclear.
The :abbr:`UST (unfoldingWord Simplified Text)` avoids using long or complex sentences. In many languages, long or complex sentences are unnatural and unclear.
The ULT translates the first three verses of Romans as one complex sentence. It says, "<sup>1</sup> Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God, <sup>2</sup> which he promised beforehand by his prophets in the holy scriptures, <sup>3</sup> concerning his Son, who was born from the descendants of David according to the flesh."
The :abbr:`ULT (unfoldingWord Literal Text)` translates the first three verses of Romans as one complex sentence. It says,
The UST breaks that into five sentences that are more simple in form. It says, "<sup>1</sup> I, Paul, who serve Christ Jesus, am writing this letter to all of you believers in the city of Rome. God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him. <sup>2</sup> Long before Jesus came to earth, God promised that he would reveal this good news by means of what his prophets wrote in the sacred scriptures. <sup>3</sup> This good news is about his Son. As to his Son's physical nature, he was born a descendant of King David."
:sup:`1`\ Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God, :sup:`2`\ which he promised beforehand by his prophets in the holy scriptures, :sup:`3`\ concerning his Son, who was born from the descendants of David according to the flesh.
When translating the UST, keep the sentences short and simple.
The :abbr:`UST (unfoldingWord Simplified Text)` breaks that into five sentences that are more simple in form. It says,
:sup:`1`\ I, Paul, who serve Christ Jesus, am writing this letter to all of you believers in the city of Rome. God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him. :sup:`2`\ Long before Jesus came to earth, God promised that he would reveal this good news by means of what his prophets wrote in the sacred scriptures. :sup:`3`\ This good news is about his Son. As to his Son's physical nature, he was born a descendant of King David.
When translating the :abbr:`UST (unfoldingWord Simplified Text)`, keep the sentences short and simple.
Missing Participants
""""""""""""""""""""
The UST often fills in the participants when these are lacking in the original Bible and the ULT. In the original biblical languages, these participants could be left out and still understood by the reader. But in many languages these must be included for the translation to be clear and natural.
The :abbr:`UST (unfoldingWord Simplified Text)` often fills in the participants when these are lacking in the original Bible and the :abbr:`ULT (unfoldingWord Literal Text)`. In the original biblical languages, these participants could be left out and still understood by the reader. But in many languages these must be included for the translation to be clear and natural.
In the ULT, Romans 1:1 says, "Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God..."
In the :abbr:`ULT (unfoldingWord Literal Text)`, Romans 1:1 says, "Paul, a servant of Jesus Christ, called to be an apostle, set apart for the gospel of God..."
In this verse, there is a participant that is left unstated, but still understood. This participant is God. It is God who called Paul to be an apostle and who set him apart for the Gospel. In some languages, this participant must be stated.
In this verse, there is a participant that is left unstated, but still understood. This participant is God. It is God who called Paul to be an apostle and who set him apart for the Gospel. In some languages, this participant must be stated.
Therefore the UST of Romans 1:1 says, "God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him."
Therefore the :abbr:`UST (unfoldingWord Simplified Text)` of Romans 1:1 says, "God chose me to be an apostle, and he appointed me in order that I should proclaim the good news that comes from him."
When translating the UST, be sure to include all of the participants that are there in the UST.
When translating the :abbr:`UST (unfoldingWord Simplified Text)`, be sure to include all of the participants that are there in the :abbr:`UST (unfoldingWord Simplified Text)`.
Events out of Order
"""""""""""""""""""
The ULT of Luke 2:6-7 says, "<sup>6</sup> Now it came about that while they were there, the time came for her to deliver her baby. <sup>7</sup> She gave birth to a son, her firstborn child, and she wrapped him snugly in strips of cloth. Then she put him in an animal feeding trough, because there was no room for them in a guest room."
The :abbr:`ULT (unfoldingWord Literal Text)` of Luke 2:6-7 says,
In some languages, events need to be told in the order in which they happened, or else the story will be confusing and hard to understand. People might understand from these verses that Mary delivered her baby outside in the street, and then looked for somewhere to stay and, after a long search, ended up putting him in an animal feeding trough.
:sup:`6`\ Now it came about that while they were there, the time came for her to deliver her baby. :sup:`7`\ She gave birth to a son, her firstborn child, and she wrapped him snugly in strips of cloth. Then she put him in an animal feeding trough, because there was no room for them in a guest room.
The UST tells these events in the order in which they happened, so that it is clear that Mary was already in the shelter for animals when she gave birth. It says, "<sup>6-7</sup> When they arrived in Bethlehem, there was no place for them to stay in a place where visitors usually stayed. So they had to stay in a place where animals slept overnight. While they were there the time came for Mary to give birth and she gave birth to her first child, a son. She wrapped him in wide strips of cloth and placed him in the feeding place for the animals."
In some languages, events need to be told in the order in which they happened, or else the story will be confusing and hard to understand. People might understand from these verses that Mary delivered her baby outside in the street, and then looked for somewhere to stay and, after a long search, ended up putting him in an animal feeding trough.
The :abbr:`UST (unfoldingWord Simplified Text)` tells these events in the order in which they happened, so that it is clear that Mary was already in the shelter for animals when she gave birth. It says,
:sup:`6-7`\ When they arrived in Bethlehem, there was no place for them to stay in a place where visitors usually stayed. So they had to stay in a place where animals slept overnight. While they were there the time came for Mary to give birth and she gave birth to her first child, a son. She wrapped him in wide strips of cloth and placed him in the feeding place for the animals.
Figures of Speech
"""""""""""""""""
The ULT of Romans 2:21 says, "You who preach not to steal, do you steal?"
The :abbr:`ULT (unfoldingWord Literal Text)` of Romans 2:21 says, "You who preach not to steal, do you steal?"
This is a figure of speech called a rhetorical question. It is not a real question that is used to seek an answer. It is used to make a point. In this case, Paul is using it to scold his audience and to condemn their hypocrisy. Many languages do not use rhetorical questions, or they do not use them in this way.
This is a figure of speech called a rhetorical question. It is not a real question that is used to seek an answer. It is used to make a point. In this case, Paul is using it to scold his audience and to condemn their hypocrisy. Many languages do not use rhetorical questions, or they do not use them in this way.
To show how to translate this meaning without a rhetorical question, the UST says, "You who preach that people should not steal things, it is disgusting that you yourself steal things!"
When you translate the UST, be sure to not use rhetorical questions or other figures of speech. (For more examples of figures of speech, see `Figures of Speech <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_intro.md>`_ and the modules linked there.)
To show how to translate this meaning without a rhetorical question, the :abbr:`UST (unfoldingWord Simplified Text)` says, "You who preach that people should not steal things, it is disgusting that you yourself steal things!"
When you translate the :abbr:`UST (unfoldingWord Simplified Text)`, be sure to not use rhetorical questions or other figures of speech. (For more examples of figures of speech, see `Figures of Speech <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_intro.md>`_ and the modules linked there.)
Idioms
""""""
The ULT of Deuteronomy 32:10 says, "he guarded him as the apple of his eye."
The :abbr:`ULT (unfoldingWord Literal Text)` of Deuteronomy 32:10 says, "he guarded him as the apple of his eye."
The word "apple" here does not refer to a kind of fruit, but instead refers to the pupil, the dark center of a person's eye. The phrase "the apple of his eye" is an idiom that refers to anything that is extremely precious to a person, or the one thing that is the most precious to a person. In many languages this idiom makes no sense, but they have other idioms that have this meaning. The Other Language translator should use one of these idioms from the target language in the OL translation, but there should be no idiom in the translation of the UST.
The word "apple" here does not refer to a kind of fruit, but instead refers to the pupil, the dark center of a person's eye. The phrase "the apple of his eye" is an idiom that refers to anything that is extremely precious to a person, or the one thing that is the most precious to a person. In many languages this idiom makes no sense, but they have other idioms that have this meaning. The :abbr:`OL (Other Language)` translator should use one of these idioms from the target language in the :abbr:`OL (Other Language)` translation, but there should be no idiom in the translation of the :abbr:`UST (unfoldingWord Simplified Text)`.
To show the meaning of this verse, the UST expresses this in plain language, without an idiom. It says, "He protected them and took care of them, as every person takes good care of his own eyes."
To show the meaning of this verse, the :abbr:`UST (unfoldingWord Simplified Text)` expresses this in plain language, without an idiom. It says, "He protected them and took care of them, as every person takes good care of his own eyes."
The Notes add another way to translate this that makes the meaning clear. It says, "He protected the people of Israel as something most valuable and precious." When you translate the UST, be sure that you do not use any idioms. Only use plain language that makes the meaning clear. (For more information on idioms, see `Idiom <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_idiom.md>`_.)
The Notes add another way to translate this that makes the meaning clear. It says, "He protected the people of Israel as something most valuable and precious." When you translate the :abbr:`UST (unfoldingWord Simplified Text)`, be sure that you do not use any idioms. Only use plain language that makes the meaning clear. (For more information on idioms, see `Idiom <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/figs_idiom.md>`_.)
(For more examples of how the UST avoids difficult grammatical constructions, idioms, and figures of speech, see the section of examples in `Translating the ULT <https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_ulb.md>`_.)
(For more examples of how the :abbr:`UST (unfoldingWord Simplified Text)` avoids difficult grammatical constructions, idioms, and figures of speech, see the section of examples in `Translating the ULT <https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_ulb.md>`_.)
People Speaking of Themselves in Third Person
"""""""""""""""""""""""""""""""""""""""""""""
The ULT of Genesis 18:3 says:
The :abbr:`ULT (unfoldingWord Literal Text)` of Genesis 18:3 says:
He said, "My Lord, if I have found favor in your eyes, please do not pass by your servant."
Here Abraham refers to himself in the third person as "your servant." To make it clear that Abraham is referring to himself, the UST adds the first person pronoun "me."
Here Abraham refers to himself in the third person as "your servant." To make it clear that Abraham is referring to himself, the :abbr:`UST (unfoldingWord Simplified Text)` adds the first person pronoun "me."
The UST of Genesis 18:3 says:
The :abbr:`UST (unfoldingWord Simplified Text)` of Genesis 18:3 says:
He said to one of them, "My Lord, if you are pleased with me, then please stay here with me, your servant, for a little while."
When editing or translating the UST, be sure to include the indications of the first person that are there in these passages of the UST so that it can be as clear as possible.
When editing or translating the :abbr:`UST (unfoldingWord Simplified Text)`, be sure to include the indications of the first person that are there in these passages of the :abbr:`UST (unfoldingWord Simplified Text)` so that it can be as clear as possible.
Implied Information
"""""""""""""""""""
The ULT of Mark 1:44 says:
The :abbr:`ULT (unfoldingWord Literal Text)` of Mark 1:44 says:
He said to him, "Be sure to say nothing to anyone, but go, show yourself to the priest, and offer for your cleansing what Moses commanded, as a testimony to them."
He said to him, "Be sure to say nothing to anyone, but go, show yourself to the priest, and offer for your cleansing what Moses commanded, as a testimony to them."
This was all that Jesus needed to say to the man whom he had just healed of leprosy, because the man was Jewish and knew all about the laws concerning being clean and unclean. But most modern readers of our Bible translations do not know that information. For that reason, the UST makes this information explicit that was left implied in the text. This information is indicated in italics below.
This was all that Jesus needed to say to the man whom he had just healed of leprosy, because the man was Jewish and knew all about the laws concerning being clean and unclean. But most modern readers of our Bible translations do not know that information. For that reason, the :abbr:`UST (unfoldingWord Simplified Text)` makes this information explicit that was left implied in the text. This information is indicated in italics below.
The UST of Mark 1:44 says:
The :abbr:`UST (unfoldingWord Simplified Text)` of Mark 1:44 says:
UST: He said, "Do not tell anyone what just happened. Instead, go to a priest and show yourself to him in order that he may examine you and see that you no longer have leprosy. Then make the offering that Moses commanded for people whom God has healed from leprosy. This will be the testimony to the community that you are healed."
He said, "Do not tell anyone what just happened. Instead, go to a priest and show yourself to him in order that he may examine you and see that you no longer have leprosy. Then make the offering that Moses commanded for people whom God has healed from leprosy. This will be the testimony to the community that you are healed."
When editing or translating the UST, be sure to include all of the implied information that is there in the UST so that it can be as clear as possible.
When editing or translating the :abbr:`UST (unfoldingWord Simplified Text)`, be sure to include all of the implied information that is there in the :abbr:`UST (unfoldingWord Simplified Text)` so that it can be as clear as possible.
.. seealso:: :ref:`glchecking-checkingudb`, :ref:`gltranslation-transulb`
@ -276,13 +304,13 @@ Adapt the ULT
Prerequisites for Adapting an Existing Translation for the ULT
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**What is needed to adapt an existing translation and use it as the ULT for a Gateway Language (GL)?**
**What is needed to adapt an existing translation and use it as the ULT for a GL?**
In order to adapt an existing translation and use it as the ULT for a Gateway Language (GL), it is necessary that the existing translation be a literal translation. That is, it should follow the same order of clauses as the original biblical languages and reproduce the original biblical idioms and figures of speech. Most Bibles that were translated into Gateway Languages in the first half of the twentieth century or earlier are literal translations.
In order to adapt an existing translation and use it as the :abbr:`ULT (unfoldingWord Literal Text)` for a :abbr:`GL (Gateway Language)`, it is necessary that the existing translation be a literal translation. That is, it should follow the same order of clauses as the original biblical languages and reproduce the original biblical idioms and figures of speech. Most Bibles that were translated into :abbr:`GLs (Gateway Languages)` in the first half of the twentieth century or earlier are literal translations.
It is also necessary that the Bible that you adapt as the ULT not be encumbered by copyright. That means that it must be in the public domain or have a license that permits us to reproduce and translate it. (For more information on copyrights and licensing, see `Open License <https://git.door43.org/Door43/en-ta-intro/src/master/content/open_license.md>`_.)
It is also necessary that the Bible that you adapt as the :abbr:`ULT (unfoldingWord Literal Text)` not be encumbered by copyright. That means that it must be in the public domain or have a license that permits us to reproduce and translate it. (For more information on copyrights and licensing, see `Open License <https://git.door43.org/Door43/en-ta-intro/src/master/content/open_license.md>`_.)
If the Bible is very old, you will need to update the language and the style so that it uses words that people use now and "talks" in the way that people talk now. Even though the ULT has a literal style, it must use words that people know so that they can understand it.
If the Bible is very old, you will need to update the language and the style so that it uses words that people use now and "talks" in the way that people talk now. Even though the :abbr:`ULT (unfoldingWord Literal Text)` has a literal style, it must use words that people know so that they can understand it.
Methodology for Adapting an Existing Translation for the ULT
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -291,26 +319,28 @@ Methodology for Adapting an Existing Translation for the ULT
Because adapting an existing translation is a process of editing rather than of translating, you should not try to follow any translation methodology. Especially do not follow any methodology that uses blind drafting. Instead, you should follow these steps:
#. Read the chapter in the English ULT and the Notes for that chapter. If you are beginning to translate a book, also read the overview of the book.
#. Read the chapter in the Bible that you are adapting as the ULT.
#. Go through the chapter and change old words to words that people use now.
#. Using the list of translationWords for that chapter, check to make sure that a good translation for each of those words is used in the Gateway Language ULT.
#. If some sentences are put together in a strange way, check to see if they are also that way in the English ULT.
#. Read the chapter in the English :abbr:`ULT (unfoldingWord Literal Text)` and the Notes for that chapter. If you are beginning to translate a book, also read the overview of the book.
#. Read the chapter in the Bible that you are adapting as the :abbr:`ULT (unfoldingWord Literal Text)`.
#. Go through the chapter and change old words to words that people use now.
#. Using the list of :abbr:`tW (translationWords)` for that chapter, check to make sure that a good translation for each of those words is used in the Gateway Language :abbr:`ULT (unfoldingWord Literal Text)`.
#. If some sentences are put together in a strange way, check to see if they are also that way in the English :abbr:`ULT (unfoldingWord Literal Text)`.
#. If the sentences are also put together in that same strange way in the English ULT, it is because the original Bible has that structure. Leave them as they are. There will be a Note that will explain that structure.
#. If the sentences are not put together in that same strange way in the English ULT, then change the sentence so that it is clearer for modern readers.
a. If the sentences are also put together in that same strange way in the English :abbr:`ULT (unfoldingWord Literal Text)`, it is because the original Bible has that structure. Leave them as they are. There will be a note that will explain that structure.
b. If the sentences are not put together in that same strange way in the English :abbr:`ULT (unfoldingWord Literal Text)`, then change the sentence so that it is clearer for modern readers.
#. If you see that any verse or phrase in the Bible that you are adapting is very different than the English ULT, then change it so that it is more like the English ULT.
#. If you see that any verse is missing in the Bible that you are adapting but it is there in the English ULT, then translate that verse from the English ULT.
#. If you see that any verse or phrase in the Bible that you are adapting is very different than the English :abbr:`ULT (unfoldingWord Literal Text)`, then change it so that it is more like the English :abbr:`ULT (unfoldingWord Literal Text)`.
#. If you see that any verse is missing in the Bible that you are adapting but it is there in the English :abbr:`ULT (unfoldingWord Literal Text)`, then translate that verse from the English :abbr:`ULT (unfoldingWord Literal Text)`.
After you do these things so that the text is ready to use as the Gateway Language ULT, you will need to translate the translationNotes. As you translate the translationNotes, you may see that there are parts of your adapted ULT that should be different so that the translationNote can make sense. Also, you may see that some translationNotes need to be changed so that they can refer to the right parts of the adapted ULT. In this way, you will need to make changes to both the Gateway Language ULT and the Notes as you adapt them to each other so that they make sense and are truly helpful for the OL translator. (For more information about this process, see `Translate the translationNotes <https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_notes.md>`_.)
After you do these things so that the text is ready to use as the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`, you will need to translate the :abbr:`tN (translationNotes)`. As you translate the :abbr:`tN (translationNotes)`, you may see that there are parts of your adapted :abbr:`ULT (unfoldingWord Literal Text)` that should be different so that the note can make sense. Also, you may see that some :abbr:`tN (translationNotes)` need to be changed so that they can refer to the right parts of the adapted :abbr:`ULT (unfoldingWord Literal Text)`. In this way, you will need to make changes to both the Gateway Language :abbr:`ULT (unfoldingWord Literal Text)` and the Notes as you adapt them to each other so that they make sense and are truly helpful for the :abbr:`OL (Other Language)` translator. (For more information about this process, see `Translate the translationNotes <https://git.door43.org/Door43/en-ta-gl/src/master/content/gl_notes.md>`_.)
Does Adapting a Translation of the ULT Require a Back Translation?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
**How does the church ensure the translation conforms to these guidelines?**
We expect that the translation that has been adapted as the ULT already went through a series of checks to ensure that it accurately reflects the original meaning of the biblical text. This would have been done by the entity that originally translated and published the Bible translation. We also expect that the people adapting this translation for use as the ULT in the Gateway Language will be well-educated and have good theological training. They will also be connected into church networks that will have adequate resources for checking the adapted translation. For this reason, back translations of the adapted ULT will usually not be necessary. The exception to this will be if the adaptation of the translation is done by a secular translation company, and there is no church network that speaks the Gateway Language that is available to check the adaptation. In this unlikely event, we will need to also request a back translation into English, done according to the guidelines set forth in `Back Translation <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md>`_ and following modules.
We expect that the translation that has been adapted as the :abbr:`ULT (unfoldingWord Literal Text)` already went through a series of checks to ensure that it accurately reflects the original meaning of the biblical text. This would have been done by the entity that originally translated and published the Bible translation. We also expect that the people adapting this translation for use as the :abbr:`ULT (unfoldingWord Literal Text)` in the Gateway Language will be well-educated and have good theological training. They will also be connected into church networks that will have adequate resources for checking the adapted translation.
.. include:: /includes/backtranslation.txt
.. _gltranslation-transtn:
@ -324,29 +354,30 @@ Translate the translationNotes
Guidelines
^^^^^^^^^^
translationNotes offer alternative ways to translate a phrase from the ULT. It is important that the phrase that you use to translate this kind of translationNote be a direct substitute for the phrase that it replaces in the ULT. In other words, the phrase has to have the same grammatical construction as the phrase in the ULT. That is, it needs to fit into the sentence in the ULT just like the original phrase did. In order to make sure that the phrase in the GL Note fits the sentence in the GL ULT, you must be able to always look at both the English translationNote and the GL ULT as you translate. Translating the translationNotes while having the source visible, therefore, is the most efficient way to translate them and this will also reduce the number of errors in translation. (For more information on the types of translationNotes, see `Using the translationNotes <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/resources_types.md>`_.)
:abbr:`tN (translationNotes)` offer alternative ways to translate a phrase from the :abbr:`ULT (unfoldingWord Literal Text)`. It is important that the phrase that you use to translate this kind of note be a direct substitute for the phrase that it replaces in the :abbr:`ULT (unfoldingWord Literal Text)`. In other words, the phrase has to have the same grammatical construction as the phrase in the :abbr:`ULT (unfoldingWord Literal Text)`. It needs to fit into the sentence in the :abbr:`ULT (unfoldingWord Literal Text)` just like the original phrase did.
Does the entire Bible need to be translated first?
""""""""""""""""""""""""""""""""""""""""""""""""""
In order to make sure that the phrase in the :abbr:`GL (Gateway Language)` note fits the sentence in the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`, you must be able to always look at both the English note and the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` as you translate. Translating the :abbr:`tN (translationNotes)` while having the source visible is the most efficient way to translate them and this will also reduce the number of errors in translation. (For more information on the types of :abbr:`tN (translationNotes)`, see `Using the translationNotes <https://git.door43.org/Door43/en-ta-translate-vol1/src/master/content/resources_types.md>`_.)
It is not necessary to have the **entire** ULT and UST Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
.. include:: /includes/entirebiblefirst.txt
When I am translating the notes, do I need the ULT and UST available and translated?
When I am translating the notes, do I need the ULT and UST available and translated?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
When you translate the translationNotes for a book of the Bible, you must also have both the ULT and the UST in front of you, already translated into the target Gateway Language in final form for that book. You must have the ULT available so that you can copy the part of the ULT text that the translationNote is talking about directly into the translationNote. You must also have the UST text already translated and available, because the translationNotes often copy part of the UST text in order to show another way to translate the same part of the verse. Other times, the translationNote does not quote the UST but it does refer to it. In that case, you need to be able to see what the UST says in order to translate the translationNote in the best way.
When you translate the :abbr:`tN (translationNotes)` for a book of the Bible, you must also have both the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)` in front of you, already translated into the target Gateway Language in final form for that book. You must have the :abbr:`ULT (unfoldingWord Literal Text)` available so that you can copy the part of the :abbr:`ULT (unfoldingWord Literal Text)` text that the note is talking about directly into the note. You must also have the :abbr:`UST (unfoldingWord Simplified Text)` text already translated and available, because the :abbr:`tN (translationNotes)` often copy part of the :abbr:`UST (unfoldingWord Simplified Text)` text in order to show another way to translate the same part of the verse. Other times, the note does not quote the :abbr:`UST (unfoldingWord Simplified Text)` but it does refer to it. In that case, you need to be able to see what the :abbr:`UST (unfoldingWord Simplified Text)` says in order to translate the note in the best way.
In addition, the translationNotes directly comment on parts of the ULT text, so you must read the part of the ULT text that the translationNote comments on in order to properly translate the translationNote. After you read and understand the ULT text, then you can translate the translationNote so that it makes sense together with the ULT text that it refers to.
In addition, the :abbr:`tN (translationNotes)` directly comment on parts of the :abbr:`ULT (unfoldingWord Literal Text)` text, so you must read the part of the :abbr:`ULT (unfoldingWord Literal Text)` text that the note comments on in order to properly translate the translationNote. After you read and understand the :abbr:`ULT (unfoldingWord Literal Text)` text, then you can translate the note so that it makes sense together with the :abbr:`ULT (unfoldingWord Literal Text)` text that it refers to.
May I use blind drafting?
"""""""""""""""""""""""""
Do not use any method that includes blind drafting to translate the translationNotes. Always translate the translationNotes with the Gateway Language ULT and UST in front of you, and the English translationNotes also visible. This is because you must copy the ULT phrase into the translationNote exactly as it is in the ULT, and you must also copy the UST phrase if the translationNote also quotes the UST.
Do not use any method that includes blind drafting to translate the :abbr:`tN (translationNotes)`. Always translate the :abbr:`tN (translationNotes)` with the Gateway Language :abbr:`ULT (unfoldingWord Literal Text)` and :abbr:`UST (unfoldingWord Simplified Text)` in front of you, and the English :abbr:`tN (translationNotes)` also visible. This is because you must copy the :abbr:`ULT (unfoldingWord Literal Text)` phrase into the note exactly as it is in the :abbr:`ULT (unfoldingWord Literal Text)`, and you must also copy the :abbr:`UST (unfoldingWord Simplified Text)` phrase if the note also quotes the :abbr:`UST (unfoldingWord Simplified Text)`.
How does the church ensure the translation conforms to these guidelines?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
We expect that the people translating the translationNotes into the Gateway Languages will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages. Becuase the translationNotes talk about grammar and figures of speech, it is highly recommended that the people translating them into the GL have training in linguistics as well as in biblical studies. They will need to know how to adapt the translationNotes for the grammar of the GL.
.. include:: /includes/glchurchcapacity.txt
Becuase the :abbr:`tN (translationNotes)` talk about grammar and figures of speech, it is highly recommended that the people translating them into the :abbr:`GL (Gateway Language)` have training in linguistics as well as in biblical studies. They will need to know how to adapt the :abbr:`tN (translationNotes)` for the grammar of the :abbr:`GL (Gateway Language)`.
Adapting the translationNotes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -354,21 +385,25 @@ Adapting the translationNotes
May I change a note so that it makes sense in my language?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Often, the ULT in the target Gateway Language will say things in a different way than the ULT said them in English. In order for the translationNote to be useful in the target Gateway Language, you will need to adapt the translationNote so that it talks about the text of the ULT as it is in the Gateway Language translation. This means that you will need to copy the phrase of the Gateway ULT that is the translation of the same phrase from the English ULT into the translationNote, and then sometimes change the translationNote so that it makes sense and is helpful for the Other Language translator who will use these translationNotes as translation tools.
Often, the :abbr:`ULT (unfoldingWord Literal Text)` in the target :abbr:`GL (Gateway Language)` will say things in a different way than the :abbr:`ULT (unfoldingWord Literal Text)` said them in English. In order for the note to be useful in the target :abbr:`GL (Gateway Language)`, you will need to adapt the note so that it talks about the text of the :abbr:`ULT (unfoldingWord Literal Text)` as it is in the :abbr:`GL (Gateway Language)` translation.
This means that you will need to copy the phrase of the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` that is the translation of the same phrase from the English :abbr:`ULT (unfoldingWord Literal Text)` into the translationNote, and then sometimes change the note so that it makes sense and is helpful for the :abbr:`OL (Other Language)` translator who will use these :abbr:`tN (translationNotes)` as translation tools.
May I delete a note that does not apply to my language?
"""""""""""""""""""""""""""""""""""""""""""""""""""""""
Because languages can be very different from each other, sometimes there will be translationNotes that are important and necessary for some languages, but that are not needed for other languages. If there is a translationNote that does not make sense when applied to the ULT text in the target Gateway Language, then you as the translator will need to modify the translationNote so that it does make sense in relation to the ULT in your target Gateway Language. If the translationNote does not apply at all to the target GL text of the ULT, then you may delete that note from your translation of the translationNotes. But be sure to think about it very carefully before you delete a translationNote, to be sure that it is not necessary for the Other Language translator who will be using the GL translation.
Because languages can be very different from each other, sometimes there will be :abbr:`tN (translationNotes)` that are important and necessary for some languages, but that are not needed for other languages. If there is a note that does not make sense when applied to the :abbr:`ULT (unfoldingWord Literal Text)` text in the target :abbr:`GL (Gateway Language)`, then you as the translator will need to modify the note so that it does make sense in relation to the :abbr:`ULT (unfoldingWord Literal Text)` in your target :abbr:`GL (Gateway Language)`.
If the note does not apply at all to the target :abbr:`GL (Gateway Language)` text of the :abbr:`ULT (unfoldingWord Literal Text)`, then you may delete that note from your translation of the :abbr:`tN (translationNotes)`. But be sure to think about it very carefully before you delete a translationNote, to be sure that it is not necessary for the :abbr:`OL (Other Language)` translator who will be using the :abbr:`GL (Gateway Language)` translation.
May I add a note that would help with translation in my language?
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
For the same reason, sometimes you will realize that the Other Language translator will need a translationNote in order to understand a phrase in the target Gateway Language ULT, but there might not be a translationNote already written for that phrase, because it was not necessary for the English ULT. In that case, you will need to write a new translationNote and include it in your translation. Usually these translationNotes will be to explain a phrase or way of saying something that is normal in the Gateway Language but that is not normal in the Other Languages that you know of. When writing your translationNote, follow the same style and format of the existing translationNotes.
For the same reason, sometimes you will realize that the :abbr:`OL (Other Language)` translator will need a note in order to understand a phrase in the target :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`, but there might not be a note already written for that phrase, because it was not necessary for the English :abbr:`ULT (unfoldingWord Literal Text)`. In that case, you will need to write a new note and include it in your translation. Usually these :abbr:`tN (translationNotes)` will be to explain a phrase or way of saying something that is normal in the :abbr:`GL (Gateway Language)` but that is not normal in the :abbr:`OLs (Other Languages)` that you know of. When writing your translationNote, follow the same style and format of the existing :abbr:`tN (translationNotes)`.
Remember that speakers of many different languages will be using these Gateway Language translationNotes to help them translate the Bible. There will be many things that you will understand about the Bible in the Gateway Language that the OL translator may not understand. For that reason, if you think that there is something difficult to understand in the GL ULT, write a translationNote that can help the OL translator to understand it. There will probably be many Other Language translators who will benefit from reading the translationNote and who will make a better translation because of it.
Remember that speakers of many different languages will be using these :abbr:`GL (Gateway Language)` :abbr:`tN (translationNotes)` to help them translate the Bible. There will be many things that you will understand about the Bible in the :abbr:`GL (Gateway Language)` that the :abbr:`OL (Other Language)` translator may not understand. For that reason, if you think that there is something difficult to understand in the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`, write a note that can help the :abbr:`OL (Other Language)` translator to understand it. There will probably be many :abbr:`OL (Other Language)` translators who will benefit from reading the note and who will make a better translation because of it.
Because the translationNotes need to be adapted in these ways and not simply translated, it is best if the people adapting the translationNotes be people who are well educated in both linguistics and biblical studies so that they can understand the various problems that the translationNotes explain.
Because the :abbr:`tN (translationNotes)` need to be adapted in these ways and not simply translated, it is best if the people adapting the :abbr:`tN (translationNotes)` be people who are well educated in both linguistics and biblical studies so that they can understand the various problems that the :abbr:`tN (translationNotes)` explain.
.. seealso:: :ref:`glchecking-checkingtn`, :ref:`gltranslation-transtw`, :ref:`gltranslation-transtq`
@ -384,35 +419,36 @@ Translating translationWords
Guidelines
^^^^^^^^^^
It is important that the Other Language translators understand all of the words that they are translating. But some of the words in the Bible are not used in everyday life in our time or in our cultures, and so the translator may not be familiar with them. Other words are used in everyday life, but they are used in a different way in the Bible. Some of these words have very important or special meanings in the Bible. They tell us a lot about God and his relationship with us. So in order for the Other Language translator to completely understand these words, we have provided the definitions in translationWords. When you translate this list into the Gateway Language, it will help all of the Other Language translators who will use it to translate the Bible for their people with good understanding.
It is important that the :abbr:`OL (Other Language)` translators understand all of the words that they are translating. But some of the words in the Bible are not used in everyday life in our time or in our cultures, and so the translator may not be familiar with them. Other words are used in everyday life, but they are used in a different way in the Bible. Some of these words have very important or special meanings in the Bible. They tell us a lot about God and his relationship with us.
Does the entire Bible need to be translated first?
""""""""""""""""""""""""""""""""""""""""""""
In order for the :abbr:`OL (Other Language)` translator to completely understand these words, we have provided the definitions in :abbr:`tW (translationWords)`. When you translate this list into the :abbr:`GL (Gateway Language)`, it will help all of the :abbr:`OL (Other Language)` translators who will use it to translate the Bible for their people with good understanding.
It is not necessary to have the **entire** ULT and UST Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
.. include:: /includes/entirebiblefirst.txt
What is the "Definition" section of translationWords?
"""""""""""""""""""""""""""""""""""""""""""""""""""""
tW entries have several parts; the first part is "Definition." This gives the meaning of the word as it is used in the Bible. Please do not use definitions from a modern Gateway Language dictionary, because the way words are used in the Bible can be different from the way they are used in modern, everyday life. We want to make sure that the Other Language translator understands the way that the word is used in the Bible.
:abbr:`tW (translationWords)` entries have several parts; the first part is "Definition." This gives the meaning of the word as it is used in the Bible. Please do not use definitions from a modern :abbr:`GL (Gateway Language)` dictionary, because the way words are used in the Bible can be different from the way they are used in modern, everyday life. We want to make sure that the :abbr:`OL (Other Language)` translator understands the way that the word is used in the Bible.
It is possible that the Gateway Language might express the idea of the English tW by using different words for that idea in different contexts. That is, the GL may use different words when the idea is talked about in different ways. Each of these GL words for the tW word may have a part of the meaning of the English word. In this case, you will need to list each of those words at the top, separated by commas. Several of the English tW entries already have multiple words at the top like this, such as "prophet, prophecy, prophesy, seer, prophetess" (see https://door43.org/en/obe/kt/prophet ). Then, in the "Definition" part, you will need to list those words in separate paragraphs with a definition for each one. The Other Language translator can then choose the word that he needs to understand from that list and translate it correctly in the passage that he is translating.
It is possible that the :abbr:`GL (Gateway Language)` might express the idea of the English :abbr:`tW (translationWords)` by using different words for that idea in different contexts. That is, the :abbr:`GL (Gateway Language)` may use different words when the idea is talked about in different ways. Each of these :abbr:`GL (Gateway Language)` words for the :abbr:`tW (translationWords)` word may have a part of the meaning of the English word.
In this case, you will need to list each of those words at the top, separated by commas. Several of the English :abbr:`tW (translationWords)` entries already have multiple words at the top like this, such as "prophet, prophecy, prophesy, seer, prophetess" (see the `Prophet tW article <https://git.door43.org/unfoldingWord/en_tw/src/branch/master/bible/kt/prophet.md>`_). Then, in the "Definition" part, you will need to list those words in separate paragraphs with a definition for each one. The :abbr:`OL (Other Language)` translator can then choose the word that he needs to understand from that list and translate it correctly in the passage that he is translating.
What is the "Translation Suggestions" section of translationWords?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
The second part of a tW entry is "Translation Suggestions" or "Translation Strategies." This section gives different ideas for how the Other Language translator can translate the word. This section gives more than one way to translate the word because it can mean slightly different things in different contexts. Be sure that you understand the differences of meaning between the different contexts in which the word is used so that you can translate them correctly.
The second part of a :abbr:`tW (translationWords)` entry is "Translation Suggestions" or "Translation Strategies." This section gives different ideas for how the :abbr:`OL (Other Language)` translator can translate the word. This section gives more than one way to translate the word because it can mean slightly different things in different contexts. Be sure that you understand the differences of meaning between the different contexts in which the word is used so that you can translate them correctly.
In the Gateway Language, some of the translationWords are not used in all of the same contexts as the English translationWords are. **In that case, you will need to adjust your translation**. If one of the Translation Suggestions does not work in the Gateway Language, then do not translate that Translation Suggestion. Instead, write a Translation Suggestion that shows how that word is used in the Gateway Language. Think about the different ways that the word is used in the Bible, and try to make sure that there is a Translation Suggestion for each of the primary uses. We want the Other Language translator to see and consider the differences and the similarity in meaning between the uses of the word so that he can choose the best word in his language to express those meanings.
In the :abbr:`GL (Gateway Language)`, some of the :abbr:`tW (translationWords)` are not used in all of the same contexts as the English :abbr:`tW (translationWords)` are. **In that case, you will need to adjust your translation**. If one of the Translation Suggestions does not work in the :abbr:`GL (Gateway Language)`, then do not translate that Translation Suggestion. Instead, write a Translation Suggestion that shows how that word is used in the :abbr:`GL (Gateway Language)`. Think about the different ways that the word is used in the Bible, and try to make sure that there is a Translation Suggestion for each of the primary uses. We want the :abbr:`OL (Other Language)` translator to see and consider the differences and the similarity in meaning between the uses of the word so that he can choose the best word in his language to express those meanings.
As you translate the ULT and UST, you may find that you need to add a meaning to a word in the tW entry, or you may need to add another word to the entry because the Gateway Language uses more than one word for the idea of that important tW. Go ahead and do this as you find more words or meanings for the words.
As you translate the :abbr:`ULT (unfoldingWord Literal Text)` and :abbr:`UST (unfoldingWord Simplified Text)`, you may find that you need to add a meaning to a word in the :abbr:`tW (translationWords)` entry, or you may need to add another word to the entry because the :abbr:`GL (Gateway Language)` uses more than one word for the idea of that important :abbr:`tW (translationWords)`. Go ahead and do this as you find more words or meanings for the words.
Under the "Translation Suggestions" or "Translation Strategies" section is a line that says, "(See also...)." You only need to translate the words "See also," and you only need to translate this one time, not for every tW. The rest of the line will be created automatically, if the translation is done in translationStudio Desktop.
Under the "Translation Suggestions" or "Translation Strategies" section is a line that says, "(See also...)." You only need to translate the words "See also," and you only need to translate this one time, not for every :abbr:`tW (translationWords)`. The rest of the line will be created automatically, if the translation is done in translationStudio Desktop.
Do I translate the "Bible References" and "Examples for the Bible Stories" sections of translationWords?
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
The third and fourth parts are "Bible References" and "Examples from the Bible Stories." You only need to translate these words of the titles, and you only need to translate them one time, not for every tW. You do not need to translate the rest of these parts. They will be created automatically, if the translation is done in translationStudio Desktop.
The third and fourth parts are "Bible References" and "Examples from the Bible Stories." You only need to translate these words of the titles, and you only need to translate them one time, not for every :abbr:`tW (translationWords)`. You do not need to translate the rest of these parts. They will be created automatically, if the translation is done in translationStudio Desktop.
.. seealso:: :ref:`gltranslation-transtn`, :ref:`gltranslation-transtq`
@ -428,25 +464,22 @@ Translating translationQuestions
Guidelines
^^^^^^^^^^
We want all translations of the Bible to communicate clearly the message that God wants them to communicate. One tool that we are providing so that the OL translators can make sure that their translations are communicating correctly is translationQuestions (tQ). The OL translators will use tQ to conduct community checks of each chapter of the Bible that they translate.
We want all translations of the Bible to communicate clearly the message that God wants them to communicate. One tool that we are providing so that the :abbr:`OL (Other Language)` translators can make sure that their translations are communicating correctly is translationQuestions (:abbr:`tQ (translationQuestions)`). The :abbr:`OL (Other Language)` translators will use :abbr:`tQ (translationQuestions)` to conduct community checks of each chapter of the Bible that they translate.
Does the entire Bible need to be translated first?
""""""""""""""""""""""""""""""""""""""""""""""""""
It is not necessary to have the **entire** ULT and UST Bible translated before translating the helps (tN, tW, tQ). The translation of these resources for a book could be started after the translation of that book is complete.
.. include:: /includes/entirebiblefirst.txt
What Is the Recommended Method for Translating tQ?
""""""""""""""""""""""""""""""""""""""""""""""""""
#. Read the chapter of the ULT that the Questions are about, so that you understand it.
#. Translate only the question part of each question-answer pair. Draft all of the Questions for one chapter.
#. In the self-edit stage of checking, edit each Question to correct any mistakes or to add things that you left out.
#. Instead of translating the answer to each question, copy the answer from the words of the Gateway Language ULT of that verse that match the answer to that question in the English source. In this way, the words of each answer will always match the words of the Gateway Language ULT.
#. Read the chapter of the :abbr:`ULT (unfoldingWord Literal Text)` that the questions are about, so that you understand it.
#. Translate only the question part of each question-answer pair. Draft all of the questions for one chapter.
#. In the self-edit stage of checking, edit each Question to correct any mistakes or to add things that you left out.
#. Instead of translating the answer to each question, copy the answer from the words of the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)` of that verse that match the answer to that question in the English source. In this way, the words of each answer will always match the words of the :abbr:`GL (Gateway Language)` :abbr:`ULT (unfoldingWord Literal Text)`.
If the ULT Has Not Been Translated
""""""""""""""""""""""""""""""""""
In order to translate the Questions for a book of the Bible, the ULT of that book must be translated already. The purpose of the Questions is to check the translation of the ULT, so it serves no purpose to translate the Questions first.
In order to translate the questions for a book of the Bible, the :abbr:`ULT (unfoldingWord Literal Text)` of that book must be translated already. The purpose of the questions is to check the translation of the :abbr:`ULT (unfoldingWord Literal Text)`, so it serves no purpose to translate the questions first.
.. seealso:: :ref:`gltranslation-transtn`, :ref:`gltranslation-transtq`, :ref:`glchecking-checkingtn`, :ref:`glchecking-checkingulb`
@ -462,13 +495,13 @@ Translating translationAcademy
Recommended Training and Experience
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
translationAcademy contains many lessons on specialized topics, such as language, translation issues, and biblical studies. Some of the vocabulary is also specialized. We recommend that the people who translate tA into a Gateway Language have a **college-level education or some training and experience in the particular area that they are translating**. For example, if you are translating the Translation Manual, it would be good if you have training and experience in linguistics and translation. You will be able to translate more accurately and clearly if you have experience in the topic.
:abbr:`tA (translationAcademy)` contains many lessons on specialized topics, such as language, translation issues, and biblical studies. Some of the vocabulary is also specialized. We recommend that the people who translate :abbr:`tA (translationAcademy)` into a :abbr:`GL (Gateway Language)` have a **college-level education or some training and experience in the particular area that they are translating**. For example, if you are translating the Translation Manual, it would be good if you have training and experience in linguistics and translation. You will be able to translate more accurately and clearly if you have experience in the topic.
This means that you will want to have **several specialists** on your translation team, with each specialist translating the parts that they are most familiar with. If you find that some lessons are unclear, discuss the problem with other members of the team until you understand what the lesson is trying to teach. You cannot translate something that you do not understand. If you try to do that, the Other Language translator will not be able to understand it, either, or be able to use it.
This means that you will want to have **several specialists** on your translation team, with each specialist translating the parts that they are most familiar with. If you find that some lessons are unclear, discuss the problem with other members of the team until you understand what the lesson is trying to teach. You cannot translate something that you do not understand. If you try to do that, the :abbr:`OL (Other Language)` translator will not be able to understand it, either, or be able to use it.
Recommended Reference Materials
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We recommend that you use specialized dictionaries as you translate to hep you understand the concepts that you are translating. Do not use unusual or technical words in your translation if there is a simpler way to communicate the same thing. Remember that the OL translators speak the Gateway Language as a second language, so they will not know unusual or technical words. Try to keep the lessons uncomplicated and clear, using simple language as much as you can. We have tried to write the lessons of tA using simple language, so please follow this same style.
We recommend that you use specialized dictionaries as you translate to hep you understand the concepts that you are translating. Do not use unusual or technical words in your translation if there is a simpler way to communicate the same thing. Remember that the :abbr:`OL (Other Language)` translators speak the :abbr:`GL (Gateway Language)` as a second language, so they will not know unusual or technical words. Try to keep the lessons uncomplicated and clear, using simple language as much as you can. We have tried to write the lessons of :abbr:`tA (translationAcademy)` using simple language, so please follow this same style.
.. seealso:: :ref:`glchecking-checkingtn`, :ref:`glchecking-checkingulb`

3
docs/includes/backtranslation.txt Normal file
View File

@ -0,0 +1,3 @@
For these reasons, back translations of the text will usually not be necessary.
An exception to this is if the translation was done by a secular translation company.
In this case, either a church network that speaks that GL will need to check the translation or a back translation into English may be necessary, done according to the guidelines set forth in `Back Translation <https://git.door43.org/Door43/en-ta-checking-vol2/src/master/content/vol2_backtranslation.md>`_ and following modules.

4
docs/includes/entirebiblefirst.txt Normal file
View File

@ -0,0 +1,4 @@
Does the entire Bible need to be translated first?
""""""""""""""""""""""""""""""""""""""""""""""""""
It is not necessary to have the **entire** :abbr:`ULT (unfoldingWord Literal Text)` and :abbr:`UST (unfoldingWord Simplified Text)` Bible translated before translating the helps (:abbr:`tN (translationNotes)`, :abbr:`tW (translationWords)`, :abbr:`tQ (translationQuestions)`). The translation of these resources for a book could be started after the translation of that book is complete.

1
docs/includes/glchurchcapacity.txt Normal file
View File

@ -0,0 +1 @@
We expect that the people translating the text into the :abbr:`GL (Gateway Language)` will be well-educated and have good theological training. They will be connected into church networks that will have adequate resources for checking the translations against the English source as well as the original biblical languages.

8
docs/index.rst
View File

@ -3,8 +3,16 @@
Gateway Language Manual
=======================
The Gateway Language Manual is for the use of translators and checkers of the Gateway Language resources. See the `Gateway Languages Strategy <https://unfoldingword.org/gateway/>`_ web page for more information on the Gateway Languages of the world.
The latest version of this document is available as a `PDF here <http://readthedocs.org/projects/gl-manual/downloads/pdf/latest/>`_.
Table of Contents
-----------------
.. toctree::
:maxdepth: 2
gl_translation
gl_checking
gl_alignment