Recently in Using Books Category

Today's guest post is from Morris Proctor, certified and authorized trainer for Logos Bible Software. Morris has trained thousands of Logos users at his two-day Camp Logos training seminars. In this series, Morris answers the question, "What's in my library?"

English Standard VersionBible (Literal)

Definition: The Bible was originally written in the Hebrew and Greek languages. Our English Bibles are based on the Hebrew and Greek manuscripts. A literal translation of the Bible seeks as much as possible to give a word for word translation from Hebrew or Greek to English. Literal translations of the Bible should be used when conducting more serious Bible study.

Example: English Standard Version

Application: If you are not familiar with original languages, but want to do serious Bible study getting as close as possible to the original meaning of the text with an English Bible, then you want to rely on literal translations like the ESV, KJV, NKJV, or NASB.

For more tips like this, be sure to visit Morris Proctor’s mpSeminars website and his Tips & Tricks blog.

You should follow us on Twitter here.

Today's guest post is from Morris Proctor, certified and authorized trainer for Logos Bible Software. Morris has trained thousands of Logos users at his two-day Camp Logos training seminars. In this series, Morris answers the question, "What's in my library?"

So That's Why BibleBible (Chronological)

Definition: The contents of the Bible are not recorded for us like a story from start to finish in chronological order. A chronological Bible rearranges the events in Scripture placing them in the order they actually occurred in time.

Example: So That's Why Bible

Application: Imagine doing a study on the life of Jesus from the four gospel accounts. You have to read a little in Matthew then jump to John then back to Luke and so on to read then events as they actually occurred. A chronological Bible places theses events on the page as they actually occurred so you can read about the life of Jesus from start to finish.

For more tips like this, be sure to visit Morris Proctor’s mpSeminars website and his Tips & Tricks blog.

You should follow us on Twitter here.

Today's guest post is from Morris Proctor, certified and authorized trainer for Logos Bible Software. Morris has trained thousands of Logos users at his two-day Camp Logos training seminars. In this series, Morris answers the question, "What's in my library?"

Logos Deluxe Map SetAtlas (Bible)

Definition: A Bible atlas contains maps pertaining to the events that occurred in the Bible. A Bible atlas would include maps about the placement of the twelve tribes of Israel or the travels of Paul.

Example: Logos Deluxe Map Set

Application: As you read in John 4 about Jesus having to go through Samaria, an atlas will help explain the significance of the passage.

For more tips like this, be sure to visit Morris Proctor’s mpSeminars website and his Tips & Tricks blog.

You should follow us on Twitter here.

Today's guest post is from Morris Proctor, certified and authorized trainer for Logos Bible Software. Morris has trained thousands of Logos users at his two-day Camp Logos training seminars. In this series, Morris answers the question, "What's in my library?"

Archaeology (Biblical)

Definition: A biblical archaeology book details archaeological discoveries that are pertinent to biblical history or Christianity. This book is normally arranged topically according to specific locations such as Jericho or the Dead Sea.

Example: Archaeological Encyclopedia of the Holy Land

Application: While you are reading about Jericho in Joshua 7 or Ephesus in Acts 18, if you wonder about discoveries recently made in these areas, then an archaeology book is where to go.

For more tips like this, be sure to visit Morris Proctor’s mpSeminars website and his Tips & Tricks blog.

You should follow us on Twitter here.

Today's guest post is from Morris Proctor, certified and authorized trainer for Logos Bible Software. Morris has trained thousands of Logos users at his two-day Camp Logos training seminars. In this series, Morris answers the question, "What's in my library?"

Apologetics

Definition: Apologetics is the area of theology which seeks to defend and support the claims of Christianity. An apologetics book then contains these defenses of The Faith. This book would answer questions such as “Is the Bible reliable?” or “Did Jesus rise from the grave?” Some apologetics books are arranged topically according to subject matter while others are more of free-flowing narrative.

Example: Handbook of Christian Apologetics

Application: If someone were to ask you: “How can you be sure Jesus rose from the dead?” What proof can you give me the Bible is trustworthy?” Then turn to an apologetics book for answers.

For more tips like this, be sure to visit Morris Proctor’s mpSeminars website and his Tips & Tricks blog.

You should follow us on Twitter here.

Today's guest post is from Morris Proctor, certified and authorized trainer for Logos Bible Software. Morris has trained thousands of Logos users at his two-day Camp Logos training seminars. In this series, Morris answers the question, "What's in my library?"

Analytical Lexicon

Definition: In addition to providing definitions for Hebrew or Greek words, an analytical lexicon examines the various forms of words used in the original texts. In other words, it not only provides definitions for the lemmas (root words), it also offers information about the inflected or manuscript forms of the Hebrew or Greek words used in the Bible. The analytical lexicon is arranged alphabetically according to the Hebrew or Greek words.

Example: Analytical Lexicon of the Greek NT

Application: Imagine coming to the word “logos” in your study of John 1:1. You notice the word is used as a subject of a sentence but you’re curious if the word is ever used in a different case as a direct object. An analytical lexicon will get you well on your way to discovering the answer.

For more tips like this, be sure to visit Morris Proctor’s mpSeminars website and his Tips & Tricks blog.

You should follow us on Twitter here.

Many pastors and Bible students who have grown up using Strong’s numbering system for Hebrew and Greek are slow to switch to something unfamiliar like reverse interlinears. We believe that reverse interlinears are a far better technology and superior to the Strong’s system, but we understand that not everyone is ready to completely abandon Strong’s just yet. That’s why we’ve tried to retain our Strong’s functionality as new versions have come out.

James Strong is best known for his Exhaustive Concordance of the Bible in which every Hebrew and Greek word was given a number, all of the references where each word occurred were listed, and brief definitions were given for each word. Strong’s numbering system made it easy for people who couldn’t read Hebrew or Greek to look up words.

Last month we got a call from a customer who has been wanting to upgrade from version 2 of our software to version 3 for a couple of years now. The only thing holding him back was that he thought he’d lose his Strong’s Concordance. After we explained to him that all of his favorite Strong’s resources and reports would still work in version 3, he was overjoyed and quickly upgraded. This post is for anyone out there who might be in the same boat.

Resources and Reports

Sometimes there can be confusion regarding what is a resource or book that can be found in My Library and what is a report or part of the software’s functionality. So let’s start by setting the record straight.

Resources

There are several Strong’s lexicons or dictionaries:

Other lexicons like the Dictionaries of Biblical Languages w/ Semantic Domains include Strong’s numbers and will work as well.

There are a few Bibles with built-in Strong’s numbering both inline and interlinear.

The ESV and NRSV NT reverse interlinears also have Strong’s numbers.

Reports

Version 2 had an Englishman’s Concordance report that produced results like you’d find in Strong’s Concordance. Version 3 has a similar report under a different name.

  • Version 2: Englishman’s Concordance
  • Version 3: Search Analysis by Strong’s

Clarification: You can actually still run the Englishman’s Concordance report in version 3. See Where’d My Strong’s Concordance Go? Part 2 for the details.

Finding the Strong’s Report in Version 3

So where do you find Strong’s Concordance in version 3? If you’re looking for Strong’s Concordance in My Library, you won’t find it because it’s not a book or resource. It’s a report. Concordances (as resources) don’t make a lot of sense in Bible software because you can generate a concordance on any word or phrase by simply running a search.

To get the Strong’s Concordance report in version 2, you’d use the Englishman’s Concordance. The same basic content is still available in version 3. Here’s one way you access it:

1. Do a Bible Speed Search or a regular Bible Search using the KJV or the NASB (or another Bible with Strong’s numbering) on a word like marriage.

2. In the search results window, click “Search Analysis by Strong’s” in the top right hand column at the bottom of “Other Tools.” You’ll see this report.

This will show you all of the underlying Hebrew or Greek words for the English word you searched on. You can arrange the results by root word or by reference. You can also do the reverse of this. See the follow-up post for details.

For more on Strong’s, see:

For more on reverse interlinears, see:

See Where’d My Strong’s Concordance Go? Part 2 for more on using Strong’s in Logos Bible Software 3.

The recently-released Lexham Greek-English New Testament Interlinear has, as one of its primary distinguishing features, domain-article references to the Louw-Nida Greek Lexicon (info here, here and here). That's all well and good, but -- beyond keylinking to a specific Louw-Nida article -- what can we do with the references?

One thing that you can do (shown in the below-referenced video) is begin to explore using the concept of "semantic chaining" (also known as "semantic chunks" or "semantic clustering"). The idea is to explore how a section of text (a pericope or chapter or book) uses or repeats ideas found in particular domains or domain-subdomain references.

OK, I'll speak in English this time. You know how repeated words can be important when you're looking at a passage? Well, Louw-Nida references let you expand that notion to repeated concepts. The theoretical backgound for this concept is well-established in the literature* but as of yet has not really been available in a consumer-level Bible study product.

But you can do it with the Lexham Greek-English Interlinear New Testament if you've also got the Louw-Nida lexicon (Greek-English Lexicon of the New Testament Based on Semantic Domains) and are willing to learn how to reference search using the Bible Speed Search dialog.

The video shows you how. Our sample passage is 1Ti 2.1, and our sample concept is prayer.


* Some references include:


  • Reed, Jeffrey T. A Discourse Analysis of Philippians, pp. 296-331. This book will be available in the Studies in New Testament Greek and JSNTS Collection.

  • Porter, Stanley E. and O'Donnell, Matthew Brook. "Semantics and Patterns of Argumentation in Romans: Definitions, Proposals, Data and Experiments", pp. 154-204 in Stanley E. Porter (ed.), Diglossia and Other Topics in New Testament Linguistics. This book will be available in the Studies in New Testament Greek and JSNTS Collection.

  • Guthrie, George, The Structure of Hebrews: A Text-Linguistic Analysis.

  • Van Neste, Ray, Cohesion and Structure in the Pastoral Epistles. This book is available in the Library of NT Studies: JSNTS on Paul collection.

[Today's Guest Post is by Dr. Steve Runge, who is a scholar-in-residence here at Logos Bible Software. Steve is working on projects to annotate discourse function in the Greek New Testament and Hebrew Bible. More importantly, he's a really smart guy with a passion for explaining the exegetical significance and importance of discourse functions in language that non-academics can understand — so that sermons and lessons can take such things into account, resulting in better preaching and teaching. Look for more posts from Steve in the future. — RB]

My name is Steve, and I wanted to give you some ideas about how you can use some technology you probably already have to enhance your Bible study. One of the great features of the Biblical Languages Addin is the Morphological Filter (click View | Visual Filters) that lets you markup Greek and Hebrew Bibles based on their morphological coding (Click for video demo; here's a blog post with similar information). And you are probably saying, “Steve, I don’t know Greek. Why would I want such a tool?” I am glad you asked!

One of the basic tenets of Bible study is to identify the main idea of each verse, which in turn allows you to build toward understanding the big idea of a passage, and so on. Believe it or not, the New Testament writers wanted the same thing. Not every action is of equal importance, and so the writers made choices about which actions to make the main idea of a sentence. One of the ways they did this was by using different kinds of verbs for different kinds of actions in order to prioritize them.

If you were to picture a line of soldiers, there are two ways I could make some of them stand out. The first way is to have the important ones take a step forward. This is essentially what emphasis does, it brings something out front. The other way to make something stand out is to have the less-important ones take a step back. By pushing the less-important things into the background (‘backgrounding’ them), I can focus your attention on the ones that are left in their original position. This is exactly what the writers did through the use of participles. Wait, it’s okay, don’t be afraid! Grammar can be a great friend and ally! Let me show you how.

Every sentence in the New Testament required the writer to make decisions. We make them all the time without even thinking about it, whether writing or speaking. We choose wording that fits best with what we want to communicate. The same is true of the NT writers. If they wanted something to be viewed as a main action, they used a main verb form (technically ‘finite’ verbs like the indicative, subjunctive or imperative moods for fellow grammar geeks). If they wanted to describe some action to set that stage for the main action, the writers would use participles before the main action to push the less important action into the background. Here is a quick example from English.

  1. I was writing a blog post this morning. I spilled my coffee on my keyboard.
  2. While writing a blog post this morning, I spilled my coffee on my keyboard.

In the first line, both actions are described as though they were equally important, both use main verbs. The second line backgrounds the first action using a participle in order to set the stage for the main action that follows—spilling my coffee (Don’t worry, Bob. I didn’t really spill, just needed an example).

This same kind of backgrounding happens all the time in the New Testament. And even if you don’t know Greek, you can use the tools available in Logos to find these backgrounded actions. Here’s how.

If you have an ESV English-Greek Reverse Interlinear of the New Testament and the Morphological Filter from the Biblical Languages Addin, you have all that you need to start your study. Open up the ESV English-Greek Reverse Interlinear in Logos Bible Software, and then click View | Visual Filters. This opens up the Visual Filter dialogue. Then click on Morphological Filter in the left pane, then click Add.


Click image for larger version
(works for all images in this post)

Then click Details. This opens up another dialog box that lets you choose the grammatical characteristics that you want to visualize. We want to check Verbs, and then Participles under Verb types. Then click Add on the lower left, and finally pick a how you want to represent it in the text using the Palettes (I chose the Gray highlighter pen). This will identify all of the participles.

Now you need to identify the main verbs. All we have to do is repeat the steps. Click Verbs, and then under the ‘Tense, Voice, Mood’ menu click Finite under ‘Verb types’, then click Add.

Now pick a visualization from the Palettes (I chose green highlighter pen), and finally click Okay. You are ready to look for backgrounded actions!

In your ESV reverse interlinear, go to Matthew 28:19, we can take a look at how Matthew uses a participle to prioritize the actions of the Great Commission. English does not use participles like Greek does, so a lot of them get translated into English as though they were main verbs. This is not incorrect translation, it is just a consequence of Greek not being English. But you can pick out the backgrounded actions from the original Greek using this Visual Filter in the Reverse Interlinear.

In English, there are two main actions of the Great Commission: Go and Make disciples. But if you look at ‘Go’, you’ll see that it is a participle. Does this mean it doesn’t matter at all? No, it does matter. Matthew used a participle to make sure that we got the main idea of the verse: MAKING DISCIPLES. Both actions need to happen, but they are not of equal importance. Using a participle backgrounds the less-important action.

This idea of backgrounding only applies to participles when they precede the main action, not when they follow it. The participles that follow the main action tend to spell out more specifically what the main action looks like. Here, ‘making disciples’ is spelled out as ‘baptizing’ and ‘teaching them to observe all that Jesus commanded’.

Another good example is found in Acts 9:1-2, where Saul is seeking to arrest the believers in order to keep ‘The Way’ from spreading.

In v. 1 there are two actions described: ‘breathing’ and ‘went’. But we can tell from the Morphological Filter that both of these actions are backgrounded. That means that these actions are setting the stage for the main action, and are not the main action themselves. The main action doesn’t come until v. 2; it is Saul ASKING for the letters. ‘Going’ to the high priest was just something that had to happen before he could ‘ask’ them for the letters. Luke’s choice to use a participle reflects how he chose to prioritize the action. Understanding how he prioritized the action will help us better understand the main point of the passage. The other participles in v. 2 function as ‘verbal adjectives’, describing whom Saul is seeking (the ones ‘belonging to the Way’) and how he will bring them (‘having been bound’). The principle of backgrounding only applies to the action participles that precede the main action.

The biggest, hairiest chain of backgrounded actions that I have yet found is in Mark 5:25-27, where SEVEN backgrounded actions before we finally get to the main action. Nearly all of these are translated in the ESV as though they are main verbs. Remember, this is not bad translation, it just reflects that Greek is not English. Take a look!

Look at all of the actions that are backgrounded! The one main action that is left standing is ‘touched’, all of the rest are simply setting the stage for this action. Mark clearly indicates this by using participles instead of main verbs. He could have just as easily chosen to make ALL of the actions main ones, but then ‘touched’ would not have stood out. They would have all been equal. By backgrounding the less-important actions before the main action, the writer lets us know which action we need to focus on. There is good reason to focus on ‘touch’ in this context, because it is the key action that sets off a whole series of events that follows. Touching Jesus is what heals this woman (v. 27). Look at how Jesus’ response is described in v. 30.

Three participles are used to describe the actions that lead to Jesus’ response (‘said’), and what he says is the most important part of the verse: ‘Who touched me?’ Mark has carefully framed his message to make sure that we do not miss the main point of the story!

The gospels and Acts by far make the most use of backgrounding through the use of participles before the main action. Here are a few more examples from Matthew. In Matt 13:46 in the parable about the pearl of great price, look at which actions have been backgrounded.

There are only two main actions in this verse: ‘selling all that he had’ and ‘buying’. The ‘finding’ and ‘going’ set the stage for the main actions. Do you see how the backgrounding fits with the main idea of the passage?

Another example is found in the description of Jesus preparing to feed the 5000 in Matt 14:19.

There are three backgrounded actions leading up to one main action in the first sentence. ‘Ordering the crowds’, ‘taking’ the loaves and fish, and ‘looking up to heaven’ are all backgrounded, keeping attention on the main action: he said a blessing. In the next sentence, ‘breaking’ is backgrounded, keeping attention focused on ‘giving’ it to the disciples who in turn give it to the crowds.

By the way, you do not need to use the visual filter to find out if an action is a participle in Greek or not. If you hover over ‘ordered’ in v. 19 of the reverse interlinear and look at the display in the lower left corner of the main window, you will see some information displayed.

The G2753 is the Strong’s number; the rest is the grammatical information for the Greek word. You can get the same information as what we have visualized using the Visual Filter, but it is does not let you see the big picture, and it is not nearly as cool!

As you may have noticed, not every participle backgrounds an action. Some participles don’t even describe action, but instead function as verbal adjectives to describe a person, place or thing. The participles that follow the main action usually spell out more specifically what the main action looks like (a topic I will take up in a future post). But there is hope!

I have been working for the last year in a super-secret department (next to Rick!) on a project that identifies all of the New Testament occurrences of cool devices like backgrounded actions. There are 15 other devices that are all explained and marked up using something like the visual filter right in the text to help you better understand what the writers were trying to draw your attention to. Stay tuned for more details.

Update: Both products are now available for pre-order:

The Louw-Nida Greek Lexicon (formal title: Greek-English Lexicon of the New Testament Based on Semantic Domains, though henceforth "LN") is a unique and helpful lexicon. It is, however, put together differently than most Greek lexicons.

[OK, this got a little long. If you're more of an I-have-to-see-it-to-understand-it sort of person, cut to the chase and check out the video.— RB]

Instead of being ordered by the Greek alphabet (for easy headword lookup) with one article per headword, the lexicon is ordered by the concept of semantic domain. Even more confusingly, words with multiple major senses have multiple entries. For example, ανθρωπος could be "human being", or more specifically "man", or even more specifically, "husband". In this case, LN has at least three definitions in three different places in the lexicon.

The lexicon has a separate index, ordered by headword, that helps one to navigate the articles and actually use the lexicon. We've had LN (volumes 1 & 2) available in Logos Bible Software for years; it is included in many of our packages (specifically, Original Languages, Scholar's, Scholar's Silver and Scholar's Gold).

So to use LN, you've had to go into the index, pick the likeliest sense from the index list, then go to that entry and see if it is proper.

With the new enhancements we've made to LN, when you keylink in from a Greek New Testament (or a New Testament Reverse Interlinear), you'll go directly to the article representing the sense being used in your current instance instead of the catch-all index entry. How's that for cool? (and time-saving!)

If you still want to go to the index entry in volume 2 after having read the sense-specific article, you can still get there — check the video for the groovy keylink-on-the-lexicon-headword trick I use to do this quickly. (Note that the method is more fully documented here).

Confused? That's OK. I made a video; you can hear me blathering on for almost nine minutes on this book, how it is ordered, how it is used and the significant enhancements we've made to it to support keylinking into this lexicon from the Greek New Testament (or New Testament Reverse Interlinears!) Apologies for the last minute; I sort of ramble on for a bit.

This updated version is available on our FTP site (ftp://ftp.logos.com/lbxbooks, look for LOUWNIDA.lbxlls). You also can download the latest version of LN from the book's page on our web site if you'd like to try this yourself.

Back in December, we put The Lexham Greek-English Interlinear New Testament on Pre-Pub.

Since the early reception to the Pre-Pub was good, we've been doing a little work on the New Testament interlinear and even have some provisional data back from the editor, Hall Harris. So I thought I'd take some time to walk you through some of the features in the hopes that even more of you will pre-order it!

My friend and colleague Johnny recently came up with some pretty cool tricks for using BDAG to help when reading the Apostolic Fathers in Greek.

The trick is pretty simple, but is involved to explain. So I made a video.

Think about other applications of this same technique:

  • Maybe you're interested in where BDAG has cited a particular section of BDF? You could use this same trick. As an example, BDF §260 has to do with how the article is used with personal names. Want to know where BDAG cites or points to this section? Search BDAG for "bdf in 260".
  • Maybe you want to see where BDF has referenced Ignatius to Polycarp. You can do the same search the video demonstrates, only do it in BDF: "af in ipol".
  • You get the gist. I'm sure you can think of others.

How cool is that?

Guest blogger Mark Van Dyke (when does he get promoted to a regular?) writes about typo reporting in Logos Bible Software.

Dr. Daniel Wallace's lecture about preserving the Word of God was a good reminder about the importance of textual accuracy. Just like the ancient manuscripts that are studied in Middle Eastern monasteries, Logos book files have an occasional misspelled word. That's why Libronix has a nice little feature for reporting typographical errors and grammatical glitches. It only takes a moment but helps us out immensely!

You can report a typo by following these three simple steps.

Step One

Highlight the error.

Step Two

On the top task bar select Help | Report Typo.

Step Three

Fill out the form with the typo correction and your email address. Then click "Submit".

Please note that if you are reporting an error with Logos' syntax database you might need to send an email to syntax@logos.com rather than using the internal 'Report Typo' dialog.

When you let us know that there is a misspelled word in one of our book files, that word is put on a list so the next time we update that book file we can fix the problem. This means that the typos aren't always fixed the next day after you tell us, but your message will definitely be read and acted upon.

As always, we love getting feedback. Even in the case where we need to change something about a book. That's because the textual accuracy of every book we create is of the utmost importance – whether it's the Bible itself or the Scripture Alphabet of Animals.

Thanks for helping!

This is the second post in a series of posts (first post here) having to do with the Apostolic Fathers in Greek and English. Today's video focuses on basic capability of the morphologically annotated Greek texts, including configuring the interlinear lines, keylinking and using visual filters.

In the third and final installment next week, I'll show how to configure linking and hovering preferences related to the Apostolic Fathers and dig into the Bible Word Study report.

Note: The video discusses two items that do not ship with Apostolic Fathers but can be added to your digital library: morphological filter (part of Biblical Languages Addin, which is included in "language" base packages) and theBDAG lexicon.

The long-awaited Apostolic Fathers in Greek and English has shipped! This includes three editions of the writings of the Apostolic Fathers (each edition has both Greek and English text, so six resources in all). More info, of course, is on the product page.

I thought I'd take a few posts and show some of the things you can do with these resources. Today's video has to do with general use of the resources with some ideas of further things you can do to get more from the books as you read them. Today I'll focus on the English, though I'll focus on the Greek editions in future posts.

Future posts will likely include things like keylink preferences, hovering and highlighting and also integration with the Bible Word Study report.

Last Thursday's post explained how to view all the papyri from Comfort & Barrett's Text of the Earliest New Testament Greek Manuscripts that contain the verse or passage you're studying. We set up the Compare Parallel Bible Versions report to scroll synchronously with Exegetical Guide (or any Bible or other canonically-organized resource or report for that matter) to make it easy to consult the papyri as you study.

Today I want to briefly offer an alternative way to view the manuscripts related to your passage and that is the Passage in All Versions report.

Passage in All Versions does not visually highlight the differences between the manuscripts but it does retain formatting such as brackets and uncertainty dots. 

Here's how to set up the report to show the papyri:

  • Click Tools | Bible Comparison | Passage in All Versions.
  • In the report window, click the Properties button.
  • Set language to Greek and check the boxes next to the Greek texts and manuscripts you want to appear in the report (or Check All and then clear the boxes next to the items you don't want).
  • Click OK.

Now you can enter a passage, click the Go arrow and see eclectic texts, received texts, and manuscripts for that passage. You can also use the "chain link" icon to link this report with other reports or resources so they move synchronously.

Compare Parallel Bible Versions and Passage In All Versions...two options for viewing manuscripts alongside the GNT text.

Update 4-16-07—a bug in the Passage In All Versions report causes some versions that you've deselected to appear in the report. Libronix DLS 3.0d (available as a beta download) fixes this bug.

In the course of working on a review of Ugaritic Library and Logos 3, blogger and pastor Dr. Jim West recently asked me whether Comfort & Barrett's Text of the Earliest New Testament Greek Manuscripts could be made to appear in the Exegetical Guide report. Since that report provides exegetical helps for a given passage of Scripture, wouldn't it be neat if it would automatically discover and link to any papyri that overlap with your passage?

I agreed that this would be grand, but since it's not currently coded into the Exegetical Guide report I wanted to find a way to do something similar.

Rick Brannan reminded me that the Compare Parallel Bible Versions report is a great way to examine and compare manuscript evidence for a given portion of Scripture (as outlined in this article).

Note: If you don't own this addin, you can use the standard Parallel Bible Versions report (sans highlighting of textual differences) or buy it here.

Now if I could only find a way to get the Compare Parallel Bibles report to stay in synch with Exegetical Guide so that they would track together as I move from verse to verse.

Wonderful news: in Logos 3 this is possible. Just set the "chain link" icon in both reports to A.

Now the two reports track together. Whenever I move Exegetical Guide to a new passage of Scripture, the Compare Parallel Bibles report updates itself to show that passage.

Just one problem, though. How do I get the Compare Parallel Bibles report to show not one but all the papyri containing the verses I'm studying? As you may know, a given biblical verse or passage can appear in any number of manuscripts and fragments. For example, John 1:30 is attested in four different papyri: P5, P66, P75, and P106!

If you open My Library and locate Text of the Earliest New Testament Greek Manuscripts you'll see that this single volume contains all the papyri from Comfort & Barrett's book and is, in fact, laid out just like the print edition of that book. It even contains a list of manuscripts in canonical order, which is how I knew that John 1:30 appears in four different manuscripts.

Because this single resource contains all the manuscripts in one place you might think you could specify it in the Compare Parallel Bible Versions report and the report would automatically show you all the manuscripts containing your desired verse. But you'd be wrong...

When you tell the report to compare NA27 and TENTGM (the all-in-one resource), the report only shows the first papyrus that matches the verse selected...in this case John 1:30 from P5. This is because the report is designed to compare Bible versions that are individual resources within the digital library...not multiple "versions" within one book. If only we could split the manuscripts up into individual resources!

Fortunately for us, the Logos book designers anticipated this need and did just that. Each manuscript appears twice in your digital library—once in the all-in-one resource (TENTGM) and once in an individual resource (e.g., TENTP30 which appears in My Library as P30 from The Text of the Earliest New Testament Greek Manuscripts).

So all we have to do is specify each papyrus (P number) individually, putting them all into the Versions box. The report is smart enough to show only manuscripts that contain data for the specified passage.

Since there are 69 different resources, it's a bit of a hassle to type in "P1, P4, P5, P6, etc." But I already endured the hassle, so I'll make it easy on you and share my workspace. Just right-click this file, choose Save Target As, and save it to My Documents\Libronix DLS\Workspaces then open it from within Libronix via File | Load Workspace.

Here's what you'll see, more or less (click the thumbnail for a larger view)...

Starting from the top left and moving clockwise: Exegetical Guide, Compare Parallel Bible Versions, NA27 Apparatus (Tischendorf apparatus on tab), SESB edition of NA27 with apparatus markers (ESV NT Reverse Interlinear on tab). Of course, if you don't own SESB or SESB for Logos Users Special Edition the apparatus and NA27 at the bottom of the workspace will show up as locked. But you can replace them with another book for your own workspace.

Now when you scroll or jump any of these four linked windows to a new verse, all the others will follow. As you can see, the Compare Parallel Bible Versions report is comparing NA27 against Scrivener's TR and all relevant papyri from Comfort & Barrett (in this case, P5, P66, P75 and P106).

Tip: You can either use this workspace "as is" or just add the Compare Parallel Bible Versions report to your Favorites and call it up whenever you want...saving you the trouble of entering all 69 papyri in the Versions box. Once the report is saved to your Favorites, you will be able to easily come back to it later or add it to another workspace.

Caveats and Links

Eli Evans saw what I was doing here and is giving some thought as to how to make this all work a little smoother in the next major version of Logos. He also offered these caveats which I will pass along to you:

Beware that most (all?) of the C&B stuff has chapter-level milestones in it, so you may get a few papyri poking in where they don't have any evidence. Try John 1:1, for example. Neither P5 nor P106 has verse 1, but they both have chapter 1, so they show up with 100% variance from the base. The report asks for "John 1:1" and the resource says, "The closest thing I have is John 1, but it doesn't have any content," to which the report replies, "Close enough, I guess." P5 starts at 1:23, and P106 at 1:29.

Furthermore, it's worth noting that where it looks like there is a significant variant, one really ought to click on the MSS title in the report and look at the resource. Things like brackets and uncertainty dots are stripped in the report, so there's a whole level of detail that isn't represented here. But this is good for finding the drill-down spots.

He's right on both counts, of course. Take a look at the screenshot below and you'll notice that brackets and dots have been stripped out for this report. Also, things like hard returns get flagged as differences (see, for example, blepei in P5 and P106). Since manuscripts may have words missing along the edges these hard returns can actually hold significance but it's always a good idea to open up the actual manuscript for further detail.

All that to say that uncritical use of this report would be unwise but with some discernment as to what it can and cannot do, it's a great way to quickly flag differences between the manuscripts and know where to dig in for further analysis.

Links

John Fallahee, king of Logos video tutorials, just produced a new video on reverse interlinear Bibles.

The video introduces the unique features of reverse interlinear Bibles and, through an extended example, shows how these features solve five common problems that plague the person who studies the Bible in translation:

  1. You can't trust your search results with English only searches.
  2. You can’t see the author’s original word choice.
  3. You can’t see different words functioning differently in the original text.
  4. Meaning can be obscured through the English translation.
  5. Strong's numbers can't reveal how the word is functioning.

Check it out: Better Bible Study Through Reverse Interlinear Bibles (14:21, 21.2MB)

In a previous post, we looked at how English translations delimit the quotation in James 4.5. Do other resources shed any light on this question?

Greek New Testaments

We can examine the formatting of Greek New Testaments much like we examined the formatting of English New Testaments. In Logos Bible Software, the relevant Greek NTs are the NA27 and UBS4 editions along with Westcott & Hort. If you have a product from Thomas Nelson, you may also have the Hodges/Farstad edition of the Majority Text, this is formatted as well.

In the above, you can see that Hodges/Farstad formats v. 6 as a quotation (complete with angle quotes). In v. 5, the relevant portion appears to be treated as a quotation of some sort; this is traditionally what an upper-cased letter after introduction would imply (ἡ Γραφὴ λέγει, Πρὸς φθόνον ἐπιποθεῖ). The upper-case gamma in Γραφὴ also implies the editors see this as referring to the Scriptures, and not to generic writings of some sort.

The NA27 uses italicised text for v. 6, which indicates an Old Testament quotation. But no special formatting or casing appears in v. 5. The UBS4 is similar, only they have no special formatting implying quotation or quotation source.

Westcott and Hort use bold text to indicate some sort of quotation or allusion (not always to the Old Testament). So v. 6 includes a quotation, but no special formatting on v. 5. (note also the placement of the question mark in WH vs. NA27/UBS, that could be significant when translating the verses).

Lexham Syntactic Greek New Testament

The Lexham SGNT marks what the editor considers to be quotations from or allusions to external source with what is called a Quotative Frame.

The Lexham SGNT Glossary defines the Quotative Frame as follows:

Quotative Frame: A frame which contains an explicit quotation, or citation, from an external source. Where allusion occurs or where, as in sections of Hebrews, the text of external sources is woven inextricably into the main text, this is annotated as if it were original on the part of the author.
Lukaszewski, A. L. (2006; 2006). The Lexham Syntactic Greek New Testament Glossary. Logos Research Systems, Inc.

Commentaries

Logos Bible Software has a wide selection of Commentaries. Commentaries focused on working through the Greek text or that are focused on interpretational difficulties will assist one in this verse. I've reviewed a few commentaries on this verse (NIGTC, Hermeneia, ICC, Word Biblical Commentary) and they don't agree any more than the translators do. But the better commentaries will explore the possibilities and explain the positives and negatives of each in some degree of detail before arriving at a conclusion. Comparing these sorts of discussions across commentaries can be enlightening and helpful in sticky situations like this one.

Conclusion

Using resources like these — in ways you may not have thought of — helps in examining the questions we've run into in James 4.5. Hopefully this series of posts has been helpful.

My primary purpose has been to show that when one runs into ambiguities in the text, there are a lot of places one can turn. The options are knowable and explorable, utilizing both textual resources (Bibles and commentaries), databases (morphology and syntactic databases) and reports (like Passage in all Versions). So next time you run into an ambiguity ... have fun digging!

I've been blogging about James 4.5-6. In the series I blogged about examining the text using English translations. Then I blogged about the underlying Greek. There are still more questions with James 4.5-6, however. In this post we'll consider the quotation from Scripture mentioned in James 4.5 and how it is represented in the English texts. Is it a quotation, or is it a summary of Scripture? Here's the text:

Or do you suppose it is to no purpose that the Scripture says, “He yearns jealously over the spirit that he has made to dwell in us”?(Jas 4:5, ESV)

Instead of writing ad nauseum about this, I've recorded a video that that compares the quotes in English translations. Examining the way that the major English translations handle this gives us an idea of the options and might even give us help in deciding which option is preferred in this case.

Earlier I blogged on using multiple English translations to see how a passage is translated differently. In passages (such as James 4.5-6) where there are ambiguities, many times comparing English translations can help in understanding the best way to deal with the ambiguity.

With James 4.5, as we saw, translations are fairly evenly split in handling this passage. Recall the issues:

  • Is it 'spirit' or 'Spirit'?
  • Is [Ss]pirit the subject or direct object of its clause?

The first point is determined largely by context and how one reads the text. This means it is important to determine whether [Ss]pirit is the subject or direct object because this may assist in determining whether it is 'spirit' or 'Spirit'. This post digs into the second point above by digging down into the underlying Greek. Of course, this is problematic for the same reason: ambiguity.

I am a contributor at another blog called PastoralEpistles.com. That blog is one outlet where I work specifically with my favorite section of the New Testament, the Pastoral Epistles (1 Timothy, 2 Timothy and Titus).

Over on PastoralEpistles.com, I'm working on a series of posts that combines a few of my loves: The writings of the Apostolic Fathers, Koine Greek, and the Pastoral Epistles. I'm using a book published in 1904 by Oxford titled The New Testament in the Apostolic Fathers (that one is actually a Community Pricing title, check it out!) that provides information on areas in the writings of the Apostolic Fathers that show affinity with areas of the New Testament. These "areas of affinity" may be outright quotes, they may be indirect citations, they may be allusions, or they may simply have topical similarity using similar language for similar topics.

I'm also able to use the shortly-to-be-released Logos Edition of the Apostolic Fathers which makes this sort of work loads easier than it was before. It's true, after long last the work on the Apostolic Fathers is done and it should be released on time — so hurry up and get the pre-pub price while you can!.

Basically, I'm working through where writings of the Apostolic Fathers are noted to have affinity with the Pastoral Epistles. I started in the Epistle of Barnabas. Here's an example of an entry from The New Testament in the Apostolic Fathers:

This short section provides the texts in question and a short (emphasis on short) discussion. But it's a starting point. Basically I'm reviewing the texts and considering the linkages. You can check out my discussion on the Ep.Barn. 1.3-6 || Titus 3.5-7; 1.2 affinities.

I'm not writing this post to discuss linkages between the writings of the Apostolic Fathers and the NT (as cool as that would be). Instead, I'm going to shift to syntax. In looking at the above linkages, one notices the Greek ἐλπίδι ζωῆς (hope of life) prominent in both the Barnabas and Titus passages.

This prompted me to ask a few questions. First, I wondered how prominent this "hope of life" (Titus has "life eternal") is in the NT, and second I wondered what other sorts of "hope" there were in the NT. And these questions can be answered with syntax searches.

I made the below video that sets up the search and shows the results. If one just searches the Greek NT for ἐλπίς, 48 verses (53 instances) are located. But there are 18 instances where "hope" is qualified in some way. There are only two instances where it is qualified by "life" (ζωῆς), and both of them are in Titus (the two examples cited above in relation to Barnabas).

Why do I bring this up? Well, with the advent of the syntactically tagged databases of the Greek New Testament, I find myself asking more and more questions like this. And I'm more and more able to run a syntax query (many of which share the same basic template that this search has) to get a clearer picture of some grammatical phenomenon without having to run a blunt concordance search, and then sift through the hits. I'm able to get more relevant, more meaningful instances of what I'm interested in and sift through less chaff in the process. And this has made my study of the New Testament deeper, which can only help my understanding and application. And to my mind, that's what it's all about.

(See also: RevInt I: Reverse Interlinears as Books and RevInt II: Reverse Interlinear Lines and RevInt III: Reverse Interlinear Symbols)

Occasionally, when I assemble a piece of furniture — say for instance a “Jerker” desk from Ikea, like the one that I sit at — I am left with a few odds and ends lying on the floor. Then I scratch my head and wonder, “Do I really need that lock washer?” The real question, of course, is: Do I really want to take the whole thing apart again to figure out where it goes?

Occasionally, when you are reading along in a reverse interlinear, you will encounter some of the nuts and bolts that are left over in the process of assembling the alignment. Here and there will be a round dot (bullet point) in either the original language line or the translation line of a reverse interlinear, indicating that no reasonable equivalent for that word could be found in the other text.

For the most part, our editorial philosophy for making these reverse interlinear alignments has been optimistic. That is, we assume that if the translation committee thinks they’ve translated the original language words of a particular verse, then we assume that they are. The goal, then, is to account for the translation, not to demonstrate elementary principles of Greek/Hebrew/Aramaic grammar. As a result, we give the benefit of the doubt in making links between the words of the original text and the translation. Our editors try — sometimes quite creatively — to account for all of the words in the translation. All of which tends, we hope, to minimize the presence of bullets in the text.

But they do happen, for various reasons.

Does this mean the translation is “bad” where you see bullets? Not necessarily.

(See also: RevInt I: Reverse Interlinears as Books and RevInt II: Reverse Interlinear Lines)

There are quite a lot of symbols that you need to master in order to read a reverse interlinear alignment. Each of the symbols is has a popup definition in the Libronix resource, so you won’t have to memorize what they mean, but understanding them in the first place will help you with reverse interlinear fluency.

Nearly all of these symbols are in the original language line; it was decided early on in the reverse interlinear design process that we would try to keep the translation text as uncluttered as possible. After all, it is the top line.

So, let's take a look at those symbols, shall we?

(See also: RevInt I: Reverse Interlinear Resources)

You can profitably use a reverse interlinear by just reading it. I’ll look into some of the ways that Reverse Interlinears can be used in later posts, but first let’s just look at all the lines of information that are available in the two ESV reverse interlinears.

Some of my favorite new Logos Bible Software 3 (LBS3) resources are the new reverse interlinear Bibles (after Hebrew Syntax, of course) — and not just because I worked on them.

A reverse interlinear in LBS3 is many things: It’s a Bible version that shows the original language words behind the translation; it’s a Bible with stronger-than-Strong’s tagging; but most importantly, it’s a bridge from here to there, from a translation back to the original language text that lies beneath. Furthermore, it’s a bridge that anyone can cross.

Earlier I blogged about Highlighting English based on Greek Morphology. This involved using Logos Bible Software 3 and a Reverse Interlinear of the New Testament to highlight words based on the underlying language's morphology (word form, part-of-speech type information).

Over the past weekend I was thinking that this would be perfect to use when working through a text doing something like participant analysis. One thing that I find handy when working through a text at a paragraph/sentence level is to stop at each finite verb (verbs that aren't participles or infinitives) and determine who is taking part in the action. I also like to see if there is someone or something that the action is being done to, or if there are other circumstances to the action.

Using Logos Bible Software 3, the Morphology Filter applied to a Reverse Interlinear makes this easy — particularly if you don't know Greek. Here's what you do.

  • First, check out the video on how to specify a morphology filter in a reverse interlinear.
  • Second, once your Logos Bible Software 3 is fired up, specify a morphology filter for the ESV New Testament Reverse Interlinear. Your Part of Speech should be Verb, the Verb Type should be Finite.
  • Third, specify the style of highlighting you'd like. I just specified yellow highlighting.
  • Fourth, go to your passage and stop at the highlights. Ask yourself questions like:
    • Who or what is doing this action? That is, who is the actor?
    • Who or what is the action being done to? That is, is there an object?
    • Are there additional circumstances to the action? Clarifying adverbs or prepositional phrases?
    • Is the same person/thing doing action here that was doing the action with the previous verb? Or has there been a shift?
    • [whatever other questions you think appropriate]

When examining the text at this level, you should keep track of where the same party (or parties) is doing the action, and where the actor changes. This may indicate secondary action (e.g., "Jim said, 'When I was with Dorothy, she decided we'd have dinner at the Olive Garden' ".) or it may indicate a larger shift at, say, a paragraph level.

Stopping at verbs and examining the flow of action in the passage is one very useful way to work through a passage at a high level. Using reverse interlinears to combine the underlying original language part-of-speech information with highlighted English makes it much easier for those with no knowledge of the original languages to start to consider these issues in their study.

When you are studying a word, it's often a good idea to look at synonyms and antonyms for that word as well. For example, if you were studying the English word run, you might also want to consider how words like sprint, jog, or even gallop overlap in meaning with run, and to what extent they are different. You may also want to consider how run and its synonyms are transformed into other parts of speech: What can the word jogger tell us about the meaning of run that runny cannot?

Finding words that are related to one another in meaning is also useful for studying the Bible, or else resources like Girdlestone's Synonyms of the Old Testament or Trench's Synonyms of the New Testament wouldn't exist — not to mention Louw and Nida's Greek-English Lexicon of the New Testament based on Semantic Domains. The Louw-Nida dictionary is particularly interesting, since it arranges all the words of the Greek New Testament by means of a hierarchical taxonomy, where each entry rests within a “domain” of meaning alongside any other words that have some degree of semantic overlap.

That's all fine and good if you're only studying the Greek of the New Testament. But what about the Old Testament?

One thing I like to do when examining Greek word usage is to evaluate how the Greek word is used in similar context outside of the New Testament corpus.

This article will point out an easy way to use the Works of Philo (in English) in conjunction with the BDAG Lexicon. This same method can be used with other Greek corpora for which Logos Bible Software has English translations, such as the Works of Josephus (in English) or the Old Testament Pseudepigrapha.

The strategy discussed is really a temporary one as we're currently working on versions of the following corpora in Greek, fully morphologically annotated:

In my morning devotional time, I've been reading through the Pauline Epistles in larger chunks. I tend to dwell in areas, reading the larger chunks over again, and sometimes dwelling on smaller chunks.

For the past week I've been in First Corinthians 12 and 13. And I've been dwelling on 1Co 13.1-3.

But as is my way, I've looked at the text in the Greek too. And I noticed some stuff from a text-critical perspective, so I thought a post on how I walk through this kind of stuff might be a good one. So, even though I've recently discussed some of these issues on my personal blog, in this article I'll go into a little different detail, showing how I use Logos Bible Software in this regard.

Subscribe

Enter your email address:

Bible.Logos.com

Bible Search

Verse:
John 3:16; Jn 3:16; John 3

Keyword:
Salvation, Jesus, Gospel

With Operators:
AND, OR, NOT, “ ”

Add this to your site!

Social Networking

RefTagger

Bible Options

Add this to your site!

Recent Comments

  • Adam Navarrete: None are scheduled for San Antonio right now, but if read more
  • Rebecca Crist: Any training sessions coming to San Antonio, TX soon? read more
  • Manuel Brambila: Hello; Please! Please! Please! I cant afford any of the read more
  • Sallie: Would love to win.. thanks for the opportunity!! In Christ, read more
  • Cameron Mills: proverbs 23:23 read more
  • Lindsey Hoover: This contest is great! I have been searching to buy read more
  • Stan: When is it going to be available? is there a read more
  • dave mchugh: I think that it is a great idea! Thanks to read more
  • A Beaver: I would love to have the ESV leather bible. I read more
  • Troy: lol! read more

October 2009

Sun Mon Tue Wed Thu Fri Sat
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

Archives

Employee Blogs

Bob Pritchett
RSS FireSomeoneToday
RSS BobPritchett.com
Rick Brannan
RSS Ricoblog
RSS PastoralEpistles.com
Mike Heiser
RSS The Naked Bible
RSS Scribal Practices
RSS PaleoBabble
Steve Runge
RSS NT Discourse
Bill Nienhuis
RSS OriginalExpression
Sean Boisen
RSS Blogos
Phil Gons
RSS PhilGons.com
Ryan Burns
RSS Going to Seminary
John Barry
RSS The Infinite in Everything

Poll

  • What’s your favorite kind of blog post?