Archive for the ‘scripture’ Category

The benefits of free data

Wednesday, February 24th, 2010

Efraim Feinstein’s post “An Economic Argument for Free Primary Data” is definitely worth the read. He argues that freely licensed data best serves a community’s needs because it reduces duplication of effort and therefore conserves resources. It is certainly true that many works have been digitized into proprietary formats many different times. This is similar to my argument about the practical problem of Christianity and Copyright: that copy restrictions make data less useful in the digital age.

A discussion of this post on the Open Scriptures mailing list generated an interesting exchange questioning the applicability of “do not muzzle the ox” to copyright royalties. I’ve written on that issue in brief before, but I may flesh out my views on that in a longer post soon.

Scripture and APIs

Thursday, February 18th, 2010

I’ve been having some correspondance on the Open Scriptures mailing list. Weston has been working on implementing database models for an API using Django. One of the most challenging aspects has been finding out how to provide structural information to the text: verses, chapters, title headings, etc. There’s also been a desire to not rely on any particular structural marker in the database. So the base unit for storing the text is what is called a Token in the project. It is comprised by one of the three atomic structures of a text – word; punctuation; whitespace. Of course, there may be cases where even the basic Token can be split, but you’ve got to start somewhere.

To provide structure, Weston has proposed a Token linkage system, where you can record a certain structure (e.g. “Verse 12″) and using the features of a relational database, connect it to the tokens which should be included in that structure. There is even a feature for non-linear token linkages, if anyone finds a use for that.

I am optimistic about the potential of this particular project. Once the API is nailed down, there will be a lot of great opportunities for “client” apps, using whatever framework they wish. Until then, the API has to be finalized and garnished with built-in methods, and the models have to be tested with real data (which requires that the data be ported to the models in the first place). At any rate, it’s a good time to be interested in the scriptures and open source software. My experience with databases is not the strongest, but I am pleased that the project is using a Python framework, since it is my best language. But it’s also fun to bring my education to bear on technical problems – sort of a perfect storm of personal interest for me.

Note: This post has been adapted and cross-posted on the Open Scriptures blog.

Hexapla

Monday, February 15th, 2010

Today I discovered a very interesting project: The Hexapla Institute.

The purpose of the Hexapla Institute is to publish a new critical edition of the fragments of Origen’s Hexapla, an endeavor which might be described as, “A Field for the 21st Century” to be available in a print edition and as an online database.

In other  words, it’s about the coolest project I’ve ever heard of. Sadly the website seems a bit out of date, so I’m not sure how/if the project is progressing at this point.

On the canon

Thursday, January 28th, 2010

In the adult education class I have been teaching we took a look at the canon last night. I feared that compared with previous topics I would be short on material, but I actually ended up going a bit long (and cutting off questions/discussion). I’ll have to get better at making time. Still, we had some good discussions about the scriptures, the Apocrypha, and some of the gospels which are covered from time to time in the media. The class was particularly amused and flabbergasted by the last sentence in the Gospel of Thomas.

OT class recap

Thursday, January 14th, 2010

The class went fairly well last night. Unfortunately I tried to pack too much content into 1 hour 15 minutes, so we did not get as much question and discussion time as I had hoped. That was not terribly surprising given the scope of the material. Still, my churchmates were (apparently) engaged and inquisitive, and I think I was able to share with them a few things they had not learned before. Also, I have a good subgroup of folks who are knowledgeable in their own right, so I get to learn from them (not to mention borrow some really interesting books).

Next week it is on to the New Testament.

Old Testament Discussion

Wednesday, January 13th, 2010

Discussion question for tonight’s class:

Why should we as Christians read the Old Testament?

Old Testament survey

Tuesday, January 12th, 2010

I recently began teaching an adult education class at my church. The title is “Historical Backgrounds of the Bible – How did we get the scriptures?” The class is only 6 weeks long, with 5 remaining, so time is going to be really tight. Here is my plan for the classes:

  • Old Testament overview
  • New Testament overview
  • Canon
  • Transmission of scripture
  • Translation of scripture

As you can see, covering the entire Old Testament in one night is going to make for a very broad survey. I’ll try to stick to the basics and facilitate conversation as best as I can.

Overall I am really excited for this course. This is my first experience of any kind in the role of teaching Bible to adults. Hopefully I will learn a lot and my class-goers will learn something too.

Vocabulary Analysis

Monday, November 23rd, 2009

While reading Ehrman’s Jesus, Interrupted I got the idea to look in to vocabulary studies. You know, the ones where linguists catalog all the words used by a particular author and use the data to compare various works by (or purportedly by) that author. Does anyone know of a publication which lays out the basic methodology for doing this? I might try to write a script to help with the first step. I’m also interested in applying these methodologies outside of the biblical texts to see what they might yield. For example, how much does the vocabulary base of authors change across genre, time, etc.? I’ve never read anything which attempts such a study.

Verbosity in translation

Tuesday, September 15th, 2009

In the midst of all the recent discussion of varying “translation philosophies,” I came across an article by Karen H. Jobes on bilingual quotation (like what they do at the UN). The article itself is very interesting. Toward the end there is a discussion on verbosity in Bible translation. The bottom line is that a certain popular translation is more verbose than another certain popular translation. Jobes insists she is not trying to say anything bad about the first or good about the second, just that word counts are not necessarily a good indicator for the “literalness” of translation. I agree on the latter point.

Thomas did an interesting workup to show how verbosity correlates to the spectrum of translations. The bottom line: it doesn’t, just as Jobes said. More “dynamic” approaches can lead to more or fewer words, it seems. Perhaps the whole point is moot, because I don’t know of anyone who counts isomorphism as a positive characteristic in translations.

The Big Business of Bible

Wednesday, September 9th, 2009

The Bible is a consumer product. Publishers want you to buy one or more, and they have just the product for you:

NIV Revision: Third time's a charm?

Wednesday, September 2nd, 2009

The NIV is getting an update, its first since 1984. This will actually be the third attempted update since then, with the first dying in its early stages in 1997, and the second, the TNIV, dying in a maelstrom of bad press and poor marketing. What ultimately killed both of these efforts was the gender-inclusive language debate, especially in the case of the TNIV.

I am very interested to see how this new translation will come out with respect to gender-inclusivity. The NIV charter requires the translators to update the text as a reflection of developments in English. Once again, I have no empirical data on this, but gender-inclusivity idiom (e.g. the use of “they” as a singular pronoun of generic gender) appears to be dominant in much of the United States, if not the whole English-speaking world. The NIV translators seem to share this opinion, given that they have worked in accord with that assumption twice previously. So the question is: will they attempt again to market a gender-inclusive NIV, or will they shrink away from the controversial topic?

Gender Inclusivity Coda

Monday, August 17th, 2009

In the course of the last week, I’ve had the opportunity to read and learn a fair amount about the concept of gender-inclusive language in Bible translation. Here are a few references:

Ideology and Translation

Monday, August 17th, 2009

In my disagreement about gender-inclusive language with Dr. Craig Carter, I have found one sure point of agreement between the two of us: ideology should not govern the translation of the Bible. The problem we have encountered is that we cannot agree on what constitutes ideology in translation. Carter has posted some additional thoughts under the title “Inclusive Language and the Doctrine of the Trinity.” Here follows a general response to Carter’s argument. My primary purpose in this post is not to argue for gender-inclusive idiom per se (I don’t as yet have a fully-formed opinion on the matter), but to come to the defense of translators who employ such language and have consequently been portrayed by Carter as compromised by “egalitarian ideology.”

Defining the Issue

First of all, a discussion of gender-inclusive idiom in English (e.g. the use of “they” as a generic singular pronoun) must be rightly divided from other issues. Translators are concerned with communication. The reasons for a change in a language’s idiom are not material to the practice of translation, whether or not said changes are wholly or partly the result of an ideological movement to which the translator objects. In the context of Carter’s posts, this ideological movement is purportedly feminism. I will accept for the sake of argument that feminism is indeed the engine behind the rise of gender-inclusive pronouns in English (though I think it is a claim wanting evidence), but even then I think that the concerns with feminism are irrelevant.

Another area where careful delineation of the issues is in the doctrine of the Trinity (per Carter’s post) or any other theological matter. If there is indeed a movement to remove the use of gendered pronouns (“he”) and nouns (“father,” “son”) from describing God, it is a separate issue from gender-inclusive idiom. The former deals with the proper address and nature of God, while the latter deals with how English-speakers indicate a generic individual. Or: the former is a matter of theology and the latter is a matter of conventions.

Carter’s initial assertion was that translators who use gender-inclusive pronouns are motivated by ideology. I believe that this charge was based on a confusion between gender-inclusive idiom and other issues relating to gender. In other words, gender-inclusive idiom may be required by the task of translating the Bible into modern English and need not be motivated by ideology at all. Indeed, to demand that gender-inclusive language not be used is itself a form of ideology.

Contemporary Idiom and Intelligibility

One of Carter’s chief arguments against updating translations to reflect new gender idiom is that the old translations are still intelligible to most readers. That may or may not be true in every case (though it stands to reason the deprecated forms will become less intelligible as they fall out of use). As an example, Carter provides Matthew 16:24

If anyone wants to follow me, he must deny himself and take up his cross and follow me.

I am inclined to agree that most modern readers could understand that “he” in this context is generic and can refer to women as well as men. I would go so far as to suggest that the average modern English speaker could even make sense of the Episcopal Church’s Rite 1:

It is very meet, right, and our bounden duty, that we should at all times, and in all places, give thanks unto thee, O Lord, holy Father, almighty, everlasting God.

But the question is: is mere intelligibility the goal of translation? It seems to me that translations ought to target the contemporary and natural speech of those who will be hearing the result. Sure, we could go back to thees and thous (and by so doing relieve much confusion about singular v. plural in the New Testament), but that would not be the sort of translation which would be most natural for modern readers. If Carter wants to fight ideology through translation, he may have to accept a stilted, dated translation.

Diachronic Study and Style

Carter’s must unusual argument comes in defense of Milton, Shakespeare, and the like:

The problem is that, once the concession is made that traditional language is exclusive of women (which is never was), then the integrity and credibility of all the texts of Western civilization are placed in question. Since everything prior to 1970 uses “non-inclusive language,” everything is open to suspicion of being “patriarchial” and thus non-binding. This applies to the concept of classic texts in literature, law, philosophy and history, as well as all theological texts up to and including Holy Scripture itself.

Thankfully this is not now nor has it ever been the case. We can track the changes in language through diachronic study. In so doing we can know how to interpret literature based on its context. The use of “he” as a generic pronoun is not a marker of patriarchy but of an older idiom for a generic person. Carter himself admitted that modern readers could tell the difference (see above). I find it particularly ironic that he mentions Holy Scripture as a potential victim of this misunderstanding, seeing as this could be easily remedied by updating translations to use the new gender-inclusive idiom!

Changes in English today are not going to destroy our appreciation of ancient English literature. It is doing just fine, thanks to diachronic study. Indeed, it has survived many changes in idiom. We can safely update our translations to use contemporary idiom without undermining our own literary foundations.

I should also note a criticism of Carter’s that the new idioms do not sound good. Style is of course in the ear and on the tongue of the beholder. We all must from time to time accept that changes in language will make our favorite stylistic flourishes passe while newer, distasteful elements will achieve hegemony. That is, contemporary English style may change without our approval or consent.

Conclusion

Carter’s treatment of the topic of gender-inclusivity utilizes arguments from many fronts: sociology, theology, literacy, literary history, and style. However, none of his arguments against the use of gender-inclusive language in Bible translations stand on their own merits. Moreover, Carter’s war on inclusive language appears to be motivated by the desire to oppose liberalism and not the desire to produce accurate, modern Bible translations. Bible translators who use gender-inclusive language out of a desire to produce good translations should not be called ideologues for failing to comply with Carter’s own ideology.

Committee Translations

Tuesday, August 11th, 2009

All of the principle translations of the Bible into English are done by translation committees. There are some notable exceptions, of course, including the Message, the Living Bible, Weymouth, Philips, etc. However, these are considered secondary due to their being completed by an individual. Moreover, I have sensed a general sentiment that such translations by individuals are not considered as trustworthy as committee translations because it is thought that personal bias would be allowed to shine through in an individual’s work. A committee is also useful for imposing a standard style on a work which is actually composed by many different scholars. I am sure there are more reasons for the committee trend.

What I began noticing in college is that committee translations are pretty rare outside of the Bible (I cannot think of one off the top of my head). Instead, translations are typically done by an individual or small team. This is the case for works of antiquity, textbooks, novels, etc. Why is it that committees are so common for biblical translation but so uncommon for everything else? Is the quality of the end product affected by the decision to use a committee or not?

Gender Inclusivity

Monday, August 10th, 2009

Craig Carter and I are having a discussion about gender-inclusive language in Bible translations. To summarize: Craig thinks that translators who use gender-inclusive language are doing so for invalid ideological (namely feminist) purposes; I think such translators are doing their best to produce an accurate, contemporary translation into the ever-changing English language.

I have absolutely no evidence available to argue that the generic/inclusive masculine in English is falling out of style, so I am not sure how necessary gender-inclusive language is for modern English translations. My anecdotal experience tells me that gender inclusive language is becoming necessary. Craig’s anecdotal experience tells him just the opposite. In other words, we have reached an impasse. Does anyone have statistical evidence on this matter?