David Cox's How to create an e-Sword Bible modules

 Overview  

What I will do on this page is break down the process into a number of phases. Please note that in the e-Sword structure, a Bible file is a MS Access database ending in the extension of *.bbl. It basically has a record in this database per verse in the whole Bible, with fields for book, chapter, and verse.

Format of a BBL (e-Sword Bible File Format)

A BBL is a simple Microsoft Access file format with the extension of BBL. Note that these can be password protected, although this protection is very easily broken. If you want to see or work on a bbl, change the extension to the Access database extension, mdb (Microsoft Jet DataBase).

In Access what you will see is two tables. Modern database programs actually house many files in a single "database" file. These are all in what is considered a "container" file. That way you can keep the files together without trying to keep track of which file goes with what when you copy and backup stuff. But this is not necessary for you to understand at this point, just information.

A BBL has 2 files, both tables (databases). One is called "Bible" and the other "Details".

"Details" File Format - 6 fields, "Description" Text field, "Abbreviation" Text field, "Comments" Text Field, "Font", "Apocrypha" Logical (True/False), "Strongs" Logical (True/False).

Description - is the tool tip popup screen text.

Abbreviation - is the text for the tab in the Bible panel.

Comments - is the fuller text of the e-Sword menu -> Bible-> Information. This should be where the copyright information goes in your file.

Font -  is probably the default font for the display of the Bible ("DEFAULT") would be in English letters.

Apocrypha - This Bible includes Apocrypha = .T. Logical True.

Strongs - This Bible includes Strongs Numbers = .T. Logical True.

Note that this table has only one record which contains information. I doubt if a second record would appear anywhere if you added one.

"Bible" File Format - 5 fields, "ID" Automatic Numeric field, "Book" Numeric field, "Chapter" Numeric Field, "Verse" Numeric Field, "Scripture" Memo field.

ID - an automatically generated field with the record number, unused by esword.

Book - Genesis is 1, etc.

Chapter - Genesis chapter 1, is 1, etc.

Verses - Genesis chapter 1, verse 1 is 1, etc.

Scripture - the scripture text actually displayed.

There is not much more to it. If you can program in Access, you just generate a file fitting these fields, and according to the books, chapters, and verses of the Bible, and then import the text. Strong's numbers appear to be a fixed thing that if they are in the text (and you click .T. True on the Details field "Strongs") then you will get these numbers in superscript green.

The Bible Import Programs below read a website or a file and generates the correct tables and records and copies the verse content into each individual record.

Problems with Imports: Note that if you do not place a blank space at the beginning of each Bible verse, e-Sword will not be able to search (find really is the point here) words that begin verses. This is probably because e-Sword searches are going to delete out the punctuation and search "_(blank space) word_(blank space)". Just my guess here.

Also note that e-Sword modules being Microsoft Access databases will read RTF formatting codes in their memo fields (the text we see). Most of the Bibles I have hacked to see how they work have NO RTF formatting so I would not bank on it and put anything in RTF in the memo field.

Phase 1 - Text preparation

Part A: I wrote/own this Bible Translation

If you are importing a Bible, I assume that you have the copyright to an original product. If not see Part B below. Basically you have the file in some kind of format, and that is the key to importing it into the e-Sword Format.

 Bible Import Programs

I would suggest you read the wikipedia article on e-Sword to get you up to speed on e-Sword generally (there they have a section on User Created Utility Programs at the bottom). There they mention the following programs, Biblos, Ben's e-Sword Tool, MFC Creator, Text2DAO, The WORDpad Editor, and the Tooltip Generator. Most all of them are going to want a delimited text file as an input file and then they will output a bbl (or some other e-Sword module format file).

In the case of most of these programs, please understand that e-Sword is freeware, and the utility programs that pop up to help, expand, etc. e-Sword are going to be freeware also. This means most people have something else in life that puts bread on the table, and their efforts in e-Sword utility programs is when they get time. None I have seen have a whole lot of bells and whistles. Just not going to happen.

 BIT (Bible Import Tool) Program  - This appears to be an older program that has been replaced by BeST (creator of both is Ben Krueger).

Comments: This program connects to BibleGateway.com or Crosswalk.com that has a lot of online Bibles and downloads what you want from these websites. This seems legal, although it is definitely not legal to distribute any of the resulting bbl files produced this way because you do not have permission from the copyright holders to do so (for those not under public domain).

Download Sites: nofearhereministries.org , PSU.edu, dnspad.com

 BeST (Ben's e-Sword Tool) Program  - "Ben's e-Sword Tool: (BeST). (Requires Microsoft .NET Framework 2.0) Converts web pages, flat files, .xml to e-Sword Bibles, Commentaries and dictionaries. This file contains the complete package installation program. Updates: TEST VERSION. This version uses a different encoding format for non-English text. The encoding SHOULD allow you to search in the same way that you can in e-Sword.net bibles. Backup your bibles before you try!" This description was taken from here.

Note that this program needs the Microsoft .NET  framework extension to Windowsto work (to make the conversions and import text, but not to display the end resulting bbl file). This is free from Microsoft, get it here. Warning that it about 22MBs. Since I haven't downloaded and installed NET yet, I will reserve comments on the program.

Help: Step4BibleModule.pdf (in Tai)

Download Sites: dnspad.com; pastorthroop.com

 Text2DAO Program  - This program works without .NET Framework. Probably the better of the programs I have listed here.

Download Sites: houseofmyrrh.com, groups.yahoo.com
Documentation: houseofmyrrh.com .

Part B: I am importing a Bible version from somewhere on the Internet.

There is first of all the copyright question. Even though you find a Bible version already on the Internet, that does not mean you have the right (copyright) to download it and repost it. The question of downing for personal use is open, and it is probably okay as long as you personally make the file yourself, and you do not share it. Legally it is still difficult to see how downloading something from some site on the Internet for personal use (without breaking a password entrance screen) can be construed as illegal.

 Phase 2 - Text retouching

I would recommend going to CraigWhite's download page of his utilities. His E-Sword MEd (Module Editor) free program can open and edit any unpassworded module. Very useful except it doesn't import from a text file. Even so it is excellent for doing touch up work on last minute changes to a module.

 Phase 3 - Text Import Problems

Coming