Rob's Open Scripture Blog

Audio copyrights

2010-10-09T15:25:00.000+13:00

I know this isn't Scripture (although many religious recordings will be included), but see this article about the negative effects of extended copyrights on historic audio at OSNews.

More on translation difficulties

2010-07-06T23:07:00.000+12:00

Eddie Arthur's Kouya Chronicle pointed me to this article about some of the difficulties in the task of Bible translation.

It mentions how that translating from one language to another is a task of compromise with opposing ideals causing translators difficulty and frustration. That's certainly been my experience, and it's part of the reason why there's no perfect Bible translation. And that in turn is part of the reason why there are so many different English Bible translations -- every one has to apply their own set of predefined weightings in making the compromises which translation of necessity demands due to linguistic and cultural mismatches.

Many Bible translations are forced to make middle-of-the-road decisions so as to ensure that the final product is marketable to the Christian public. The Open English Translation of the Bible (OET) handles this in a different way -- it consists of a collection of four different linked versions each of which is able to make some more extreme decisions than most traditional translations, yet the compromises between things like accuracy and naturalness are balanced across the entire set. Thus, although compromised like every modern English Bible translation has to be, it tries to make the compromises more open and exposed to the reader.

The "Old" and "New" Testaments

2010-06-27T18:46:00.000+12:00

Over a few years now, I've come to dislike the names Old Testament and New Testament. They seem inaccurate and misleading, perhaps like my old socks (full of holes and now discarded in the rubbish bag) and my new socks (which completely replaced the old ones). Or would my jeans be a better example? The new ones I wear when I'm going out -- the old faded ones are still useful, but only for working out in the garden. Old and new can mean many things.

So is the Old Testament, broken and discarded completely, or just faded but still there in the background, or is this a wrong picture completely? Maybe it means just older in age, compared to the newer one? So now we come to complex theological questions including whether or not the Mosaic law has been "fulfilled", and many other thorny issues which I really don't want to start into here.

And then there's the issue of what does the word testament mean to a modern reader (outside of the Bible context). To me, the only association which comes to mind is to do with the legal jargon of wills. And I don't think the main messages of the two sections have a lot in common with a will! Perhaps covenant, contract, agreement, or promise might substitute better here to help the modern reader???

All I want to really say in this blog, is that the traditional names can be misleading to Christians themselves, and can also be problematic to those explaining Christianity to people of Jewish or Israeli heritage.

So, I want to change the terminology for the OET (Open English Translation of the Bible). So here's some of my argument in question/answer format:

Do we need/want a separation between these two parts of the Christian Bible? Yes, there are good reasons to do with history, age (a gap of several hundred years between their authorships), and contents which make it seem sensible to maintain the divisions.
Should we stick with the "old" and "new" traditions? No, as shown above they can be misleading and even problematic.
Should we stick with the "testament" tradition? No, this is an outdated word in my mind -- meaningless to most people and misleading to others.
What would be the requirements for a new names? We need one term for each of the Old and New Testaments. The two terms should preferably have some meaningful relationship or connection to each other. They should also be relatively simple, i.e., not long complex names, but rather concise and helpful. They should be easily understandable to modern readers and also it should be recognisable (in the context of the major Bible sections) what they are referring to (even though they won't, of course, be familiar at first).
Of course, no heading can ever fully summarise a long section. So unfortunately some dissatisfaction must be expected, because there are so many important topic areas in the Scriptures which we can't totally represent in the section names.
What would we replace them with then? Yes, this is the big question in my mind, so I'll break my answer into two paragraphs:

Old Testament: The suggestions that first come to mind are Hebrew Scriptures and Jewish Scriptures. Technically, it's not all Hebrew -- there's some smaller Aramaic sections in there. So Jewish Scriptures seems to fit quite well, and even as a side-effect acknowledges how much Christians have inherited from the Jewish people.

New Testament: Of course, this was mostly written by Jews as well! We could maybe call it the Christian Scriptures, but that might imply that the Old Testament is not part of the Christian Scriptures. Besides, I'm heading away from the Greek term Christ/Kristos because many readers don't even realise that the term has a meaning. (Some have even thought it to be Jesus' surname). But we can't call it the Messianic Scriptures because there are many messianic prophecies in the Old Testament. Greek Scriptures might seem like the appropriate counterpart to Hebrew Scriptures, but I'm not sure I favour that so much either.

So all that thinking aloud didn't get me to a solution. So we have to look in another direction. Another aspect of the Bible is that large portions of both the Old and New Testaments are historic narratives. I think it's not a bad thing to emphasise that aspect of the Scriptures. So how about using "account(s)" to describe them. The New Testament could be The Messiah Accounts; the Old The Hebrew Accounts (being largely about the rise and fortunes of the Hebrew nation).

What do you think? Just follow the familiar tradition? Don't like these suggestions? Want to offer better ones? Use the comments to tell me what you think.

One advantage of a free (no cost) Bible translation is that we don't have to worry about marketing -- being concerned that people won't buy it if we make changes. I think it's a refreshing opportunity to break with tradition and make some needed improvements.

Free Bible commentary

2010-06-23T08:29:00.000+12:00

I only have time to write a short note here today, but I just discovered Dr. Bob Utley's Free Bible Commentary. I can't say anything about the content yet, except to say that it looks like he's done a lot of work. Worth investigating!

Summary of OET versions

2010-06-16T12:18:00.000+12:00

Well now that all of the different versions of the Open English Translation of the Bible (OET) have been announced, it's time for a brief summary of them:

The Literal Version
Closely follows the Hebrew and Greek scriptures, so the sentences are English, but still using the original vocabulary and idiom as much as possible. Extensive notes about variants in the originals.
The Readers' Version
An up-to-date free translation that's easy to read. As few distracting notes as possible. Designed for reading Bible stories easily and in full context.
The Study Version
A less free translation but with many helpful notes and cross-references. This is the one to preach from and to memorise segments from.
The Extended Version
An extended text of the Study Version, with many more notes and details also added in. Designed for lecturers and Bible translators.

These different versions are designed to be used to complement each other, especially in linked media like the Internet where two or more of them could scroll together.

The links above focus on the differences between the different versions of the OET. The following list (from here) focuses on the common features:

The misleading terminology Old Testament and New Testament will NOT be used
The terminology Major Prophets and Minor Prophets is also misleading to many readers and will NOT be used
Traditional chapter and verse numbers will be there, but will be downplayed to discourage their use
Segments which are not included in the most ancient manuscripts will be removed from the inline text
Wherever section headings are used (all but the Literal Version), they will be typeset/displayed in such a way so as not to interrupt the flow of the actual Scripture text
The so-called apocryphal books will be included in the OET (with a section name yet to be determined)
Eventually, the order that the books will be presented will be changed from the traditional English Protestant order
Each book will have an individual version number, and each major release will also have an overall version number
Each version will be available in multiple formats for download, including text, OpenOffice (ODF), and PDF files (both of individual books and of entire versions), USFM files, and OSIS files, and Epub electronic book files
It will be released under a licence that both enables and encourages others to use and build upon this work. (Most likely this will be a Creative Commons BY-SA or BY licence, but other content licences are also being considered, even Public Domain.)

I've never seen a Bible translation project that's attempted to do things this way. Apart from wanting to make a good English Bible translation that's both open and free, it's largely an attempt to design an English translation that connects the reader with the original texts; helping them to understand where our Bible come from and some of the decisions that are made for them by the translators.

And yes, it is a very ambitious goal -- totally impossible without God's blessing! So come on volunteers...

What do we translate from?

2010-06-15T18:21:00.000+12:00

A very interesting article here (from Biblical Archeology Review) explains some of the difficulties in interpreting the source texts of the Jewish Scriptures (Old Testament).

Many people don't understand that some differences in the various English translations go all the way back to trying to interpret whether a certain segment of text was in the original and accidentally not transferred into a new copy, or whether it was not in the original but deliberately added to a later copy (perhaps as a "helpful" explanation). It's as much art as science in trying to determine such things, but wonderful that we have such good sources of quite ancient material available.

The article doesn't mention that most of the text between the different Hebrew manuscripts agrees very well. (Of course, the Septuagint is a translation into another language, and that's a whole different matter!)

And it's encouraging also that these discrepancies don't seriously affect any major Christian doctrines, because most of them concern relatively minor issues.

[The article doesn't mention it, but seeing how much more we know since the Dead Sea Scrolls were discovered beginning in the late 1940s kind of weakens any "King James version only" argument.]

OET Extended Version

2010-06-14T10:09:00.000+12:00

Ok, this is definitely the last one!!! It comes out of my desire to help provide freely available resources for those wanting to create free Bible translations for their language or area.

The Open English Translation of the Bible (OET) Extended Version (OET-EV), closely follows the text of the Study Version, so this one is really a derived version, not a totally separate text. However it makes a number of changes (mostly additions):

The divine name (tetragrammaton) will be rendered as YHWH (since the Extended Version is intended for technical people)
There will extensive notes on variants in the original manuscripts (similar to the Literal Version)
There will be extra grammatical notes, including the explicit marking of singular/dual/plural and other grammatical features brought through from the original languages
Ambiguities in interpreting the original texts will be highlighted and multiple renderings offered
Extra exegetical and translation notes will be added

So you can see that the text of the Study Version becomes augmented with a lot of extra information for translators and serious students. The final detailed specifications and a small sample text should eventually be available here.

So that finishes up the round-up of OET versions: the Literal Version, the Readers' Version, the Study Version and this, the Extended Version. They are intentionally designed to be used in parallel in order to give the interested student a broader perspective of the intricacies of God's written word.

Now, we just have to get recruiting some help to get the website going, and then we'll be working on recruiting translation teams.

OET Study Version

2010-06-13T14:55:00.000+12:00

The Study Version (OET-SV) is the third version of the Open English Translation of the Bible (OET). Again, the text is quite different from the previously announced two versions, and the main distinctives are:

It's aimed at preachers / students who want to study the text carefully in English
It will attempt to give a readable English text with normal contemporary English punctuation
Additions to the text which are necessary to translate the meaning will be marked
The divine name (tetragrammaton) will be rendered as Yahweh
People and place names will be transliterated more accurately, e.g., Yonah instead of Jonah, Yesous instead of Jesus, but the traditional spelling will be added in parenthesis where the name is first used in any book
The word God will be capitalised where appropriate, but other references, e.g., the father, the son, will not be capitalised
Paragraph breaks and section headings will be added to the text, along with indentations for poetry and quotations and a method of explicitly marking Hebrew parallelism
Modern measurements will be used in the text but the original measurements will also be noted
There will extensive cross-referencing and footnotes, including notes on the more important variants in the ancient manuscripts
It is hoped that the web-based publication will also provide live links to the OET-LV.

This is intended to be a version that you would be confident to preach or teach from and to recommend to your Bible students. Again, the final (more detailed) specifications and a small sample text should eventually be available here.

Ok, now, surely there can't be (m)any more OET versions? The next blog will tell...

OET Readers' Version

2010-06-12T15:04:00.000+12:00

Today I am revealing the initial design plans for the second version of the Open English Translation (OET), the Readers' Version. This is pretty-much totally different from the Literal Version. Here are some of the main features of the OET-RV:

It will attempt to give an easily-readable, natural English text with normal contemporary English punctuation
It will attempt to replace Christian jargon with language that is more likely to be found in modern newspapers, magazines, and books
Additions to the text which are necessary to translate the meaning will not be marked in any special way
The divine name will be rendered as Yahweh
Traditional English spellings will be used for people and place names
The word God will be capitalised where appropriate, but other references, e.g., the father, the son, will not be capitalised
Paragraph breaks will be added to the text, along with indentations for poetry and quotations
Section headings will be added but typeset/displayed in such a way so as not to interrupt the flow of the actual Scripture text
Traditional chapter and verse numbers will be downplayed, as in all OET versions
Only modern measurements will be used (the original measurements will not be included)
There will be a minimum of footnotes
The OET-RV is aimed at readers (including second-language English readers) who want to easily read the text and understand the overall message
It is hoped that the web-based publication will also provide live links to the OET-LV.

The final specifications and a small sample text should eventually be available here.

So hopefully you can already guess where I'm going with the OET. So far I've announced the Literal Version and the Readers' version -- quite different versions which are complementary parts of the OET translation. It is intended that they be viewable together, especially on media where they can scroll and be linked together. One is easy to read; the other choppy and unnatural but helping the Bible student to understand where the smooth English of the Readers' Version has come from.

There's a big debate these days about the most useful kind of English Bible translation. Different publishers try to position their translations at different spots in the market. The OET tries to solve the dilemma with a different approach: multiple linked versions all under the banner of the Open English Translation.

And best of it, it's planned that all of this be made available under a very generous free licence (details not decided yet) to enable and encourage others to use and build upon this work.

Beaten again

2010-06-03T21:58:00.000+12:00

I just can't believe this -- everyone is stealing my ideas! Actually, I'm happy, because I'm finding so many other people already thinking in similar ways to me. Knowing that great minds think alike, I figure that... well, I'll leave it to you to figure!

Yesterday, I included a link to John Dyer's writeup about chapters and verses. A couple of his links pointed to The Books of the Bible project by the International Bible Society (IBS) which I just read about today. Apparently IBS assembled a group in 2003 to explore a new visual presentation of the Bible. They used Today's New International Version (TNIV) as their text.

According to the FAQ list, they relegated chapter and verse numbers to a range down at the bottom of the printed page. Even more amazingly, they dared to change the order of the books, changed the traditional Old Testament to First Testament, and got rid of most (or all?) section headings.

These were all things that I had planned for the Open English Translation of the Bible (OET):

greatly downplay chapter and verse numbers,
downplay section headings (by not allowing them to actually interrupt the text),
change the Old Testament, New Testament terminology, and
change the order (and by combining, even the number) of books.

(I also plan a number of other distinctives for the OET, but I'll resist the urge to list them all here so as not to clutter this blog.)

So yes, it was very encouraging for me to see that an organisation like IBS has already experimented with these issues. Maybe some of my ideas aren't so far off the wall after all!

I'm sure that tradition has kept the sales of something this different pretty small, but I'll certainly have to order a copy. There's sample PDFs for download here. I think I might just print one or two and see how they look.

P.S. Here's a link to another excellent little write-up that John also referred to.

More on chapters and verses

2010-06-03T09:34:00.000+12:00

Last week when I started writing about my design of the Open English Translation (OET), I alluded to the fact that chapter and verse numbers would be downplayed in all OET versions.

I planned to write more about this later in the month (and still hope to), but today I came across another blog with a similar theme here. So again, it's encouraging to see that some others are seeing some of the same drawbacks to making this reference system so prominent in our Bibles. (Of course, there are many positive features also.)

So just another quick prelude to my forthcoming writeup: The OET will include book, chapter and verse references so that it can be used by traditional software and webware and people looking for specific passages, but the printed or displayed versions will go to a lot of effort to downplay all those distracting numbers.

By the way, the same goes for section headings, but more on that another time...

OET Literal Version

2010-05-25T14:42:00.000+12:00

Most Bible translations consist of only one version, but a number of editions, perhaps with British vs. American spellings, with or without cross-references or study notes, mini-concordance, etc. However, the Open English Translation (OET) of the Bible comes from the beginning with more than one version with different aims, but expected to be used together just like a modern builder might use a nail-gun for many tasks, but pick up his hammer for others.

The first OET version I want to introduce is the Literal Version (OET-LV). Here's an initial list of some of the Literal Version features:

It will attempt to follow the original (Hebrew and Greek) Scriptures as closely as possible (at the expense of sounding "wooden" in English)
This means being as literal as possible -- trying to match pretty much word-for-word (thus idioms won't be adjusted)
Any non-trivial words that must be added to the English for understanding will be clearly marked as additions
Every attempt will be made to make the English glosses consistent (at least for the primary meanings of words)
Primary and extended meanings of words will be marked using slashes, e.g., (מַלְאָךְ) messenger/angel
Slashes may also be used to denote an English range of meaning that's perhaps different from the word in the original languages, e.g., sorrow/mourning
Underscores may be used to join English words coming from a single source language word, e.g., cause_to_stumble, except that small grammatical features like articles, prepositions, and conjunctions maybe be exempted from this
Where it seems to critically affect the meaning, grammatical features that are not normally in English (such as marking gender or distinguishing between you singular and plural) will be marked
The divine name will simply be rendered as YHWH
People and place names will be transliterated more accurately, e.g., Yonah instead of Jonah, Yesous instead of Jesus (but not going to the trouble of using additional markings to distinguish the long and short vowels, etc.)
Only proper nouns (and sentence beginnings) will be capitalised in the text, thus there will be no God only god
The translation will be rendered into English sentence by sentence (with ambiguities marked in footnotes), i.e., the 19th sentence of the English New Testament should match the 19th sentence of the Greek.
There will be no section headers or paragraph markings -- it will generally be displayed by sentence (as traditional chapter and verse numbers will be downplayed in all OET versions)
Only original measurements will be used, e.g., cubits not metres.
There will be extensive footnotes about variants (and missing or unclear sections) in the early manuscripts
The OET-LV is aimed at readers and students who don't read the original languages themselves, but want to get a good idea of what they actually say
It is hoped that the web-based publication can also provide live links to facsimiles of the original documents.

A very rough sample of a small book can be seen here: Jonah

Please note your suggested improvements in the comments -- I want to hear your ideas for improvements.

So hopefully you can see that the OET-LV is aimed to give pastors and all those studying the English Bible relatively good access to the original texts, even if they are impeded by not being able to read the original languages.

Introduction to the Open English Translation

2010-05-24T16:30:00.000+12:00

I've been thinking for a loooong time about starting a new English Bible translation (unashamedly inspired by the public domain World English Bible (WEB) of Michael Paul Johnson and team). After much searching and pondering, I've come up with the name: Open English Translation (OET) of the Bible.

Open (unashamedly inspired by Open Source software) expresses my desire to make it freely available for others to use or adapt in any way. I haven't decided on a licence yet, so feel free to make suggestions. I'm also wanting to make it open in the sense of open for others to join in and help with (but that doesn't mean that it would be open to everyone -- just those who show a genuine interest and ability). As mentioned in prior blogs, there's a number of others way ahead of me in developing the necessary (web) software tools for that kind of project.

English because it'll be an English translation. (It seems a little ethnocentric to me to leave the language qualifier out of the title, although it is true that in most cases that language of the title itself indicates the language of the translation.)

Translation just to remind readers/users that it is indeed just a translation of the original Scriptures. (Again it seems a little deficient to me if a book called something like The Holy Bible doesn't clearly remind its readers that it's not the original.)

I'll try to progressively blog about various aspects of the OET over the next few weeks.

A sad scenario

2010-05-21T08:55:00.000+12:00

I second the story at Distant Shores Media. We hit the same problem with our experience in Asia -- the local church leaders and others wanted to take popular Christian resources and adapt them for their use. In the situation that we were in, it was often more to do with Christian songs and music rather than the Bible because the Scriptures were still in the process of being translated and checked.

The pastors' cooperative organisation didn't have the resources to seek (or pay for) the international permissions to use and translate or adapt these materials. So either they don't use them at all, or else they may feel pressured to go ahead and use them without the permissions. Either scenario sadly limits the ministry of the indigenous churches.

Thumbs up to the slowly increasing number of people and ministries who are forgoing the urge to control and profit from their productions (often already paid for by offerings, donations, or other funds) and who are making their materials available for the rapidly growing church in the third world to make full use of. I'm hoping one day to be able to highlight them at Freely-Given.org.

Open discipleship resources

2010-05-20T10:21:00.000+12:00

I was just thinking about this topic myself yesterday, and today Tim at Distant Shores Media (DSM) has written another good blog entry.

It's also interesting that DSM list The Open Bible Translation as one of their (future?) Door43 projects. Very similar name to my Open English Translation (OET) that I have started work on, although I'm yet to publish any details (apart from the brief mention here).

So why not just combine with one of the several open translations mentioned on this and previous blogs? Yes, I'd like to in terms of sharing resources, but it would depend on agreeing on a common philosophy of translation. That, of course, depends on your target audience amongst other many factors. I guess I need to get into gear and start placing my thoughts into a public forum, but I'm in a place of major job decisions and transition over the next few weeks so it won't likely happen before late June at the earliest. :(

Holman Christian Standard Bible

2010-05-18T18:18:00.000+12:00

I was already aware that the NET Bible was developed because Bible.org was wanting to publish free Bible studies on the Internet, and had problems getting copyright permissions. They put it like this in their preface:

Bible.org’s ministry objective is to be used by God to mature Christians worldwide. To accomplish this we needed to quote a modern Bible translation in the production of thousands of trustworthy Bible Study resources that could be offered on the Internet for free. We predicted in 1995 that the number of Bible verses quoted in these studies would soon surpass available legal permission limits. We tried for a year, but could not obtain the necessary permissions. Lack of a legal ability to quote the Bible online makes online Bible studies impossible and threatened bible.org’s “Ministry First” model. Quite simply the only way we could secure permission to quote a modern Bible was to sponsor a new translation – the NET Bible. We now want to ensure that other ministries and authors don’t experience the same roadblocks. The NET Bible is not just for bible.org, but for everyone.

(There's also more written here.)

But I was surprised to learn today that the Holman Christian Standard Bible was also published partly for reasons relating to copyright as explained here:

In 1998 the people at Broadman & Holman were seeking to buy the copyright of some already-existing Bible version for use in their publishing projects. For many years they had been using the New International Version, but this was not convenient for them, because the copyright holder of the NIV (the International Bible Society) had sold exclusive North American publishing rights for their translation to the Zondervan corporation in Grand Rapids, and Zondervan would allow other publishers to use the NIV only under some very expensive and restrictive license agreements.

So one just can't help wondering how many Christian ministries around the world continue to be frustrated in their outreaches and discipleship programs because of copyrights on Bibles. Personally, I think the world is ripe for a new approach.

The M108 project

2010-05-06T10:24:00.000+12:00

Ryan Cartwright, a web developer / IT consultant in the UK, writes in his Crimperman blog about a new project, tentatively called m108 (from Matthew 10:8 "...you received freely, so freely give."). He's started a discussion about how to best encourage Christians to make music, video, art, literature, etc. freely available on the Internet.

So far he seems to have attracted about just a few people who've expressed some interest in his ideas. Obviously, you need to have a much higher profile way of making your ideas and site known in order to attract sufficient interest to really get the ball rolling. It seems you need a critical mass of several hundreds of people to even get started; several thousands to make even a small ripple in the pond. But maybe one high-profile artist getting involved could have a greater effect than even tens of thousands of unknown individuals???

That's why I've dreamed a lot (esp. last year) about starting a high-profile lobbying organisation called FreelyGiven.org or something similar, to seek sponsorship in order to personally contact or even visit high profile Christian artists and ministries in order to encourage them to make more of their output available freely to the church world wide (esp. the rapidly growing church in developing countries). But alas, too many things to do, and only one lifetime to do it in...

Scripture Tools for Every Pastor (STEP)

2010-04-22T13:52:00.000+12:00

Tyndale House has an interesting project to provide Bible-study tools for pastors. See the writeup here, and also here. Looks very interesting and encouraging. Now if we could only use or extend it for Bible translation...

The wheels keep turning

2010-04-15T08:05:00.000+12:00

Another long, but insightful blog by Tim over at Distant Shores Media (DSM) again explains how copyrights of Christian materials can limit discipleship. He also talks about a forthcoming Open Discipleship License -- it's not completely clear but it sounds like something that DSM is developing as a niche alternative to Creative Commons licensing.

Trickles turn into rivers

2010-04-12T15:22:00.000+12:00

Kudos to programmer Michael Paul Johnson for realising many years ago that Bible copyrights impede a lot of good, constructive Christian activities in the digital/Internet age, and for adapting and editing the now out-of-copyright American Standard Version (ASV) of 1901 into the World English Bible (WEB), which is given as a public domain gift to the world.

I came across it a couple of years back as I wrestled with similar concerns, and considered joining MPJ's effort. But although we have many overlapping interests, I was aiming at a different audience, and decided to move towards a similar project, but named The Open English Translation (OET) Bible. Imitation being the best form of flattery, I have also started by updating English words in the ASV (e.g., seeketh -> seeks, prayest -> pray) and making some other automated changes. In my spare time for the last few weeks, I have been learning the Pinax/Django platform to try to find an effective way to host a Bible editing wiki-type site.

Then last week, I came across The Open English Bible. It starts with the Twentieth Century New Testament (which I had never heard of) and does something similar. Obviously, with a website already up, and a preview release of Mark already available, lawyer Russell Allen is already way ahead of me! (It has a Creative Commons Attribution licence and like me, he's also a Python man.)

I'm sure there's others too out there -- the Net is a BIG place! I know that Door43 is also trying to do something similar.

So is this encouraging or discouraging? The trickle turns to a stream. Might it turn into a river? At least I was probably on to a good thing, even if I'm now just one of many. At the risk of stubbornly continuing with the individualistic "do your own thing anyway" philosophy, I think I'll continue dreaming and slowly plodding forward for now. I'll try to start writing more about my OET intentions soon...

Added P.S.: I knew there was another one I should have mentioned. Kata Biblon (meaning: according to the book) has set up the Wiki English Translation (WET), also taking inspiration from MPJ and based on the WEB. Thomas Moore has already done a LOT of work to get this up and going.

Christianity and Copyright

2010-04-10T15:03:00.000+12:00

I don't have time to craft my own blogs yet, I guess because I'm still spending time on the net learning what others are up to. And I keep discovering more people with overlapping ideas. Here's another at Nathan Smith's blog.

A thought-provoking lecture

2010-03-15T10:41:00.000+13:00

As well as my interest in the Bible, I'm also a computer "geek", and I was pleased to find a link on OSNews (which is a site about computer operating systems that I read) to an excellent lecture about copyright in the digital world from Harvard law Professor Lawrence Lessig. The link is here, and I too highly recommend that anyone who is seriously interested in this important topic view the 50-minute lecture.

Well-articulated thoughts

2010-02-09T20:39:00.000+13:00

It takes time to craft a good piece of text, and the days and weeks are rushing by (as we still work on getting ourselves fully organised here) and this blog isn't being written.

But fortunately, someone else is writing some good thought-provoking articles while I'm too busy. So, for now, in lieu of any good write-ups here, I recommend reading some of the blogs at Distant Shores Media.

Another online resource

2009-12-30T14:09:00.000+13:00

I also discovered the Open Text site. It kind of gives the impression that it hasn't been touched for a few years (and their discussion forum link seems to be broken) but it seemed they were doing some good work marking and displaying clauses in the Greek New Testament. I didn't see a description of their file format or where to download their work but perhaps it's in there somewhere? Or maybe this is just an archive site and they've moved onto something better somewhere else?

Exciting on-line resources

2009-12-29T07:31:00.000+13:00

I was very pleased to find out about the Open Scriptures group on the Internet. They have a website at OpenScriptures.org but nothing posted there since July. The current action seems to be over in GoogleGroups (note the hyphen in that URL). They've also had data and code in GoogleCode but seem to be moving to GitHub now (hyphen gone again).

It was great to listen to some of this group (and many other speakers) at the BibleTech site. I've learnt a lot from listening to the 2008 and 2009 talks there (scroll down the page).

It's exciting to find a group that seem to have many of the same interests, particularly in working towards providing free and open Scriptures (original languages and translations), along with software and webware tools that will use standardized interfaces to make it easier for programmers and others.

I'm still learning about their goals and projects, but I'm hoping that I can find something to do to help them by around the second quarter of 2010. There seem to be four main areas of work:

Overall planning and design, especially XML formats
Preparing and checking/proof-reading data files (HUGE job)
Writing utilities to convert data files between various formats
Designing and writing software to access and use the available data.

Of course, my specialty interest is minority-language Bible translation, so I'm hoping to eventually get to #4 above as we consider our experience in a translation project and how computer tools might have better assisted us.

Site available

2009-12-20T07:50:00.001+13:00

We are in the process of moving back into our home in New Zealand after spending most of the last 21 years overseas. I am hoping to set up a small Ubuntu server there so I can host a few of my own small sites.

Meanwhile I have bought Freely-Given.org. It only has an ugly placeholder page at the moment, but I'm hoping to set up a site there. I want to research and evaluate free Biblical materials available on the Internet and for mobile devices, and to publish the links and my evaluations on the site. My particular special interests are tools for Bible translators along with original Scripture resources and English translations, but I'd also like to extend it to other modern languages and other Christian resources.

I envisage a site structured by type of resource and by language, and for each entry to contain: the link to the resource, a list of computing platforms that it runs on, any additional technical information which is known (such as which language it's written in), a rating for usefulness, a rating for openness (e.g., is the source code/data available), and a very brief overview/evaluation which links down to the full review.

I'm not a site designer so I'd love help with the artistic side of the site, and I'm looking towards using some kind of framework to allow rapid development of wiki type features, etc. Because I'm a Python lover I'm investigating Django first, but I'm really jumping in over my head here. I really want to spend most of the time listing and evaluating the materials, not actually developing the site. So if anyone wants to help me out with this, I'd be very grateful.

Introduction

2009-12-13T13:17:00.000+13:00

I am a linguist / Bible translator who is just helping a team finish a Scripture selection (New Testament plus 8% of the Old Testament) ready for publication for a cultural community in Asia. It's taken us over twenty years to do this, including learning the language (plus a couple of the major languages in the country), establishing a literacy program, training local (mother-tongue) translators, establishing a Scripture promotion program, etc., etc.

Now I'm starting this new blog to pursue an interest in making more Biblical materials more available to students of the Scriptures all over the world. I'm concerned that it often seems that the Western countries are the "gate-keepers" of the original (Hebrew and Greek) texts, as well as the reputable English translations that local translators often want to use as resources for study and for translating into their own languages. Often copyrights or expensive charges prevent students from the rest of the world from having legal access to these helpful materials.

I think there's a growing (but still very small) number of people who recognize this problem and who, rather than focussing on the negative aspects of this discussion, want to take positive action to make quality Bible resource materials more freely available.

Hopefully you'll join me in thinking through some of these issues over the next weeks and months, and coming up with an action plan or how we (yes, me and YOU) can make a useful contribution. I guess the steps might be: 1/ try to define the problem more clearly, 2/ identify what Bible study resources are currently freely available, 3/identify what resources still need to be made available, 4/ plan how this might be achieved (this involves both data resources and software resources), 5/ see which part of this picture we might be able to contribute something tangible to. Please do contribute your comments, suggestions, objections, and anything else that will spur on this area of research.