Lately, I’ve enjoyed the balance of using a reader’s text and a bigger lexicon. I say “balance” because this combination allows you to move quickly when you want to move quickly, and for me that is what I want most of the time. The reader’s text facilitates this wonderfully. When I want to step into the bigger picture and explore the broader meaning of a word, when I want more than a basic gloss or a meaning in this context, the big lexicons are what I want. Lexicons that are devoted to the particular corpus you are reading will often even satisfy the desire to check your understanding of a particular phrase in a particular verse because they provide translations of so many occurrences. So in addition to giving you a more complete picture on the use of a word across time or across the literature you are reading, the big lexicons frequently eliminate the need to consult your favorite translation, as well.
Details by Corpus
For the New Testament, I’ve really enjoyed the Tyndale House reader’s edition this year (leather/hardback). I’ll do full post on it this summer, but what I enjoy about it is everything from the font, to the paragraph layout, to the textual choices (cf. 2 Corithians 5:3, ἐνδυσάμενοι), and more. The lexicons of choice have been either BDAG, Montanari’s GE, or LSJ. Depending on the scenario, I’ll use print or digital versions of the lexicons.
For the Septuagint, the new reader’s edition is splendid (flexisoft). I’ve been in Leviticus and enjoying reference to LSJ, Montanari, and occassionally Muraoka or LEH.
For Anabasis, Steadman’s reader has been great. He only has books 1 and 4, but all I’ve needed this year is book 1. Eventually, I will have to turn to the Loeb, which is fine, but a reader is always preferable. It’s usually a digital LSJ that I turn to when I want more. Montanari would be great, but when I finally get around to Xenophon during the week I’m rarely in my office and I never have time to flip pages and read leisurely.
Hebrew has been on the back burner, but with a friend I’m making another pass through Genesis in the BHS reader’s edition (flexisoft). I normally turn to digital versions of HALOT or CDCH, but when I’m home I go to my print copy of Holladay (because of Michel Gilbert’s experience shared here and here).
Conclusion
Usually when you want to turn from a reader’s text and explore a bigger lexical work, it is more enjoyable to use a print lexicon if the situation allows. This weekend it’s been the reader’s GNT, BDAG in print, and Apple’s Arcade Fire Essentials playlist. Saturday mornings are made for this sort of reading experience.
There are so many ways to read in the original languages. Don’t latch onto one way and make that the only way you can feel satisfied in doing it. Just do it.
For over ten years I used Logos as my primary tool for studying the Bible. A few years ago, however, it seemed clear to me that my primary interests and the focus of Faithlife (the company that makes Logos) were going in different directions. I wanted a product that prioritized original language research, and it seemed to me that Faithlife was focusing primarily on creating new ways for their average customer to discover new things in Scripture. Helping people discover new insights is great, but it wasn’t where my interests were. I was struggling in the forums to get typos fixed in what I considered to be key resources, and so I eventually made the move to Accordance. I love Accordance and still use it every day. So why am I reconsidering Logos?
At some point, Logos ironed out the typographical problems in their Dead Sea Scrolls resources. That was the primary issue that turned me away from the product. Recently, they also significantly upgraded their mobile app — changes that affect the every day reading experience. Tabbed browsing makes it easier to have multiple resources open and easily move between them. What I care about is how quickly and fluidly I can move throughout the program, open resources, look up words, and run searches without seeing the spinning beach ball of sluggishness. The reading experience is the key.
Finally, when Logos 8 released I heard there were significant performance improvements, and this is what made me want to give it another shot. Logos is notorious for severely taxing older computers with an intense, frequent indexing process, and in my opinion, the program has not been snappy since the Libronix/Logos 3 days. The way the promotional material spoke about performance improvements tipped the scales. I had to give it another shot. I’ve been using Logos 8 for a couple months now, and here are a few thoughts on my experience with both the Mac and iOS apps.
a mid-2014 MacBook Pro with a 2.2GHz i7, 256GB SSD, and 16GB of RAM
an early-2014 MacBook Air with a 1.4GHz i5, 128GB SSD, and 4GB of RAM
Here’s the scoop: Logos 8 runs well on both machines.
On the MacBook Pro, I thought the performance was solid from start to finish. The startup time was very reasonable, it was easy to open and move around multiple resources, searches were very fast, and much to my surprise even the indexing process seemed more efficient. I am really happy with how quickly I can open multiple resources, move them around, and run searches. At no point did I hit a wall where I thought the program was having to catch up. That’s a big deal, but that is also on a MacBook Pro. Granted, it’s a four year old MacBook Pro, but it has 16GB of RAM.
The real story here is that Logos 8 runs well on my MacBook Air with a measly 4GB of RAM! I did not expect this. I want to illustrate what I mean by “well,” so the video below demonstrates basic performance functions like opening the program, opening resources, moving them around, looking up words, and running a simple morphological search — text, lexicon, & concordance work.
Even in a resource as typographically complex as the Qumran Sectarian Manuscripts, I can scroll through the resource with relative ease. If I scroll down or up as fast as I can in any of the resources I opened, eventually scrolling becomes jumpy, but that is not a big deal. You don’t navigate from Matthew to James by scrolling. You use the navigation box. If you just want to scroll a few paragraphs or chapters or even to the next book of the Bible, that’s no problem.
I don’t have any detailed metrics to report — just a video and my testimony based on every day, normal use. I am happy with the performance of the Logos 8 Mac app.
iOS app
The iOS app serves well as an on-the-go reading companion. You can download books for offline access, including morphologically tagged resources. So if you want to download your GNT and be able to double-click for morphological information and quick word lookups, you can do this even when offline. When your text is downloaded and the lexicons you want to access are downloaded to your mobile device, looking up words is fast — down right snappy.
The mobile app features tabbed browsing and the ability to save workspaces. This means that I can create a workspace for reading Anabasis with the text, lexicon, reading notes, and companion grammar, easily swipe between the resources, and then save that workspace when I’m done and navigate to another reading setup for the GNT or Hebrew Bible.
Aesthetically, both the Mac and iOS apps look great. I love the Greek and Latin fonts. The iOS app is particularly noteworthy because it fills the screen of the latest iOS devices, from edge to edge, and has a true black reading mode that is gorgeous on OLED displays. Here is a video that illustrates opening a saved workspace, looking up words, navigating to another workspace, and using tabbed browsing. I’m recording this on a 2018 12.9 iPad Pro:
As a reading companion, the app does its job, but there are a few annoying glitches that affect the reading experience. For example, if you need to look up multiple words in a sentence and want to do this by double-clicking each word, you find that double-clicking frequently just highlights the next word without showing the quick information pop-up. The other issue is that sometimes the app seems to cause the resource you are viewing to jump several lines up. This happens most frequently when flicking between tabbed resources in the same workspace.
These issues are much easier to illustrate with a video. In what follows note that every other word shows the information pop-up. The second issue is harder to reproduce, but it does happen a couple times toward the end. As I move around in the text and flip back and forth between resources, notice that the text jumps from Matthew 5:24 to Matthew 5:9. This happens around second 40. The same thing happens again around second 50.
Conclusion
I’m really happy to say that Logos 8 seems like a mature product. There are new, experimental features, but the performance improvements make Logos 8 seem to me like the most stable, efficiently running version since the era before the major rewrite that took place between Logos 3 and 4. I have tried to show here that for everyday reading, lexicon work, and research, Logos 8 should run well enough on older, entry-level laptops, as well as more robust machines. I’m sure there are portions of the program that would still push an old MacBook Air to the limit, but those are not features that I have encountered as I use the software for teaching, reading, and reference. At this point, the mobile app still seems primarily intended to be a reading companion to the Mac app, but if you primarily use the software to read and reference lexicons, the mobile app can serve as your primary driver. I use it far more than the desktop version, and overall I’m happy with it. I hope the glitches noted above will be fixed soon, and I would love to see more robust, full-featured morphological and lemma search functionality come to the mobile app.
I experienced a passage in Exodus this morning as I never have before. I was reading Exodus 32, and verses 17–18 seemed to jump off the page. I have read this passage before in the Septuagint, but perhaps I was moving a little too fast. I was reading for comprehensive exams the first time, and that sort of reading is rarely reflective. Here’s the passage:
And when Joshua heard the sound of the people crying out, he said to Moses, “That’s the sound of war in the camp! [Moses responded] and said, “It’s not the sound of those marching ahead with force or of those turning to run. But the sound of those marching headlong into wine is what I hear.”
Now, that’s my idiomatic translation, and it captures the way I experienced the text. Rendering ἐνάρχομαι in verse 18 is difficult to do in an idiomatic way. It translates three instances of IV.ענה, to sing. Here’s the Hebrew of verse 18:
It’s not the sound of conquering or the sound of defeat; it’s the sound of singing I hear.”
Whatever you do with ἐνάρχομαι, it seems pretty clear to me that the Septuagint is a little more explicit about what is happening. I hear more contrast and perhaps frustration with the addition of ἀλλά and especially the addition of οἶνος, wine — a word that makes explicit the real reason the people were in such an uproar.
So, I’m drawing no major text-critical conclusions here; it’s just striking. This verse made me stop and reflect and visualize the scene as I never had before. I had to check the Hebrew to see if the Septuagint text was different in any way, and as it turns out, it is just different enough from the Hebrew to at least partially explain why the passage seemed so fresh and new.
Incidentally, I was reading in the new Septuagint Reader’s Edition, which you can still get for a fantastic price at CBD. More on that edition in the coming weeks.
Charles Jones posted notice that the University of Zurich has made available all five volumes of Dominique Barthélemy’s Critique textuelle de l’ancien Testament.
There is nothing quite like this work. I’ve posted in the past on the Hebrew Old Testament Text Project, which led to these volumes, and on the unique role Bathélemy played in the committee’s work. These five volumes are the most comprehensive treatment of the textual problems in the Hebrew Bible ever produced.
In print, each volume is very expensive. I’ve always wanted to own copies, but with the price — a couple hundred bucks a piece if I remember correctly — there was just no way. To have each volume in a quality PDF is so fantastic.
Give them time to download. The files aren’t that big, but they took a bit longer to download than I expected. I should note that they are all in French. Here’s the permalinks:
Over the summer I did a series of posts about different ways of reading Greek and Hebrew. I said that my the summer time tools of the trade are a print text and a print lexicon. During the school year, however, I am rarely able to read in my home office. To continue reading with a print text and lexicon would mean that everyday I have to carry multiple heavy books around campus. My favorite way to read hasn’t changed, but during the school year I’m really happy to settle for a print text and digital lexicon.
Print text
NA28, Rahlfs’ Septuagint, a Loeb Crito, and Steadman’s Lysias 1 & Crito are in my bag on most days, but because Rahlf’s Septuagint is so thick, sometimes it gets left behind. I prefer a print text because I think holding a book and flipping pages is more enjoyable, unless the book is old and gross. I realize that sometimes an old book is great, but I am not a fan of mold and other people’s finger grime — for example, crusty library copies of Migne or seminary library copies of a GNT.
Digital lexicon
For New Testament, Septuagint, and classical Greek there are a couple really great, affordable iOS options: Logeion & Protagoras. Logeion is free and includes LSJ, Middle Liddell, big Lewis and Short, little Lewis, and several other Greek and Latin lexicons. Protagoras is only a couple dollars, and for Greek it includes LSJ, Middle Liddell, Slater, and Autenrieth. For Latin it has both the full Lewis and Short and the smaller version by Lewis.
Logeion is amazing because of the way it interacts with Attikos, and because the user interface allows for quick entry and easy movement back and forth between the last few words you’ve looked up. Logeion hasn’t yet been updated for the iPhone X, however.
Protagoras, on the other hand, looks great on the iPhone X, and the developer has formatted the text in a way that makes a big difference for longer entries. Every portion of each entry that was originally in italic type appears in Protagoras as bold-italic. This means that as you scan a long entry your eyes can easily jump from gloss to gloss. For quick reading, this is such a timesaver. The bold glosses and iPhone X support means that I’ve been using Protagoras as my digital lexicon more often than not. One additional feature of Protagoras: it has a bookmark feature. As you are looking up words, you can bookmark them, and after your reading session, or maybe at the end of the week, you can go back to review.
For any lexicon not found in Protagoras or Logeion, I turn to Accordance. It is much more expensive, but it is worth every penny. With Accordance you are looking at a price tag much closer to what you would expect to pay for a print text, and this is completely understandable for works that are still in copyright and/or works that they have labored in house to tag in various ways. BDAG and HALOT, for example, are lexicons that I would do whatever necessary to have digitally and in print.
One final note about the digital options: I appreciate the ability in Protagoras and Accordance to type the Greek word you are looking up in beta code. This just saves the step of having to change your keyboard.
Experience
When reading this way, I usually access a digital lexicon on an iPhone, sometimes on an iPad. The bigger screens on the iPhone X or one of the plus models turns thousands of pages with tiny print into a much more readable, handheld reading companion.
This …
becomes this:
I know that the thought of your phone lying directly on top of the book you are trying to read sounds repulsive to some. Random notifications are a real threat, but they’re something that can be muzzled. Waiting for the ideal reading conditions just means you will not read as much text, and the number one thing most people need coming out of their first year of Greek is time in the text reading quickly. For more in that line of thought, see this post on reader’s texts.
Conclusion
Whether you are fresh out of your elementary courses or you’ve been doing this for decades, reading with a print text and digital lexicon is comfortable on the go. Sometimes even at home you just want to sit on the couch and relax with a text and lexicon that makes a small footprint but still gives you all the info you need. This way of reading fits those situations well, too. The print text allows an immersive reading experience and provides all the memory benefits of the sensory experiences that go along with holding a physical book, and the digital lexicon gives you portable, quick access to the vocab you need to keep moving.
This is the primary way I’m reading these days. Read however you like.
Some say reading in Greek and Hebrew versus reading in English is like the difference between watching a show in color versus black and white. Others might say something like 2D versus 3D. I don’t think these metaphors are the best ways to describe the experience. Reading in Greek and Hebrew slows me down and helps me rummage around in the text and reflect. For me, that’s the core idea. It gives me something to do.
I’m asking and answering this question as someone who initially learned the languages to read and teach Scripture. I’m going to write more about other benefits and things that flow from this rummaging and slow down, but in this post I just want to lay the foundation. How many times have you sat down to prepare to teach or preach and you read your passage and think, “Ok, now what?” If you are reading in the original languages you have so many different resources and tools to explore, and I’m thinking primarily about lexicons and concordances. If you don’t regularly read and work with the original languages, all you can do is skim the surface of an entry in BDAG or HALOT. Exploring contemporary literature, figures of speech, the metaphors used in your passage, looking at a words full range of meaning and determining which meaning is relevant for your passage — these are things you can actually engage in yourself if you can read the language.
But in my opinion, those things are not the primary benefit of the original language slow down. The real benefit comes in your day-to-day reading. It’s about stripping away the familiarity of your natural language and lingering over the original words. Especially for the first few years of reading, you have to decipher every word and phrase, and the fog never really lifts. Sure, after a few years, you may be able to read one or two or four chapters in an hour, but it’s still not English. You’re moving slower, and when I do this, I find that I make connections with other portions of scripture that I wouldn’t make otherwise. With certain phrases come flashes of other stories or scenes, and my imagination takes off. This sort of reading isn’t about exegesis. It’s about rummaging. It’s about trying to step through the wardrobe into the real world of God’s presence.
There is only one type of reading group I have stuck with and enjoyed, and that’s a digital reading group of two. I once made the mistake of trying to lead a Facebook reading group. Won’t do that again. It just takes too much time to maintain all the join requests and administrative notifications, and if you have a large group, keeping up with the comments drains your time to read, which is the whole point.
For over a year now, my Greek reading group has had only one other member, Abram KJ. He and I just finished a GNT read through and are starting on the Pentateuch. We do not live in the same area so our workflow is completely digital. We don’t meet, but as I mentioned in the last post, we’ve used Todoist to manage a shared reading plan, and it has worked wonderfully. For the GNT we commented on tasks in Todoist to facilitate reading discussion, but for our Pentateuch journey we are trying out Twist (initial thoughts here). We will use use Todoist for the reading plan and Twist to manage our comments. Any sort of live discussion usually takes place on iMessage.
Reading time is in one sense a luxury, but in another sense it’s as essential as food. I work at the library as a research aid for students, and someone asked me the other day how to find time for Greek and Hebrew reading while managing seminar papers and the rest of life. I think you have to prioritize reading on the same level as eating. You simply cannot wait until life isn’t busy to read. Isn’t reading the whole point of the education? You take all these language classes for the purpose of reading the literature written in the languages. Everyone finds time to eat, and everyone can find time to read. Groups help, however, because reading big books can be a lonely journey. It’s always nice to know someone is walking with you.
I think the key for any reading group is to keep everything as simple as possible, even when it comes to expectations. Our “plan” is simply a list of chapters (Abram Gen 1, Brian Gen 1, Abram Gen 2, Brian Gen 2, etc.) Each chapter is a task in a Todoist project called Greek Reading. Ideally, we will both read one chapter a day, but that rarely happens. No worries. Just read when you can, and keep going. If someone falls a little behind, send an encouraging text. If someone falls far behind, the other person can read something else for a week or two and let the other catch up. We are both committed to regular reading, but over the past year each of us fell behind more than once and we always caught up with each other eventually. Schedules vary, and each person has certain seasons that are more busy than others. That’s why the digital notes are so helpful. If I fall behind, I can check out Abram’s comments on each chapter as I catch up.
To sum up, here are my suggestions for digital reading groups:
Keep the group as small as you can.
Keep the plan as simple as you can.
Be flexible and know that you won’t always stay together.
For writing anything more than a note, I use two apps: Ulysses and Word. I like one of them and tolerate the other. I’m just going to tell you about Word today, the one I tolerate.
If I weren’t a student and a teacher, I would never touch Word because Ulysses is absolutely sublime. If your document has footnotes, however, you should be using Zotero, and this means using Word on a Mac or Windows computer. So for the dissertation and any conference papers, I turn to Word. Word also gives you more control for precise, quick formatting, which I need for writing assessments.
For about the past year, Word for Mac has worked well with right-to-left scripts like Hebrew and Aramaic. For a couple decades, Word and Mac didn’t play well together. I you were doing anything with Hebrew you had to use something like LibreOffice or Mellel. Many people don’t realize that this era is over. The only remaining Hebrew/Aramaic hang up is the fact that the vowel points in SBL fonts do not align correctly. As I understand the situation, this is SBL’s problem and not Word’s. My school allows the use of Times New Roman font throughout the entire document, and I actually like the look of TNR for Hebrew, Greek, and English. It’s not my preferred font, but for technical writing it’s easy and everyone has it on their devices. The only situation where you will run into a problem with TNR is if you want to put diacritical marks above a Hebrew letter to mark the letter as “partially visible” or something like that. If you are working with DSS transcriptions, you will probably still have to use SBL Hebrew and Mellel at this point. Hopefully SBL will update their fonts soon.
The real draw towards using Word is that your documents are easily shareable. The chances are that whomever you want to share your work with uses Word. But there is another significant benefit: the iOS app works pretty well, especially if all you need to do is edit documents on the fly. During the past school year, I would take only my iPad to class, and when we found a typo in a quiz, I would fix it right away in the Word iOS app. Occasionally, I would print handouts from Word using Readdle’s Printer Pro, and maybe once or twice I actually wrote a quiz in Word for iOS. This became problematic for the vocab sections of the quiz because for some reason with a multi-column layout combined with Greek polytonic characters, Word began acting crazy. The cursor would jump around all over the place when I would start typing.
I don’t think you can create new character and paragraph styles in Word for iOS, but if you open a document that already has styles applied, you can use those styles with the same document. I think you can also save a blank document as a template with the style you want, and just start there.
One other thing the Word iOS app does really well is work with cloud storage. You can log into your Google Drive, One Drive, or Dropbox accounts and open files within the Word iOS app. Word downloads the latest version and opens it pretty quickly. While you are working in the document, everything automatically saves, and when you leave the document, Word uploads your changes to your cloud service. Everything stays in sync.
I really prefer to write in Markdown, and that’s where Ulysses comes in. But good old rich text word processing is still necessary for the time being, and Word isn’t bad.
If you have an external keyboard attached, you can actually type polytonic Greek on an iOS device. It used to be more hassle than it was worth to use an iOS device and an external keyboard, but the release of the iPad Pros and the Smart Keyboard changed the game.
You add Greek and Hebrew keyboards just like always:
Settings > General > Keyboards > KeyboardsBut when you have an external keyboard attached, there is an extra Hardware Keyboard menu that allows you to choose which Greek or Hebrew or English keyboard layout you would like to use. It’s curious that they call it Hardware Keyboard because what we are really talking about are software keyboards for use with a hardware keyboard.
The Greek Polytonic keyboard layout is the same as what you find on Mac and Windows computers. I’ve been using it for years because, though there are plenty of others out there that might be in one way or another more user friendly, this one is always preinstalled and ready to roll.
Here’s a collection of posts I’ve written on different ways of reading original language texts. I find myself frequently moving from one way of reading to another. Sometimes I read one way for a week or a month or a year, but it’s bound to change. That’s a theme that runs throughout the posts. There isn’t one right way to read. Read however you want. Just read.
