Making a feature for translating the Bible
Can you please make a feature that will be helpful for doing Bible translation from original languages, please. It is very hard to pick a right document for doing this, and I think this would be very helpful!
What are others doing regarding this?
Comments
-
One option is a Personal Book Bible.
Logos Wiki Personal Books has See also User Contributed Personal Books
- American Standard Version (ASV) 1901 (Without Chapter and Verse Numbers, Red Letter) with updated New Testament
Logos.com offers four Reina Valera Bibles, including Reina Valera 1909
Also 1901 American Standard Version (ASV) from Logos.com now has ASV Bible NT Reverse Interlinear & ASV Bible OT Reverse Interlinear that is included in several feature sets.
Keep Smiling [:)]
0 -
Can you please make a feature that will be helpful for doing Bible translation from original languages, please. It is very hard to pick a right document for doing this, and I think this would be very helpful!
What are others doing regarding this?
Can you explain more precisely how you want this feature to work?
0 -
This is how I have set things up for translation. I have my original language on one side with large font size so I can see all the squiggles. Then I have notes open in the top middle, this is where I will write out my translation of the text, with the note anchored to the specific reference. I have a dedicated notebook for translations. Then below the notes in the middle I have the relevant critical apparatus's (in this case UBS5 and NA28) linked to the text on the left so that they always display the right info. BDAG lexicon is also there if I want to look up the gloss/usage of a word. And then finally I have 'Cited by' on the far right, again linked to the text. This is set to show anytime the passage is cited within my favorite Greek grammars that I have tagged as such.
.png)
Current MDiv student at Trinity Theological College - Perth, Western Australia
0 -
Interesting thought. But, I don't see how can I build a book in Logos. I would have to first make it in Word and then insert it into Logos, but then it defeats the purpose? Or am I misunderstanding something?
0 -
I envision it could be done in different ways... from the easiest to a bit more complicated.
For example, the easiest would be something like a dedicated Bible translation document that you could build, that would be fairly easy to navigate and have a capability to translate the Bible under Bible verses, insert translation comments and/or even commentary.
It could contain all the numbering and spaces for all Bible verses, linked to the original Hebrew and Greek text, so that it would know what passage you are translating (like it does when you are researching things already), and you would fill the spaces with your own translation, comments (alternative translation) and commentary.
Another way to do this would be to make a three tier interlinear, which would first offer you with a purely lexical translation that you can change and modify (for example, you can insert a different word or even language) and also in the third line you would have the ability to make a readable translation that you could later export into a document on its own.
For example, something like this:
16 Οὕτως γὰρ ἠγάπησεν ὁ θεὸς τὸν κόσμον, ὥστε τὸν υἱὸν τὸν μονογενῆ ἔδωκεν,
16 thusly for loved God the world, so that the Son the only born he gave
16 Because God loved the world in such a way that he gave his only begotten Son
Hope this helps.
0 -
For example, the easiest would be something like a dedicated Bible translation document that you could build, that would be fairly easy to navigate and have a capability to translate the Bible under Bible verses, insert translation comments and/or even commentary.
Notes anchored to Bible Verses can appear in books having Bible milestones: e.g. Bibles (includes Personal Book Bible) & Bible Commentary.
It could contain all the numbering and spaces for all Bible verses, linked to the original Hebrew and Greek text, ...
Personal Book Bible lacks reverse interlinear capability.
A readable translation with reverse interlinear (linking to Hebrew, Aramaic, & Greek) to consider is the Lexham English Bible (LEB) whose footnotes offer idiom insights:
Lexham English Bible (LEB)">
Preface
With approximately one hundred different English translations of the Bible already published, the reader may well wonder why yet another English version has been produced. Those actually engaged in the work of translating the Bible might answer that the quest for increased accuracy, the incorporation of new scholarly discoveries in the fields of semantics, lexicography, linguistics, new archaeological discoveries, and the continuing evolution of the English language all contribute to the need for producing new translations. But in the case of the Lexham English Bible (LEB), the answer to this question is much simpler; in fact, it is merely twofold.
First, the LEB achieves an unparalleled level of transparency with the original language text because the LEB had as its starting point the Lexham Hebrew–English Interlinear Bible and the Lexham Greek–English Interlinear New Testament. It was produced with the specific purpose of being used alongside the original language text of the Bible. Existing translations, however excellent they may be in terms of English style and idiom, are frequently so far removed from the original language texts of Scripture that straightforward comparison is difficult for the average user. Of course distance between the original language text and the English translation is not a criticism of any modern English translation. To a large extent this distance is the result of the philosophy of translation chosen for a particular English version, and it is almost always the result of an attempt to convey the meaning of the original in a clearer and more easily understandable way to the contemporary reader. However, there are many readers, particularly those who have studied some biblical Hebrew, Aramaic, or Greek, who desire a translation that facilitates straightforward and easy comparisons between the translation and the original language text. The ability to make such comparisons easily in software formats like Logos Bible Software makes the need for an English translation specifically designed for such comparison even more acute.
Second, the LEB is designed from the beginning to make extensive use of the most up-to-date lexical reference works available. For the Old Testament this is primarily The Hebrew and Aramaic Lexicon of the Old Testament (HALOT), and for New Testament this is primarily the third edition of Walter Bauer’s A Greek–English Lexicon of the New Testament and Other Early Christian Literature (BDAG). Users can be assured that the LEB as a translation is based on the best scholarly research available. The Hebrew text on which the LEB Old Testament is based is that of Biblia Hebraica Stuttgartensia. The Greek text on which the LEB New Testament is based is that of The Greek New Testament: SBL Edition (SBLGNT), a new edition produced by Michael W. Holmes in conjunction with the Society of Biblical Literature and Logos Bible Software. In its evaluation of textual variation, the SBLGNT uses modern text-critical methodology along with guidance from the most recently available articles, monographs, and technical commentaries to establish the text of the Greek New Testament.
Naturally, when these two factors are taken into consideration, it should not be surprising that the character of the LEB as a translation is fairly literal. This is a necessary by-product of the desire to have the English translation correspond transparently to the original language text. Nevertheless, a serious attempt has been made within these constraints to produce a clear and readable English translation instead of a woodenly literal one.
There are three areas in particular that need to be addressed to make a translation like the LEB more accessible to readers today, while at the same time maintaining easy comparison with the original language text. First, differences in word order have to be addressed. In this regard, the LEB follows standard English word order, not the word order of biblical Hebrew, Aramaic, or Koiné Greek. Anyone who needs to see the word order of the original languages can readily consult the Lexham Hebrew–English Interlinear Bible or the Lexham Greek–English Interlinear New Testament, which contain a sequence line which gives this information. Second, some expressions in biblical languages are idiomatic, so that a literal translation would be meaningless or would miscommunicate the true meaning. The LEB uses ⌊lower corner⌋ brackets to indicate such expressions, with a literal rendering given in a note. Third, words which have no equivalent in the original language text must sometimes be supplied in the English translation. Because the LEB is designed to be used alongside the original language texts of Scripture, these supplied words are indicated with italics. In some cases the need for such supplied words is obvious, but in other cases where it is less clear a note has been included.
Finally, the reader should remember that any Bible translation, to be useful to the person using it, must actually be read. We encourage every user of the LEB, whether reading it alongside the original languages text or not, to remember that once we understand the meaning of a biblical text we are responsible to apply it first in our own lives, and then to share it with those around us.
The Editors
W. Hall Harris III et al., eds., The Lexham English Bible (Bellingham, WA: Lexham Press, 2012).
Translation process is the intersection of source language range of meaning & target language range of meaning within the bounds of human translator beliefs. When source & target languages have different primary verbal focus, then what does NOT translate well is source language verbal expression. English verbs have primary focus of time: past, present, OR future. Hebrew & Aramaic verbs express kind of action: happening, volitional, completed,... (with no sense of time). Greek verbs primarily express kind of action with secondary aspect of time. Four of the seven Koine Greek verbal tenses can have a secondary time aspect. Caveat: when translating Hebrew & Aramaic verbs into Greek (& English), any time aspect is a human belief interpretation (could reflect contextual words).
The Bible Software Users Companion Pack (2 vols.) provides Hebrew & Greek exegetical insights.
Keep Smiling [:)]
0 -
For example, the easiest would be something like a dedicated Bible translation document that you could build, that would be fairly easy to navigate and have a capability to translate the Bible under Bible verses, insert translation comments and/or even commentary.
It could contain all the numbering and spaces for all Bible verses, linked to the original Hebrew and Greek text, so that it would know what passage you are translating (like it does when you are researching things already), and you would fill the spaces with your own translation, comments (alternative translation) and commentary.
Another way to do this would be to make a three tier interlinear, which would first offer you with a purely lexical translation that you can change and modify (for example, you can insert a different word or even language) and also in the third line you would have the ability to make a readable translation that you could later export into a document on its own.
It's an interesting idea. You can accomplish much of this with a single note file, and simply create chapters and verses accordingly. But you probably want it to also be closely tied in with Logos as a Bible resource as you go, and that's where I think it becomes unrealistic. I don't think tags are assigned purely by algorithm, but require a lot of human interaction. And a very, very small number of users would actually utilitize such a feature.
0 -
Interesting thought. But, I don't see how can I build a book in Logos. I would have to first make it in Word and then insert it into Logos, but then it defeats the purpose? Or am I misunderstanding something?
I have my own Bible software, which is my primary; Logos adds research capability. But my software offers a simple feature that comes close to what you're discussing (and yours is a better idea). I select a translation I like, as a base translation. And then allow literally editing it, with the edits attached directly to notes (which are more flexible than the Logos ones). I normally put anything I change in brackets just as a reminder of who's who.
I don't get too wrapped up in interlinears; they're handy. But the readable flow is more important (both english and OL). My software automatically outputs to tagged Word docs; Logos compiles them with a single click. And they're in my layouts.
0 -
LEB is a nice solution only if you are looking for an English translation. Not sure that Miroslav is interested in yet another English one.
0
