Corrected Luke format Co-authored-by: Larry Sallee <email@example.com> Reviewed-on: #2506 Co-Authored-By: Larry Sallee <firstname.lastname@example.org> Co-Committed-By: Larry Sallee <email@example.com>
|15 hours ago|
|.github||4 months ago|
|.gitattributes||4 years ago|
|.gitignore||5 years ago|
|01-GEN.usfm||8 months ago|
|02-EXO.usfm||2 days ago|
|03-LEV.usfm||1 year ago|
|04-NUM.usfm||1 year ago|
|05-DEU.usfm||1 year ago|
|06-JOS.usfm||2 years ago|
|07-JDG.usfm||2 years ago|
|08-RUT.usfm||6 months ago|
|09-1SA.usfm||1 year ago|
|10-2SA.usfm||1 year ago|
|11-1KI.usfm||2 years ago|
|12-2KI.usfm||1 year ago|
|13-1CH.usfm||1 year ago|
|14-2CH.usfm||1 year ago|
|15-EZR.usfm||4 months ago|
|16-NEH.usfm||6 months ago|
|17-EST.usfm||3 days ago|
|18-JOB.usfm||1 year ago|
|19-PSA.usfm||1 year ago|
|20-PRO.usfm||1 year ago|
|21-ECC.usfm||1 year ago|
|22-SNG.usfm||1 year ago|
|23-ISA.usfm||1 year ago|
|24-JER.usfm||1 year ago|
|25-LAM.usfm||1 year ago|
|26-EZK.usfm||1 year ago|
|27-DAN.usfm||9 months ago|
|28-HOS.usfm||1 year ago|
|29-JOL.usfm||2 years ago|
|30-AMO.usfm||1 year ago|
|31-OBA.usfm||2 months ago|
|32-JON.usfm||6 months ago|
|33-MIC.usfm||1 year ago|
|34-NAM.usfm||2 years ago|
|35-HAB.usfm||1 year ago|
|36-ZEP.usfm||1 year ago|
|37-HAG.usfm||1 year ago|
|38-ZEC.usfm||1 year ago|
|39-MAL.usfm||1 year ago|
|41-MAT.usfm||2 months ago|
|42-MRK.usfm||2 months ago|
|43-LUK.usfm||15 hours ago|
|44-JHN.usfm||4 weeks ago|
|45-ACT.usfm||7 days ago|
|46-ROM.usfm||2 weeks ago|
|47-1CO.usfm||2 months ago|
|48-2CO.usfm||2 months ago|
|49-GAL.usfm||4 months ago|
|50-EPH.usfm||2 months ago|
|51-PHP.usfm||2 months ago|
|52-COL.usfm||2 months ago|
|53-1TH.usfm||2 months ago|
|54-2TH.usfm||2 months ago|
|55-1TI.usfm||5 months ago|
|56-2TI.usfm||2 months ago|
|57-TIT.usfm||2 months ago|
|58-PHM.usfm||4 months ago|
|59-HEB.usfm||2 months ago|
|60-JAS.usfm||2 days ago|
|61-1PE.usfm||2 months ago|
|62-2PE.usfm||2 months ago|
|63-1JN.usfm||2 months ago|
|64-2JN.usfm||2 months ago|
|65-3JN.usfm||3 months ago|
|66-JUD.usfm||2 months ago|
|67-REV.usfm||2 months ago|
|LICENSE.md||2 months ago|
|README.md||4 weeks ago|
|manifest.yaml Valid||3 days ago|
|media.yaml||3 years ago|
an unrestricted literal version of the Bible intended for translation into any language as a tool for use by Bible translators
The ULT began as an open-licensed adaptation of The American Standard Version. It has since undergone a careful comparison to the original biblical languages, using the best tools that are available to modern scholarship, and made to reflect the forms of those languages as far as English grammar and understanding will allow. The ULT is thus 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 translator’s 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. For translators who do not speak English, we intend to translate the ULT into the other major languages of the world.
To read or print the ULT, see the ULT project on Door43.
If you are a contributor to this project please add your name to the
field in the manifest.yaml
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. Therefore, the 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 English or other 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 world’s 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 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 basic (“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 ULT negotiates a path between these two kinds of texts. For example, the ULT reproduces the OrigL idioms even when they are not English idioms, relying on a translation note to explain the meaning. In that way, the translator can see the original expression, and also the meaning. The ULT does not substitute English idioms or expressions. However, if an OrigL grammatical form would give the wrong meaning or no meaning at all, the ULT will use the English form in that case so that the ULT can also meet the demand of reasonable understandability in English.
The unfoldingWord® Literal Text (ULT) is designed to be used as a tool for Bible translation in conjunction with the unfoldingWord® Simplified Text (UST), the unfoldingWord® Translation Words (UTW), and the unfoldingWord® Translation Notes (UTN). It is not an end-user Bible, which seeks to transform all of the structures of the original biblical languages into those that are natural and idiomatic in the target language. Instead, unlike the UST and unlike an end-user Bible, the ULT is designed to reflect the forms of the source languages, so that the MTT can see what they are. By using the ULT, the MTT can “look through” it to see how the original Bible expressed the biblical ideas.
Therefore, as you (an editor or translator of the ULT) edit or translate the ULT, you must retain the grammatical and syntactic structures of the original as much as the target language (English or other Gateway Language) will reasonably allow. If the original structure is ungrammatical in the target language, then you will need to change it into a structure that is grammatical in the target language. It does no good to make a translation that a MTT using this tool cannot understand. But as much as the target language will allow, retain the structures of the original while editing or translating the ULT. For English, it is often possible to retain nouns as nouns, verbs as verbs, etc., but their order in the original sentence must be changed.
In addition to the grammatical forms, the ULT must also retain the idioms and the figures of speech found in the original languages so that the MTT can consider them and use them if they communicate the right thing in his target language (i.e. a minority or Other Language [OL], not Gateway Language). If these aspects of the original language text are changed in the English version (or other Gateway Language translation) of the ULT, then the OL translator will never see them. Furthermore, their accompanying explanations (found in the unfoldingWord® Translation Notes) will not make sense.
The ULT and the UST are designed to be complementary tools for use by an OL translator. These tools should be as useful as possible, which means that the ULT should retain original language structures that would not always be retained in an end-user Bible. Therefore, you must understand that the ULT will often lack naturalness (and sometimes also lack clarity) because it aims to reproduce the original language structures and figures of speech that the GL may not normally use. However, in places where the ULT lacks clarity, there will be BOTH a Translation Note to explain the meaning of the structure for the OL translator AND a clear rendering of the original meaning in the UST. Together, the UTN and the UST will provide the meaning of the text wherever that meaning is in doubt in the ULT. In this way, the various tools work together to provide an OL translator with more complete information about both the form and the meaning of the biblical text as written in the original languages.
One specific way in which the ULT and UST are complementary tools concerns the selection of meaning in the original language texts. There are many instances in the biblical text where the meaning of a word or phrase in the original languages is ambiguous. In those cases, the ULT should retain the ambiguity of meaning, if possible. In contrast, the UST should select the most probable meaning and express that meaning according to its own translation method. NOTE: It is acceptable for the ULT to select meaning in cases where the meaning of the original language is linguistically ambiguous but seems clear from the context.
For examples see the Examples portion of the Gateway Language Manual.
See the The ULT Contrasted with the UST in the Gateway Language Manual.
See Specific Editing Guidelines for the ULT in the Gateway Language Manual.
Both Biblical Hebrew and Koiné Greek utilize different word forms to indicate grammatical gender, which may or may not correspond either to the actual gender of a person or to the lack of gender in an object. For example, the Hebrew phrase beney yisrael (“sons of Israel”) sometimes literally means “male children of the man named Israel” (Gen 42:5). However, most of the time in the Old Testament this phrase refers figuratively to the entire Israelite nation as a whole, both men and women. In a similar way, the Greek term adelphoi (“brothers”) can sometimes literally mean “a male person who has the same father and/or mother” (Mark 3:22), but most of the time in the New Testament refers figuratively to Christian believers, both men and women. This linguistic feature of “engendered language” poses significant problems for translation. The meaning of the original Hebrew/Aramaic/Greek text is not always clear; also, some languages do not use engendered language, which makes the translation of gender very difficult.
The ULT should retain the engendered language of Hebrew/Aramaic/Greek terms as much as possible. However, a notable exception to this rule concerns the translation of masculine participles (that is, verbal nouns and/or verbal adjectives) which actually refer to both men and women together; those terms can be translated without specifying gender.
See the Combined ULT-UST Translation Glossary in the Gateway Language Manual.
See the Translation Glossary for the Old Testament in the Gateway Language Manual.
See the Translation Glossary for the New Testament in the Gateway Language Manual.
See the Notes About Making a “Literal” Translation section in the Gateway Language Manual.
In the tC (translationCore) Word Alignment tool, the English 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 OrigL (Hebrew, Aramaic, or Greek) text for that verse are also in separate boxes in a field to the right of the English word list. There is a space under each of the source word boxes outlined with a dotted line.
To align the English text:
When the English word is over a word box of the OrigL, the dotted outline will turn blue to let you know that the word will drop there. If you make a mistake, or if you decide that the English word belongs somewhere else, simply drag it again to where it belongs. English words can also be dragged back to the list.
When the same English 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 English word to the correct original word in the correct order. When aligning, check to ensure that these numbered words are in their proper places, since it is easy to miss the numbers and align repeated words incorrectly.
translationCore supports one-to-one, one-to-many, many-to-one, and many-to-many alignments. That means that one or more English words can be aligned to one or more OrigL words, as necessary to get the most accurate alignment of the meaning conveyed by the two languages.
Because English has different requirements for sentence structure and the amount of explicit information that must be provided, there is often not a one-to-one correspondence between an OrigL word and an English word. In these cases, the English words that are provided should be aligned with the OrigL word that implies them.
When aligning an English translation to the OrigL text, the precision of the alignment between the two languages is the highest priority. The most important function of the aligned text is to show the ULT user as specifically as possible from which word in the OrigL text the English meaning is derived. In practice, this means that OrigL words should be merged together ONLY when absolutely necessary for the accuracy of the alignment. Otherwise, OrigL words should not be merged together. In other words, the aligning should be done so that the smallest number of English words are aligned to the smallest number of OrigL words that accurately represent their shared meaning.
For English, we follow these principles, but other GL’s may need a different list to support full alignment.
Other alignment issues pertinent to Biblical Hebrew include the following:
You should expect that sometimes you must align words/phrases in English with words in the OrigL that differ in the number of words, order of words, and/or parts of speech (as described above). However, you should ALWAYS align the English words to the OrigL 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 English text that are left over and seem to be extra. If those words are truly necessary for the English text to make sense, then find the OrigL word(s) that they help to express and align them there. But if those words do not express a meaning found in the OrigL text, then it may be that those words should be deleted from the English translation.
Sometimes, in the process of aligning a verse, you will find:
For the above cases: if you are an authorized editor, you will want to edit the English translation so that it is more accurate to the OrigL. Otherwise, contact the Englishg translation team to let them know about the issue.
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 so we can address it in the next release. In the meantime, align the text as well as possible.
In the process of alignment according to the instructions above, you may find that the English text has words or phrases that do not represent any meaning in the OrigL text and are not there because the English sentence needs them to make sense. If this occurs, follow these recommendations:
Biblical Humanities Dashboard <http://biblicalhumanities.org/dashboard/>for other manuscripts).