Threads from Henry's Web

Tag: Logos-Bible-software

  • RefTagger from Logos Bible Software

    I generally read Adrian Warnock’s blog because his theology is so glaringly different from my own that I think there’s a certain amount of community accountability that results just from forcing myself to read and consider his viewpoint.  (Sorry, Adrian, but that’s how it is!)

    But today he pointed me to a new tool from Logos Bible Software, RefTagger which appears to be a wonderful addition to this blog, considering the number of Bible references I use, and also the fact that I use the Logos software on my laptop.  (This is a Linux machine, so no Logos, but via my home network, I can remote control by laptop and use Logos anyhow.)

    It comes either as a snippet of code, or as a plugin for your WordPress blog.  I’m going to test it here and see how I like the overall result, but I will probably end up adding this code to a large portion of my various sites.  So thanks to Adrian for pointing it out!

    I also just have to point out, being who I am, that I am starting with a default version of TNIV for the tooltips, whereas Adrian, of course, has the ESV.  It’s fun to be different!

  • Logos Blog is Back and Free Commentary Offer

    I got an e-mail late yesterday telling me that the Logos Blog is back and advertising a free commentary volume.

    I find the Logos software to be an essential of my Bible study day, and though I know very little about the commentary series that is offered (Cornerstone), the names involved read like a who’s who of evangelical Biblical scholarship.

    In any case, wander on over and check it out!

  • Anchor Bible for Logos

    In comments to my earlier post on the Anchor Bible for pastors, Kent notes that the Anchor Bible will soon be available.

    One of the best ways to avoid getting bogged down in details is to employ the search capabilities of an electronic version the ability to hyperlink from Scripture references to the Greek text and English translations. This is a far more useful way to use the Anchor Yale commentaries for preaching.

    You might be interested in a new, electronic edition of the Anchor Yale Bible Commentaries from Logos Bible Software. It’s much easier to use than print versions, and about $2,500 cheaper.

    and

    I forgot to mention the website:

    Anchor Yale Bible (83 Vols.).

    (There’s also an interesting discussion on the Logos Blog.)

    Thanks to Kent for posting this here. I wish I could afford it, but even at the wonderful price, it’s beyond me at the moment. Those of you who can, however ….

    I don’t know as this will solve all the problems I discussed regarding the value of the Anchor Bible for the busy pastor preparing a sermon, but it will certainly help in finding just the points that are relevant for current activity.

  • Learning a Little Greek

    One of the major problems with seminary study of Biblical languages is that it is often short term and shallow. The seminarian, required to take a certain number of hours or just get by a particular test focuses all his efforts to getting past the hurdle. Precious few such students ever gain a real facility with the language. Some will have an exaggerated view of their own skills based on that study, but most will abandon what they have learned. Others will pop Greek and Hebrew words on their congregations, normally gleaned from commentaries and various articles of, often of questionable validity.

    In general, when you hear a pastor say “what the Greek really says,” prepare to be deceived. Not intentionally–the preacher really believes he knows, but actually he is probably missing the point. I have heard sermons in which the Greek word was completely wrong because the preacher simply provided the wrong Greek word. At other times, the error was one of context, when the preacher used a definition for a Greek word that was valid in some context, but not in the particular context in question. In one case, I heard a speaker recite the “real Greek” of a verse in four words. The only problem was that the verse was not, as he claimed, four words long in Greek, and not one of the four Greek words he used were actually in the verse he cited. I could just barely tell I was looking at the right verse based on the interpretation.

    I have a book in my library from the infamous Dr. Floyd Jones of KJV-Only fame. In the front of the book, on a page titled “TO THE READER – THE SOUNDING OF AN ALARM,” he cites a number of Hebrew words from Isaiah 14:12, in which he is giving the alarm regarding mistranslation. He should, however, be giving the alarm about his disastrous ignorance of Hebrew. I count no less than 8 errors in Hebrew in the course of a single paragraph. Now the KJV-Only position is so discredited that one might wonder why I bother to mention it. The reason is that most of the errors noted in that paragraph appear to result from the use of an interlinear in order to find the Hebrew form that is cited. Transliterations don’t match the Hebrew, though the translations match in the way an interlinear would.

    In both KJV-Only debates and discussion with lay “experts,” I have also encountered work done from Strong’s concordance. While it is more difficult to work with Strong’s than with an interlinear, it is even easier to be in error. Strong’s definitions are often out of date, and in fact they are generally not definitions at all but rather lists of glosses. I once was presented with a possible translation of a Hebrew text in which not a single word was translated correctly. On careful examination, however, every single word was translated by some word from Strong’s, and what was more, the resulting sentence was comprehensible in English though a bit stilted. It simply had no relationship to the meaning of the source text in Hebrew.

    We’ve probably heard that “to err is human, to really foul things up requires a computer.” Well, enter Logos Bible software, now with reverse interlinears (HT: Metacatholic–I recommend you read his entire post). Now don’t get me wrong. I own Logos with all the Biblical languages extensions I can get my hands on. But many wonderful tools have potentially bad uses.

    When a student uses tools that allow him to look up words more quickly so as to cover more ground in reading that’s a good thing. One way to actually gain facility in a foreign language is to work with it. Many students plow through one or two verses at a time and never go beyond that. They become specialists in individual leaves on individual trees, but they have no sense of how Greek or Hebrew reads or feels. Tools such as reader’s lexicons–works that give glosses by verses–can be very useful for rapid reading. But they don’t teach you Greek. Neither do interlinears, and neither do reverse interlinears. (Everything I say here about Greek is equally applicable to Hebrew.

    I have to discipline myself to spend time reading without the tools to prevent dependence. Especially in reading the Septuagint, I like to go into Logos so that I can quickly look up some of the words that I don’t know from my New Testament reading. But to really dig in and learn the material, I need to read without those tools from time to time. Now I have taken an different approach from the normal seminarian (whoever that may be!). I started in Biblical languages as an undergraduate. I had several years of Greek before I got to Seminary. I had three years of Hebrew. I actually read the passages I use when I prepare sermons first from the original languages. I use all the Logos tools constantly–except for anything resembling an interlinear. That is something I won’t do to myself.

    The writer of the post on the Logos blog bemoans the passing of original languages requirements in seminaries. But I would suggest that it will not be an improvement if people who are not competent with Biblical languages start substituting their judgment for that of the trained translation committees and reviewers that produce our modern English versions.

    For more on this topic see my series Word Study Dangers and my post on my Threads blog What the Greek Really Says.