Alternate Versification
Disclaimer: Alternate versification support, though preliminarily implemented, is not yet complete in SWORD. The contents of this page will in some cases be incomplete or speculative. This page is under ongoing improvement while alternate versification support is improved in SWORD itself (and various front-ends).
Contents
Introduction
Alternate versification is also known as dynamic versification and has been abbreviated as v11n, av11n and dv11n.
In these three numeronyms, there are 11 letters between v and n in the word "versification".
- Canon pertains to what is included in a version of the Bible.
- Versification deals with the naming and order of books, and the numbering of chapters and verses in a canon.
As of SWORD 1.5.11, there was only one supported canon and versification: The KJV Old and New Testaments. This is represented in canon.h as a fixed, hard-coded system.
Alternate versifications mean ultimately to allow Bible texts with arbitrary canon or versification schemes to coexist peacefully on the same SWORD installation and (ultimately) to map cleanly between each other via cross references or parallel display.
There are technically 2 routes to support this under development:
- ripping out the hardcoded KJV canon.h offsets and replacing them with VerseMgr, which allows registration of canon.h-like v11n systems.
- genbook Bibles
Both these routes have been under development and 2 requires 1.
- is nearly completed and included in Sword 1.6.0.
- is not supported by Sword 1.6.0.
Overview
Up until 1.5.11, the canon and the versification were hard coded into the engine in the form of the file canon.h, which offered book names and chapter + verse offsets to the engine. The new approach is that:
- Each Bible module will carry a .conf entry identifying its versification from an supported list of versification systems. Without this identification, the versification system will default to "KJV" for backward compatibility.
- The engine will have, for each major canon and versification variety, a new header file similar to the previous canon.h.
- On system start, the engine will load, for each open KJV-divergent module, the relevant data presented in the relevant canon_{Versification].h into a table held in memory.
- Subsequently, the relevant module will be accessible via the usual methods - which have not changed from 1.5.11.
- What does not work anymore is to assume that a book or chapter has a set (fixed) number of verses. Instead, 1.6.0 introduces new methods VerseKey::getChapterMax() and VerseKey::getVerseMax() to provide the relevant information for a given module--replacing VerseKey::books[testament][book].chapmax and .versemax members.
- Similarly VerseKey::getBookName() and VerseKey::getBookAbbrev() replace the previous const char *name and const char *prefAbbrev respectively.
- At a later stage (>1.6.0) the engine will allow for GenBook Bibles to automatically create arbitrary versification tables on the fly.
- The final step (in >1.6.0) will be to allow mappings between versification schemes to allow cross-referencing and parallel display of corresponding passages.
GenBook Bibles
GenBook Bibles are Bibles stored in GenBook format. They are accessed via VerseKey, which in turn calls TreeKey.
The role of GenBook Bibles will mainly be to allow alternative versifications and canons over and above those provided by alternative canon header files.
SWORD Versification Tools
The primary versification tools are:
- v11nsys.pl – Converts a v11n spec into a SWORD canon header file.
- osis2mod – The -v11n flag allows one to build a Bible or commentary SWORD module with a versification other than the KJV.
- imp2vs – The -v11n flag allows one to build a Bible or commentary SWORD module with a versification other than the KJV.
Note: These are under development and may not work as expected until av11n is fully implemented.
How to Create Modules with Alternative Versifications
- Set the relevant entries in the configuration file
- If your module uses a versification or canon not yet present in SWORD you might have to create a canon header file. Sword tools contain relevant scripts. Please be aware that we will not hard code every versification under the sun but only select and important ones. If your scheme is not one of those you will need to go down the route of a GenBook Bible. Discuss on sword-devel what you are planning to do and you will get appropriate advice.
- The importers will work as usual. You'll specify a versification for the text to the import utility (imp2vs or osis2mod). It will pass the v11n value to the SWText constructor, which will instruct it to use the specified v11n.
- Append will also work as usual. Append pertains to whether a text is overwritten or appended to, so its use can affect the stored order of verses, but won't affect where the engine thinks they belong for access/display purposes.
- Each v11n will specify a book order, so different traditions that vary with respect to book order would have to be represented by different v11n definitions.
What happens to verses that fall outside the specified v11n?
During module making, what happens to verses in the source text that fall outside the specified v11n?
There are a variety of v11n schemes which can be specified when you import a module. Based on your selection, the tool will append extra verses to the previous canonical verse that has already been assigned content. Extra verses in a canonical chapter will be assigned to the last canonical verse that has been assigned content. Extra chapters in a canonical book will be assigned to the last canonical verse of the previous chapter that has been assigned content. Non-canonical books will be ignored or cause an error.
Supported versification systems
Pre-1.6.0
- KJV (The default v11n system in Sword)
1.6.0
- KJVA (KJV + Apocrypha)
- NRSV (This is a probable future replacement for KJV as the default v11n in Sword.)
- NRSVA (NRSV + Apocrypha)
- MT (Masoretic Text--for Hebrew Bibles)
- Leningrad (The v11n of the Leningrad Codex, except that the book order is different)
1.6.1
- Synodal (The v11n of the Russian Synodal Bible and related Bibles)
- Vulg (Vulgate)
- Luther (Luther)
- German (Identical to Luther, but without the apocryphal books and with Vulgate/KJV book order.)
1.6.2
- Catholic (The v11n of many Catholic Bibles, for those Bibles with 10 chapters in Esther)
- Catholic2 (The v11n of many Catholic Bibles, for those Bibles with 16 chapters in Esther)
- SynodalP (The KJV v11n, but employing verse counts of the Synodal v11n)
See also
- Canon Definition Format for Alternate Versification
- OSIS Book Abbreviations – which lists the books found all the various canons
Resources
- Harry Plantinga's Mapping of Alternate Versifications - a useful examination of various versification systems, based on data supplied by WBT, but due to numerous errors probably not a prospective source of data for Sword
- Books of the Bible – a side-by-side comparison of Jewish, Catholic, Orthodox and Protestant canons. The scope of this article is the book order - it does not dive down to chapter and verse level.
- Psalms – this article includes a handy table showing how the organization and numbering of the Psalms differs slightly between the (Masoretic) Hebrew and the (Septuagint) Greek manuscripts.
- Towards Canon-Neutral Bible Computer Applications, presented at BibleTech 2010 by Neil Rees of bfbs linguistic computing.
