Legacy texts or e-commentaries?

Because designers of file formats and Bible software that uses them are print-centric in their thinking I seem to face a choice in envisaging a new generation e-commentary. Either I produce something that accepts the traditional limitations of print, but which would work within Bible software and so be available to people when and where they need it. OR I produce a genuinely electronic commentary, with links and media (pictures, video and sound), but that must be accessed apart from the Bible study tool.

In my previous post I expressed some frustration at the lack of tools for conveniently preparing a text marked up in OSIS (Open Scripture Information Standard). In this post I will look at OSIS from a different prespective. I am discovering that, as well as the practical difficulties of producing well-formed valid XML, I have  another deeper problem. OSIS is designed for marking up Bible and related texts, but it is designed for and from the print age. Its mentality is that of words written on a page. It is therefore quite good at rendering manuscript texts (after all print largely mimics manuscript). It is not good at producing e-texts.

To make matters worse, different front end1 designers have different ideas about the importance of non-textual elements (like figures)2 or hypertextual elements (most notably links). Among those who can import OSIS text (often adapted into Sword modules) some support figures (though the ability to size and place images in text seem to be rudimentary), others support links – though learning the arcane methods reguired is problematic and on occasions the results are bizzare (Xiphos3 may jump to an internal link in a commentary module, but seems to reset the Bible text displayed to the start of Revelation each time, not quite the effect I am after!

At present it looks as if I have the choice of aiming for commentary that is as print-like as possible, producing such a print-like commentary augumented by links to Internet based materials outside the commentary itself, or producing an e-commentary that does not work inside Bible software.

If anyone can suggest ways to cut the Gordian Knot, or even a decent compromise, would deserve and recieve my deep gratitude!


  1. Think Bible software or websites that allow you to read and study the Bible. []
  2. Photos, maps, diagrams, charts… []
  3. One of the most developed Crosswire front ends. []