Update 'README.md' (#2239)

This commit is contained in:
Joel D. Ruark 2020-08-19 04:43:31 +00:00 committed by Gogs
parent b8056b8306
commit 5d2a78f731
1 changed files with 7 additions and 7 deletions

View File

@ -5,7 +5,7 @@
## Overview
The ULT (English) is an open-licensed adaptation of *The American Standard Version*, intended to provide a form-centric rendering of the biblical text from the original languages (Biblical Hebrew, Biblical Aramaic, and Koiné Greek) into English. This increases a translators understanding of the lexical and grammatical composition of the biblical text by adhering closely to the grammatical (i.e. parts of speech) and syntactic (i.e. word order) stuctures of the original languages.
The ULT (English) is an open-licensed adaptation of *The American Standard Version*, intended to provide a form-centric rendering of the biblical text from the original biblical languages (Biblical Hebrew, Biblical Aramaic, and Koiné Greek) into English. This increases a translators understanding of the lexical and grammatical composition of the biblical text by adhering closely to the grammatical (i.e. parts of speech) and syntactic (i.e. word order) stuctures of the original languages.
## Viewing
@ -20,7 +20,7 @@ file.
## Introducing the ULT
The ULT (unfoldingWord® Literal Text) is a form-centric (and thus “literal”) version of the Bible in English. It is intended to be used alongside the UST (unfoldingWord® Simplified Text) and other translation resources to give English-speaking mother-tongue translators (MTTs) a more complete understanding of the messages communicated in the Bible. For MTTs who do not have reading knowledge of the Original biblical Languages (Hebrew, Aramaic, Greek), the ULT provides a sense of *how* these messages were communicated in those Original Languages (OrigL). It is anticipated that the ULT and other resources will be translated from English into the worlds Gateway Languages (GLs) so that MTTs worldwide can use them as a set of resources for making accurate translations of the Bible into their own languages.
The ULT (unfoldingWord® Literal Text) is a form-centric (and thus “literal”) version of the Bible in English. It is intended to be used alongside the UST (unfoldingWord® Simplified Text) and other translation resources to give English-speaking mother-tongue translators (MTTs) a more complete understanding of the messages communicated in the Bible. The purpose of the ULT text is to allow a Bible translator who does not have reading knowledge of the Original biblical Languages (Hebrew, Aramaic, Greek) to "see" the grammatical forms of those languages as best they can." Therefore goal of the ULT text as a translation resource is to copy the Original Language (OrigL) form as much as possible yet still be understandable in a Gateway Language (GL) For MTTs who cannot read the OrigL text, the ULT provides a sense of *how* these messages of the Bible were communicated in the OrigL. It is anticipated that the ULT and other resources will be translated from English into the worlds GLs so that MTTs worldwide can use them as a set of resources for making accurate translations of the Bible into their own languages.
As aligned in the translationCore (tCore) software, the ULT stands in the range of literalness somewhere between a very literally translated user Bible (such as the New American Standard Bible [NASB]) and an English interlinear text. An English interlinear text is designed to render OrigL words into their individual and literal English meanings without regard to understandability of the overall English text. On the other hand, a very literally translated user Bible tries to adhere as closely as possible to the OrigL but must sometimes compromise in favor of English idiom and expression in order for the text to be both grammatically correct and readily understood. The aligned ULT negotiates a path somewhere between these two kinds of texts. The ULT seeks to use the English language in order to reproduce the OrigL linguistic forms as closely as possible. Thus, the ULT is a degree "more literal" than a literally-translated user Bible such as the NASB. However, the ULT still meets the demand of reasonable understandability in English. Thus, the ULT is a degree "less literal" than an English interlinear text.
@ -82,7 +82,7 @@ Here are some guidelines for composing or editing biblical text in the ULT:
* Capitalization: in general, follow the practice of the 2011 NIV.
* All pronouns are lower case (even when referring to God) except when a pronoun begins a sentence. Of course, the first person singular ("I") is always capitalized.
* Proper titles should be capitalized (Son of Man, King David, the Messiah).
* Retain the literal nature of the text. The ULT should complement the UST rather than be similar to it.
* Retain the grammatical parts of the speech and syntactic expressions of the OrigL as much as is understandable in the GL. The ULT should complement the UST rather than be similar to it.
* Use vocabulary and phrases that differ from the UST as much as possible. The complementary tools fail to help the MTT when they are the same.
* Where possible, use common vocabulary that is easy to translate into another language.
* Spell out numbers up to and including ten (e.g., one, two…). For numbers larger than ten, use numerals (e.g., 11, 12…).
@ -112,16 +112,16 @@ NOTE: Occasionally, the TGs specified translation will not be suitable. As al
Preferred English renderings for the ULT appear in bold type.
* *brethren* should be updated to **brothers**. When both genders are indicated by the context, a note from the Notes team should be expected to appear to that effect. Do not replace the ULT text with “brothers and sisters.”
* *Call* in the ASV usage “call his name”: update to “**call him** [+ name]” or “**name him** [+ name].”
* *Call* in the formula of the type, “he shall be called the Son of the Most High” (Luke 1:32): keep this formula in the ULT, but be aware of the metaphor that is operative here: in this verse, Jesus will not only be *called the Son of the Most High*, but he will be the Son of the Most High.
* *Hand* indicating power or possession: keep this metaphor in the ULT.
* Sentence-initial or preverbal *and* of the type, “And Joseph said,” “And it came about,” etc.: these should be rendered in English somehow, usually as the conjunction "**and**." However, a different conjunction ("**but**", "**so**", etc.) may be selected in cases where a specific logical relationship is clear from the context.
* **Shall** vs. **will** : in English future expressions in general, use “**will**” instead of “shall,” e.g., “he is a prophet, and he <del>shall</del> **will** pray for you” (Gen 20:7). Note that some ASV future expressions are better updated into todays English by using the present tense, e.g., “I shall not drink from…the fruit of the vine, until the kingdom of God shall come” (Luke 22:18) can be updated to “I **will** not drink…until the kingdom of God **comes**.” Cases in which “shall” expresses obligation can usually be restructured, e.g., “You shall not steal” becomes “ **Do** not steal;” and, “Shall I go and smite these Philistines?” (1 Sam. 23:2) becomes “**Should** I go and attack these Philistines?” This general preference for “will” probably conforms to the instincts of most English native speakers. However, in genres such as prophecies, blessings, curses, and in other passages focusing on the expression of the speakers intentionality, retain the use of “shall” in the ULT. For example: “Yahweh said, **Shall** I hide from Abraham what I am about to do…?’” (Gen 18:17); “A deliverer **shall** come to Zion;” “every mountain and hill **shall** be made low.”
* Sentence-initial or preverbal *and* of the type, “And Joseph said,” “And it came about,” etc.: these should be rendered in English somehow, usually as the conjunction "**and**." However, a different word ("**but**", "**so**", etc.) may be selected in rare cases, where the discourse function of the conjunction is foregrounded and the specific conjunctive meaning is so strong as to be contextually undeniable.
* **Shall** vs. **will** : in English future expressions in general, use “**will**” instead of “shall,” e.g., “he is a prophet, and he <del>shall</del> **will** pray for you” (Gen 20:7). Note that some ASV future expressions are better updated into todays English by using the present tense, e.g., “I shall not drink from…the fruit of the vine, until the kingdom of God shall come” (Luke 22:18) can be updated to “I **will** not drink…until the kingdom of God **comes**.” This general preference for “will” probably conforms to the instincts of most English native speakers. However, in genres such as prophecies, blessings, curses, and in other passages focusing on the expression of the speakers intentionality, retain the use of “shall” in the ULT. For example: “Yahweh said, **Shall** I hide from Abraham what I am about to do…?’” (Gen 18:17); “A deliverer **shall** come to Zion;” “every mountain and hill **shall** be made low.”
### Translation Glossary for the Old Testament
* *adam* (ASV: man, men) When referring to humanity in general, use “**mankind**.”
* *'af* should be rendered "**nose** when it appears in the singular form and **nostrils** when it appears in the dual form.
* *'al* (עַל) When used causatively, this preposition should be rendered "**on account of**" to differentiate it from the causative use of מִן. When used quatitatively, this preposition should be rendered "**in accordance with**" to differentiate it from the quantitative use of כְּ. However, these are only general principles. The specific translation gloss used should always be determined by the specific context.
* *Ark of the Covenant* The ULT will use the word "**Box**" ("Box of the Testimony" in Exodus, "Box of the Covenant of Yahweh" in Joshua, etc.), and the UST will use the term "**sacred chest**."
* *be* (בְּ) As a general rule, this preposition should usually be rendered as "**in**," "**at**," or "**by**." However, the specific translation gloss used should always be determined by the specific context.
@ -138,7 +138,7 @@ Preferred English renderings for the ULT appear in bold type.
* *kapporeth* (כַּפֹּרֶת) "**atonement lid**"
* *ke* (כְּ) When used quantitatively, this preposition should be rendered "**according to**" to differentiate it from the quantitative use of עַל. However, this is only a general principle. The specific translation gloss used should always be determined by the specific context.
* *koh 'amar yhwh* (כֹּה אָמַר יהוה) "**Thus says Yahweh**"
* *lifney* (לִפְנֵי) This should be rendered as a phrase and not as a single preposition, either "**to the face of**" or "**before the face of**," etc.
* *lifney* (לִפְנֵי) This should be rendered as a phrase and not as a single preposition, usually either "**to the face of**" or "**before the face of**," etc.
* *Meshiach* “**Messiah**” (almost always, “**the Messiah**,” since “Messiah” is a title)
* *min* (מִן) When used causatively, this preposition should be rendered "**because of**." However, this is only a general principle. The specific translation gloss used should always be determined by the specific context.
* *mishpat* (מִשְׁפָּט) should be rendered "**judgments**" wherever possible, because it is the derivative noun of שׁפט (to judge). However, in instances where it clearly does not mean "judgments", then the English term "**ordinance**" should be used when referring to a religious rule, and another word such as "**regulation**" when referring to a more civil or legal rule.