DCS-Mirror
/
Door43-Catalog_en_ult
mirror of https://git.door43.org/Door43-Catalog/en_ult
2
0
Fork 0
Files Issues Releases Wiki Activity See in Reader

Fix formatting problems (#2081)

This commit is contained in:
Joel D. Ruark 2019-11-25 14:11:10 +00:00 committed by Gogs
parent bcb025503a
commit 44b2e5dce4
1 changed files with 11 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
README.md
View File

@ -112,7 +112,6 @@ Preferred English renderings appear in bold type.
* *gospel* **gospel** will be used in most cases in the ULT, while the UST will use “good news.”
* *hagioi* When referring to people, “**saints**.” When referring to heavenly beings, “**holy ones**.”
### Notes About Making a “Literal” Translation
1. It is not possible to maintain a one-for-one correspondence between words in translation. One word from the source language may require a phrase for its translation in the target language, and vice-versa.
@ -121,7 +120,6 @@ Preferred English renderings appear in bold type.
4. Greek makes abundant use of participial clauses. For the English of the ULT to make sense, often this must be changed to a relative or adverbial clause.
5. The general rule is, retain the structures of the original unless English sense does not allow it. If not, make the adjustments necessary.
### The ULT Contrasted with the UST
The ULT seeks to represent the language **forms** of the original in a way that also makes sense in English and other Gateway Languages. The UST (unfoldingWord® Simplified Text) seeks to represent the **plain meaning** of the original Bible text. This means that:
@ -144,17 +142,16 @@ The words of the original language (Greek, Hebrew, or Aramaic) text for that ver
To align the GL text:
#. 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 the GL word by releasing the mouse button.
* 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 the GL word by releasing the mouse button.
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 Unmerge Notes
^^^^^^^^^^^^^^^^^^^^^^^
#### Merge and Unmerge Notes
tC 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.
translationCore 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 original language 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 original language word, simply drag and drop the GL words onto the box below the desired original language word.
* When it is desired to align GL 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.
@ -163,12 +160,11 @@ tC supports one-to-one, one-to-many, many-to-one, and many-to-many alignments. T
* Any GL 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
--------------------
### Alignment Philosophy for the ULT
Because each GL will have different requirements for sentence structure and the amount of explicit information that must be provided there is often not a one-to-one correspondence of the original language word and the GL word. In these cases, the GL 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.
For English, we follow these principles, but your GL 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.
@ -186,9 +182,6 @@ Other alignment issues pertinent to Biblical Hebrew include the following:
* When aligning a verbless clause in Hebrew, the supplied "to be" verb should usually be aligned with the predicate instead of the subject. An exception to this rule occurs when the subject is a demonstrative pronoun (or carries some sort of deictic function). In those cases, the supplied "to be" verb should be aligned with the subject of the verbless clause.
* Sometimes a verb in Hebrew requires an accompanying preposition that is not required in English, or vice versa. In these cases, align with whichever part of speech fits best on a case-by-case basis. For example, take the phrase "...to pay on our fields..." in Nehemiah 14:4 in the UST. The English preposition "on" fits better semantically with the noun ("on our fields") rather than with the infinitive ("to pay on"). However, the reverse is true in v.15 in the phrase "...even their servants oppressed the people..." (Heb. שׁלטוּ על־העמ). In this case, the Hebrew שׁלט requires an accompanying preposition, and the concept is already incorporated into the English translation of the verb itself, "oppressed." So in this case, it is best to merge the Hebrew verb and preposition together, then align both with the English "oppressed."
Alignment Philosophy for the ULT
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The 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 GL. Ideally, then, there would be one GL 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 GL 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 GL words to the original language words whose meaning they express, in whatever combination is necessary to produce the most accurate alignment of the meaning.
@ -206,15 +199,12 @@ In the above cases, if you are an authorized editor, you will want to edit the :
If you notice places where the ULT (unfoldingWord Literal Text) is wrong or potentially wrong, create an issue for it at https://git.door43.org/unfoldingWord/en_ult/issues and we’ll address it in the next release. In the meantime, align the text as well as possible.
.. _glalignment-wordsnotfound:
Words Not Found in the Original Language
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#### Words Not Found in the Original Language
In the process of alignment according to the instructions above, you may find that the :abbr:`GL (Gateway Language)` text has words or phrases that do not represent any meaning in the original language text and are not there because the GL sentence needs them to make sense. If this occurs, follow these recommendations:
#. If possible, consider editing the GL text to match the original language text.
#. You may consult other Greek or Hebrew manuscripts to see if there is textual support for your translation (see the `Biblical Humanities Dashboard <http://biblicalhumanities.org/dashboard/>` for other manuscripts).
#. If you find support for your translation, make sure to include a comment or note about where you found it and why the translation should include it.
#. You should consider placing these GL words in brackets or in a footnote.
* If possible, consider editing the GL text to match the original language text.
* You may consult other Greek or Hebrew manuscripts to see if there is textual support for your translation (see the `Biblical Humanities Dashboard <http://biblicalhumanities.org/dashboard/>` for other manuscripts).
* If you find support for your translation, make sure to include a comment or note about where you found it and why the translation should include it.
* You should consider placing these GL words in brackets or in a footnote.