 |
Greek Interlinear Bible
stefankmitphBooks & Reference
- First is the Greek Interlinear New Testament. If you have ever had an interlinear New Testament like I have, you will appreciate the things you can do with this one in the setup. You will probably turn on all the functions for a while, just to decide which to keep and which to turn back off. I did that and now I use all 6 options when I read it.
- The Show Strongs Concordance which shows the concordance translation of the word.
- The Strongs reference/numbers to the word where tapping it shows the entry, and the other 4, which are:
- Show Transliteration,
- Show Functional Items, and
- Keep Screen On. There is a final item on the settings menu,
- Text Size. There is no on and off option for text size.
You will probably never ever turn off the underlined option. That is the row of words in red that are in English. all the other rows are in Greek or the Greek transliteration Maybe after more time I will discontinue the Strongs reference numbers row. The only time they help is when you select one of them specifically and read what pops up. For now I like seeing what other words have been used in other places as English choices to the word showing up under the Greek on the permanent red line. Maybe I will discontinue the Show Functional Items which is grammar, nouns, verbs, cases, tenses and the rest of the language categories, adverbs, adjectives, pronouns, prepositions and all the rest.
I was reading the comments that users of the Greek app shared on Google Play store, like these two:
Canuk Hed
September 1, 2016
With the Nestle translation, John 1:1 is theologically backwards John wrote that the Word was God but in Nestle's translation it states "God was the Word". This statement says that God was Jesus Christ, instead of Jesus Christ was the God of creation. Jesus was the Word by which creation came to exist and was in the Garden as the Word walking with Adam, was The Angel of the Lord talking to the old prophets, and is God incarnate as fully God and fully man. God and the Word are One, but theologically stating that God was the Word in this verse is backwards.
Randy Dueck
February 8, 2018
Great app. Could have more user friendly navigation though. To the comment about John 1:1 being backward, you should know that an interlinear Bible is not meant to read as an actual rendered English translation. It shows the English words or phrases directly above the Greek as it was written. Greek often renders thoughts in a different order than English. That is just a function of the grammatical construction of the language. When rendered, you will find this Greek text is usually translated as "the Word was God", as it should be.
I decided to try the mobile app which I am suggesting you download and I found it is a literal interlinear, not a reverse interlinear. You will either need to study each sentence in a reverse interlinear also, or you will need to learn Greek grammar structure before proposing to translate a sentence from what you are seeing in a literal interlinear. Here is the RSV reverse interlinear with all the rows turned on for John 1:1 from Logos Bible Software for laptop computers or towers so that you wind up with columns of things under each word. The publisher of the reverse interlinear RSV has a word by word highlighting system which shows where the literal Greek text was originally and where it was moved to so that it could be called reverse interlinear. When you click on the four words in the highlighting below, the Word was God, the Greek order is θεὸς ἦν ὁ λόγος and you see the jumping around as you click each English word and its corresponding Greek word. Notice the flip from "the Word was God" to "God was the Word" they do it both in the screenshot jpg of the Reverse Interlinear, and the copied and pasted exhibits with footnotes number 1 and 2 below. and I have included the Nestle which is the text used by the mobile device app I am recommending here corresponding to footnote number 4.
In the reviews of the app, both Canuk and Randy had correct points to make which I highlighted. Both were using similar tools, Canuk was using a Reverse Interlinear like mine but he did not know it was a Reverse Interlinear, I do. His comments would be incorrect if you work from the screenshot section on the right and proceed directly to item by item translation, ignoring the English side on the left, because it shows the literal Greek saying what the screenshot section on the right says in forward order, except it is in reverse order which is the order on the left which is the English order. I however know Canuk was using a Reverse Interlinear which means he can't fight the order of the original words. He has to concede to Randy the interlinear Bible is not meant to read as an actual rendered English translation I admit that I am not skilled in grammar and how best to phrase it in English when working in the Nestle or the Society of Biblical Literature Edition my quote number 3 below. I had to do a screenshot of the reverse interlinear showing the literal Greek in its order,on the right and the reverse interlinear showing the English order on the left. The screenshot was required because normal selecting, right clicking on the selection and making copy and paste actions was disabled by the Logos App for PCs.
Here is the screenshot
|
John 1.1 Ἐν ἀρχῇ ἦν ὁ λόγος, καὶ ὁ λόγος ἦν πρὸς τὸν θεόν, καὶ θεὸς ἦν ὁ λόγος. [3]
Here it is in the Nestle Greek New Testament (27th ed)
John 1.1 Ἐν ἀρχῇ ἦν ὁ λόγος, καὶ ὁ λόγος ἦν πρὸς τὸν θεόν, καὶ θεὸς ἦν ὁ λόγος [4]
Next is the Hebrew Interlinear Bible
The same thing that I said about the Greek app literal interlinear line of English words applies to the Hebrew app literal line of English words. You can't just say "The literal text says ______________________" without making the changes required by the grammar and usage. Saying things in another language based on what you think it should say from reading a literal interlinear is difficult. I can provide lots of examples
Here is a review from someone on the Play Store of the Hebrew app: I'm giving you 5 stars because this is most true to the original Hebrew wording I have found. I think a lot of people are confused with translations of ancient texts when there is a modern language in use. They forget that Ancient Hebrew is not modern Hebrew. Also, no one should be changing names, as written, to appease anyone. Great job! Comments that users of the Hebrew app shared like this one are fine as far as left to right languages go, but it really needs more. The reviewer does not mention the requirement to read the sentences with words under their hebrew language line in right to left groups of words. For example one Hebrew word can replace two or even three English words sometimes, so the translation of the two or three english words is grouped and provided going left to right under that one word, but the next Hebrew word on that line is found going right to left, so the English reader has to leapfrog over the next group to reach the first English translation in that group. Once you figure the process out you will be fine.
This concludes the blog post.
[4]Nestle, E., Nestle, E., Aland, B., Aland, K., Karavidopoulos, J., Martini, C. M., & Metzger, B. M. (1993). The Greek New Testament (27th ed., Jn 1:1). Stuttgart: Deutsche Bibelgesellschaft.
This concludes the blog post.
[1]The Revised Standard Version. (1971). (Jn 1:1). Oak Harbor, WA: Logos Research Systems, Inc.
[2]Screenshot.jpgThe Revised Standard Version. (1971). (Jn 1:1). Oak Harbor, WA: Logos Research Systems, Inc.
[3]The Greek New Testament: SBL Edition (Jn 1). Lexham Press; Society of Biblical Literature Holmes, M. W. (2011-2013).
[2]Screenshot.jpgThe Revised Standard Version. (1971). (Jn 1:1). Oak Harbor, WA: Logos Research Systems, Inc.
[3]The Greek New Testament: SBL Edition (Jn 1). Lexham Press; Society of Biblical Literature Holmes, M. W. (2011-2013).
[4]Nestle, E., Nestle, E., Aland, B., Aland, K., Karavidopoulos, J., Martini, C. M., & Metzger, B. M. (1993). The Greek New Testament (27th ed., Jn 1:1). Stuttgart: Deutsche Bibelgesellschaft.
|
No comments:
Post a Comment