In the course of preparing for their Greek finals I have received a number of wonderful questions from students about this or that passage of Scripture. And since Nick Batzig has been hounding me for over a year to include some kind of Greek exegetical comment on my blog, I thought it might be appropriate to share one with you, though it is a significant departure from my usual posts (I really try to steer clear of theological stuff here).

The question revolves around translating 1 Cor 15:26:

ἔσχατος ἐχθρὸς καταργεῖται ὁ θάνατος

Don’t let the brevity fool you. I found it very difficult to bring out the force of this in sensible English. The Greek syntax actually made me teer up a little. Here are some considerations.

  • The position of ὁ θάνατος makes it difficult to bring out the “surprise” of the passage. It is appositional with ἔσχατος ἐχθρὸς: “the last enemy… namely, death.” Translating as appositional in English seems overly formal to me, though. Paul makes his point with a bit of rhetorical flair, a flair that is removed in the “literal” English.
  • The verb καταργεῖται is both passive and progressive. The combination makes translation difficult, but the big problem is the force of the progressive. Most English versions regard it as futuristic, which would indicate the surety of the outcome described. I think it better to regard it as having a durative or tendential force.
  • Futuristic idea: either “the last enemy to be destroyed” (most translations) or “the last enemy that will surely be destroyed is death” (focuses on the surety of a future outcome). This is possible, but it is not the best explanation. Remember we are driving to a main point in all this discussion of resurrection: the (present!) stinglessness of death (1 Cor 15:55-6).
  • Tendential idea: “the last enemy is being destroyed” (that is, Christ is currently in the business now of destroying this enemy). This is my preference. See Thiselton’s 1 Cor commentary, p1234. The difficulty here is the passive. It’s really difficult to get (1) the tendential idea, (2) the passive idea, and (3) the pithiness all in one go.
  • Durative idea: “the last enemy has begun to be destroyed” (that is, Christ began destroying this enemy in the past and continues to do so. This is possible, but durative progressives are usually associated with a temporal adverbial clause, which we don’t have here.
  • Paul is all over the temporal and aspectual map in this section (1 Cor 15:23-28); progressives are bracketed by Aorists, which in turn are bracketed by progressives again. The whole constitutes a redemptive-historical description of the resurrection. We start with the broadest eschatological orientation: ἀπαρχὴ Χριστός, ἔπειτα οἱ τοῦ Χριστοῦ (15:23). One resurrection harvest in two parts (see Gaffin). So Christ’s resurrection starts the process, and the whole thing will be completed when his many sons (Genitive of relationship) will be raised ἐν τῇ παρουσίᾳ αὐτοῦ (temporal prepositional phrase (“when”) with a subject Genitive (“when he comes”). Within these two bookends we have a whole slew of activity, described with whole slew of progressives and Aorists and related temporal conjunctions, all of which is then described under the umbrella of Jesus’ βασιλείν. Sorting when each activity occurs can be difficult, and goes beyond the abilities of what started out as a simple post.

So the question is: can we bring all this content out with the same economy and forcefulness of Paul’s original? Here are my attempts at a translation.

Respecting the passive, though adding an adverb to bring out the tendential/durative force:

“Death, the last enemy, is already being destroyed.”

Or, avoiding the passive for the sake of clarity (our little girl has made me appreciate the NLT more than I had in the past):

“Christ is already destroying death, the very last enemy.”

Or, alternatively:

“Christ has already begun to destroy the last enemy, death.”

All of these are significant syntactic departures from the original, though.

In any case, here is my (loose, preliminary) translation of the entire passage, 1 Cor 15:22-27a:

ὥσπερ γὰρ ἐν τῷ Ἀδὰμ πάντες ἀποθνῄσκουσιν, οὕτως καὶ ἐν τῷ Χριστῷ πάντες ζῳοποιηθήσονται. Ἕκαστος δὲ ἐν τῷ ἰδίῳ τάγματι· ἀπαρχὴ Χριστός, ἔπειτα οἱ τοῦ Χριστοῦ ἐν τῇ παρουσίᾳ αὐτοῦ, εἶτα τὸ τέλος, ὅταν παραδιδῷ τὴν βασιλείαν τῷ θεῷ καὶ πατρί, ὅταν καταργήσῃ πᾶσαν ἀρχὴν καὶ πᾶσαν ἐξουσίαν καὶ δύναμιν. δεῖ γὰρ αὐτὸν βασιλεύειν ἄχρι οὗ θῇ πάντας τοὺς ἐχθροὺς ὑπὸ τοὺς πόδας αὐτοῦ. ἔσχατος ἐχθρὸς καταργεῖται ὁ θάνατος· πάντα γὰρ ὑπέταξεν ὑπὸ τοὺς πόδας αὐτοῦ.

For just as all die in Adam, so in Christ all will be made alive. But each in its own proper order. Christ as firstfruits, then those who are sons and daughters of Christ when he comes, then the end, when he will hand over the kingdom to His God and Father, after he has destroyed ever authority and power. For it is necessary for him to continue to rule until every enemy has been placed under his feet. The Last Enemy, Death, is already being destroyed, for all things have been placed under his feet.

What do y’all think?

Oh, and I have found Thiselton’s commentary on 1 Corinthians to be a very helpful handling of the Greek text. He consistently appeals to Paul’s overarching theology in its eschatological/redemptive-historical emphasis.

 

I have written a series of guides on best practices for typing in Greek. The trick is to use Unicode. Though it requires some initial struggle the payoff is enormous, and will save you frustration down the road.

There is a new guide out for Linux users, and it looks excellent (pretty pictures). Find that here.

For Windows setup follow this guide. For fonts, check out my review here. And if you need a font with text-critical glyphs, try this.

 

I’ve mentioned BibleArc before. Apparently it has recently received a major upgrade with some new features, including automatic parsing of Greek words, the inclusion of the Hebrew OT, and enhanced sharing capabilities. Check it out.

Don’t know what arcing is? Check out this video from John Piper on how he uses this tool. If you are interested in arcing and other linguistic concepts as they apply to biblical studies, check out Cotterell’s Linguistics and Biblical Interpretation

 
Greek language
Image via Wikipedia

Are you using Unicode to type in ancient Greek (if not, follow this guide)? Do your prefer OpenOffice to Microsoft Office? Well today is the day where it all pays off. There is only one Word Processor in the world that spell-checks ancient Greek, and that’s OpenOffice. You can set it up by installing this plugin for OpenOffice 2.4 or higher.

 
Rossano Gospels, 6th century, a representative...
Image via Wikipedia

Mourning the loss of Zhubert? Me too, and I will have an update on the copyright discussions soon, and a new eBook of the GNT as well.

In the mean time there is an excellent new reader’s Bible available that is based on Tischendorf‘s Greek New Testament. Check that out here. It features handy footnotes and popups. You will need Google Gears for it to work, but that’s an easy install.

HT: Justin Taylor

Update:David Stark points out that the site also displays the OT, with notes for both Hebrew and Aramaic.

 

Update: The links to the ebook in question have been (preemptively) removed because of licensing issues. Such licensing issues are not an issue for the SBLGNT, which now has a kindle version available. So download that instead!

Greek NT on the iPhone

Having Googled long and hard for a free, accented, open-source, Unicode eBook of the Greek New Testament, and to no avail, I decided to make one myself.

Getting the Book

You can download the NA26/UBS4 Greek New Testament eBook in the following formats (right-click and “Save File As”): Kindle, Palm, mobi, and xhtml. Follow the instructions for your device. The Kindle version is the best, so use that if your device supports it. You can convert eBook files using the free application Calibre.

iPhone and iPod Touch users can use the free application Stanza with this guide to get everything set up (it’s easy).

If you need another format for your reader, try Stanza’s Desktop Reader to convert one format to another.

I will post about new releases and improvements on this site, so if you like what you see you may want to subscribe. There are a couple of improvements I would like to make–like sub-chapters and a better Table of Contents–but that will have to wait for another time. Stay tuned!

Licensing

The source text is for this eBook came from the MorphGNT with UBS4 (ver. 5.08) by CCAT and James Tauber, as produced by the Work Viewer web-app created by the Open Scriptures project. It is the same Greek text you will find on the much more robust Resurgence Greek Project and was originally derived from NA26.

This eBook is distributed and licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported license, as allowed and required by the use of MorphGNT.

te

(pre

 

It’s been a long time coming, but SBL has finally released their promised Greek Font. The download page is here, or you can download it directly here. There is also a Hebrew font.

The fonts work in all Operating Systems (Windows, Linux, Mac). They are not open-source (so a couple of other fonts are still my top recommendations), but they are free to use:

SBL fonts are made available without cost to individual scholars for non-profit use. Commercial use by publishers is reserved for members of the SBL Font Foundation.

If you haven’t already set up your keyboard to support Unicode Greek, follow my guide (for Macs go here, or for Linux here).

SBL’s Biblical Font FAQ is also worth a read. If you’re not already familiar with the advantages of Unicode (as described, for example, in my guide), you may find their explanation of interest:

Why should I bother with a Unicode font? Isn’t it easier to keep using the fonts I have used for years?

With older, non-Unicode fonts, character glyphs were simply mapped over Roman characters. So, with SPEzra for example, pushing “b” displays a bet, and “[” displays an ayin. However, the computer understands these characters as “b” and “[.” Thus, when the document is transferred to a computer that does not have that specific font installed, the computer displays those characters.

Unicode seeks to allow for transfer of encoded documents between platforms and independent of fonts. So, if a document is typed using one Unicode font, it will also be viewable using another Unicode font. Likewise if the font is not installed, the computer simply defaults to its normal Unicode font. If one wants to use a different font for aesthetic (or other) reasons, one can change the font just like one would do with English. Additionally, the computer understands the characters to be the ones that the screen displays. So, an ayin both displays as an ayin and is encoded that way. This makes cross-platform text transfers and searches possible, because texts can be encoded with the characters in which they are written. Even though learning to switch to and use keyboard layouts for other languages takes a little bit of time to learn, the benefits of Unicode more than make up for this small initial investment of time and effort.

HT: Rod Decker

 

If you ever type in Greek, Hebrew, or any other language that requires special characters, then you need to make sure you are using a Unicode font. I have written up a pretty thorough guide to using Unicode fonts in Windows and/or Linux, but my Mac knowledge is flaky. If you’re a Mac user and are interested in typing in Greek or Hebrew then follow this guide.

Regardless of your operating system you might also be interested in my introduction to Unicode.

 

example-textRod Decker and Danny Zacharias have reported about a new unicode Greek font that will be of particular interest to those that need text-critical glyphs. From Zacharias’s blog:

I’ve just been made aware of an excellent Greek unicode font that is the most thorough I have ever come across. Designed for the papyrologist and text-critical scholar in mind. The font is called IFAO-Grec and can be downloaded at the bottom of this page. You will see also a documentation page, which lists all of the extra characters available.

You can download the font here.

Rod Decker mentioned in a comment that the font is offered free of licensing constraints:

The only statements I can find re. licensing issues is that “IFAO-Grec Unicode is issued free of all rights” and: “Elle est gratuite et libre de droits” (~ “It is free and free of copyright”). There does not appear to be any reference to any of the “Open” licenses.

This is not quite the protection I would recommend (see my post about Greek font recommendations) but if you need a full text-critical arsenal, this might be a good option.

For most of us, however, some other open-licensed Unicode font might be preferable. Check out my guide for more information and font recommendations for Greek (and Hebrew).

 

It’s pretty easy to add all the various modules and resources available in Bibleworks to your Zotero database. Follow this guide.

© 2011 Nerdlets Suffusion theme by Sayontan Sinha